Microsoft 365 Copilot Is Changing How Code Appears in Chat: What Users Need to Know

Microsoft is making another small but meaningful change to the Microsoft 365 Copilot experience. Starting in mid-September 2026, Microsoft 365 Copilot will begin rolling out support for inline previews of code blocks, charts, diagrams, and other supported visual content directly within conversations.

At first glance, this may sound like a minor interface update. But for people who regularly use Copilot to generate code, visualize information, create diagrams, or work through technical tasks, the change could make everyday interactions considerably smoother.

The biggest difference is simple: users will no longer need to rely on a separate side-by-side code canvas to preview supported generated content. Instead, the content can appear directly inside the Copilot conversation, keeping the work in one place.

Microsoft 365 Copilot brings code previews directly into conversations

Until now, users working with generated code in Microsoft 365 Copilot could preview that content through a separate code canvas experience. While the canvas provided a useful workspace, it also meant moving away from the main conversation.

The new inline preview experience is designed to reduce that friction.

With the update, supported code blocks will be displayed directly within the Copilot conversation. Users will also be able to preview supported charts, diagrams, and similar visual outputs without having to open a separate experience.

That means a Copilot conversation can become more self-contained. A user can ask Copilot to generate something, review the result, make a follow-up request, and continue working without repeatedly switching between different views.

For users who rely on Copilot as part of their daily workflow, that seemingly small change could make the overall experience feel faster and more natural.

Why this change matters

One of the biggest challenges with AI assistants is maintaining context.

When an AI-generated result requires users to open another panel, window, or workspace, the interaction can become fragmented. Users have to move back and forth between the original prompt and the generated output.

Microsoft’s move toward inline previews addresses that issue by keeping generated content closer to the conversation that produced it.

Imagine asking Copilot to create a piece of code, explain how it works, and then modify one section. With inline previews, the generated content remains part of the same conversational flow. Users can review it and continue asking questions without feeling like they have left the conversation.

The same principle applies to visual content.

A chart generated from information in a conversation can be previewed where the discussion is taking place. A diagram can be reviewed without opening another workspace. For users who work with a combination of text, technical content, and visual information, this could make Copilot feel more cohesive.

What users can expect

Microsoft says the update will support inline previews for code blocks and other supported content, including charts, diagrams, and similar visual outputs.

The key changes include:

Code blocks can render directly within Copilot conversations.
Supported charts and diagrams can be previewed inline.
Users won’t need to open a separate code canvas for supported previews.
Generated content stays closer to the conversation context.
Existing Copilot prompts and workflows will continue to work as expected.

Importantly, this is primarily an experience improvement rather than a major change to how Microsoft 365 Copilot works.

Users do not need to learn a completely new Copilot workflow. Instead, content that previously required an additional preview experience will increasingly appear directly in the conversation.

When will the new Copilot experience arrive?

Microsoft says the worldwide rollout is scheduled to begin in mid-September 2026, with the company expecting the rollout to be completed by late September 2026.

As with many Microsoft 365 updates, the exact timing can vary as the change becomes available across environments and users.

Organizations therefore shouldn’t be concerned if the new experience does not appear for everyone at exactly the same time. The rollout is expected to happen progressively during the stated window.

No administrative action is required

For Microsoft 365 administrators, the good news is that this update does not introduce a significant configuration burden.

Microsoft indicates that no action is required from organizations.

Existing Copilot prompts and workflows should continue to work as expected, meaning companies do not need to redesign their Copilot processes simply because previews are moving into the conversation.

However, there is one area where organizations may want to take action: internal documentation.

Companies that have created training materials, screenshots, user guides, or adoption documentation showing the previous side-by-side code canvas experience may eventually want to update those materials.

This is especially relevant for organizations that have invested heavily in Microsoft 365 Copilot training. Users following older documentation could become confused if the interface they see differs from the screenshots or instructions in their training materials.

A short communication explaining the change could be enough.

A better experience for developers and technical users

The update could be particularly useful for developers, analysts, technical teams, and other users who regularly ask Copilot to generate or interpret structured content.

For example, a user might ask Copilot to produce a code snippet and then follow up with questions about errors or improvements. Having the code visible in the conversation can make those interactions easier to follow.

It can also make collaborative discussions more straightforward. Instead of explaining where a particular generated result can be found, users can reference content that appears directly in the conversation.

That does not mean the separate code canvas concept is suddenly irrelevant in every scenario. More complex tasks may still benefit from dedicated workspaces. But for quick reviews, iterations, and conversational workflows, inline previews offer a more immediate experience.

What this means for Microsoft 365 Copilot adoption

The update also fits into a broader trend in AI software: making generated content feel like a natural part of the conversation rather than something users have to manage separately.

As AI assistants become more capable, they increasingly produce different types of outputs. A response might contain ordinary text, programming code, a chart, a diagram, or another structured artifact.

The challenge for product designers is making those outputs easy to consume.

Inline previews are one way to solve that problem.

Rather than treating every output as a separate artifact, Microsoft is bringing more of the experience into the conversational interface. This could help reduce friction for everyday Copilot users and make it easier for less technical users to understand generated content.

What organizations should do now

There is no urgent technical action for Microsoft 365 administrators.

Still, organizations can use the rollout as an opportunity to review their Copilot adoption materials.

IT and digital workplace teams should consider checking whether their internal documentation includes references to the separate code canvas. If it does, screenshots and instructions may need to be refreshed once the new experience becomes available.

Organizations may also want to let users know that the change is expected and that they do not need to change their existing prompts or workflows.

For most users, the transition should be relatively straightforward: keep using Copilot as usual and take advantage of the new inline previews as they become available.

The bigger picture

Microsoft 365 Copilot continues to evolve from a traditional AI chat experience into a more integrated productivity assistant.

Bringing code, charts, diagrams, and other supported visual outputs directly into conversations is not necessarily the biggest Copilot update Microsoft has introduced. But it is the kind of usability improvement that can have a noticeable impact on everyday work.

The less users have to switch between interfaces, the easier it becomes to maintain context and keep moving.

For organizations already using Microsoft 365 Copilot, this September 2026 update should therefore be viewed as a low-impact administrative change with a potentially positive user-experience benefit.

There is no configuration work required, no major workflow redesign, and no immediate action needed. Organizations simply need to be aware that the way users preview generated content is changing.

As the rollout progresses through September, users should begin seeing supported code and visual content appear more naturally within their Copilot conversations.

And sometimes, the most useful AI improvements are the ones that simply remove a few extra clicks from the work people are already doing.