Copilot in email: Microsoft embeds AI in the Outlook editor

What’s changing in email workflows

Microsoft is preparing a feature that brings Copilot chat directly into the email editor in the web version of Outlook. Currently, if you want the assistant to revise a sentence or add a paragraph, you have to open a separate sidebar and shift your attention between the email and the chat. The new version removes that step: the assistant appears alongside the text.

The roadmap describes the feature briefly: Copilot helps refine and edit emails as you write. The company has not shown the interface yet, so it’s unclear how much space the panel will take up or exactly what the interaction will look like.

How it works

The approach follows a model Microsoft already uses in other products. In Visual Studio Code, you can interact with the assistant alongside your code without switching to a separate window. In Outlook, Microsoft is trying to integrate AI into the writing process in the same way, so it feels like part of the editor rather than an external service.

This builds on previous steps. The company previously announced that it would force-enable the “Draft with Copilot” feature in all versions of Outlook, including classic Outlook, and add a permanently visible Copilot button to the classic version’s ribbon. Now it is moving on to embedding Copilot in the body of the email.

When to expect it and who it affects

The feature will be generally available, but will remain tied to a paid subscription. This matters as Microsoft gradually phases out free access to Copilot in Office apps for its largest customers and moves these capabilities to a paid tier. A Copilot license costs around 30 dollars per user per month, and companies are increasingly weighing whether this kind of integration is worth the investment.

What this means for administrators

Embedding an assistant in email raises questions that go beyond convenience.

• Data and compliance. Email text is sent to a cloud service. It’s worth deciding in advance which categories of correspondence should not be processed by Copilot.
• Licenses and roles. The feature is available only with a subscription, so access will need to be planned by department rather than enabled for everyone at once.
• Employee training. The lower the barrier to entry, the greater the risk that people will trust drafts the assistant hasn’t checked.

Practical implications

For everyday users, the benefit is clear: fewer switches between windows and faster edits. For a company, something else matters more—the boundaries of use. An assistant embedded in email blurs the line between a text editor and an external service, so it’s best to approve usage policies before rollout, not afterward.

Quality is another consideration. Based on the description, the feature helps formulate and continue text, but does not take responsibility for checking facts or attachments. The decision about what goes into the sent email remains with the user.