Claude and Microsoft: Microsoft 365 Integration and the Internal Copilot Migration

Are Claude and Microsoft "allies" or "rivals"?

First things first: Anthropic (the maker of Claude) and Microsoft are not simple competitors. Microsoft is well known for its massive investment in OpenAI, but it has also been actively incorporating Claude into its business applications and cloud services. Because users have different preferences when it comes to AI models, Microsoft is moving toward offering multiple AI options on its own platform.

As a result, Claude is officially offered as a selectable option on Microsoft 365 and Azure. At the same time, what Microsoft chooses to use internally for its own software development is a separate business decision — and there, it pulled back on Claude Code. "Claude embedded in products" and "Claude used by employees" are decisions made at different layers — that's the essence of the duality.

Claude Integrated into Microsoft 365: What Can You Do in Office?

On May 7, 2026, Anthropic launched the general availability (GA) of Claude for Microsoft 365. The Excel, Word, and PowerPoint integrations reached GA across all paid plans, while the Outlook integration joined as a beta (sources: The New Stack, "Claude can now follow users across Outlook, Word, Excel, and PowerPoint" https://thenewstack.io/claude-word-excel-powerpoint-outlook-microsoft-office/ ; official page https://claude.com/claude-for-microsoft-365 ).

The defining feature is context that persists across all four apps. You can bring content from an Outlook email into Excel and carry it through to PowerPoint — no need to re-explain the situation every time you switch apps. Output comes in native formats: in Word, changes appear as tracked revisions; in Excel, edits don't break formulas; in PowerPoint, slides are formatted to match your slide master. Both Mac and Windows are supported.

Note that the "Microsoft 365 Connector (read-only)" — which lets Claude search across your internal emails and files — is a separate feature. Connection steps and coverage are covered in detail in the Claude and Microsoft 365 connection article and the Microsoft Teams integration article.

Calling Claude via Azure / Microsoft Foundry

For enterprises that cannot send data to Anthropic's servers, cloud-based routing options are available. Claude for Microsoft 365 traffic can be routed through Amazon Bedrock, Google Cloud Vertex AI, or Microsoft Foundry. With this setup, the add-in works without a direct Anthropic account, and data stays within the cloud infrastructure your organization already uses.

For developers calling Claude via API, routing through Microsoft Foundry or Azure Databricks is also an option. Supported models, regions, authentication, pricing, and how to choose between this and Azure OpenAI Service are all covered in the article on using Claude AI on Azure. This is the entry point for enterprises that want to use Claude within their existing Microsoft cloud contracts.

Selecting Claude in Microsoft 365 Copilot's Researcher

Microsoft 365 Copilot also offers a way to bring Claude in. In Copilot's "Researcher" agent, users can select Anthropic's Claude models as the underlying model (source: Microsoft Support, "Use Claude with Researcher in Microsoft 365 Copilot" https://support.microsoft.com/en-us/microsoft-365-copilot/use-claude-with-researcher-in-microsoft-365-copilot ).

However, there are prerequisites. In order:

1. An administrator must first grant access to Anthropic AI models in the Microsoft 365 Admin Center.
2. The user must hold a Microsoft 365 Copilot license (required to access the model selection feature).
3. Only once both conditions are met can the user switch to Claude in Researcher's model selector.

In other words, there is an officially supported way to run Copilot's research tasks "with Claude's intelligence." It's the most straightforward example of Claude operating inside Microsoft's business UI.

Meanwhile, Microsoft Cut Claude Code Internally

That covers the "distribution" side. The opposite movement is the internal retreat.

According to reports, in December 2025 Microsoft began providing Anthropic's command-line coding agent Claude Code — at company expense — to thousands of engineers and product managers in its Experiences and Devices division, which builds Windows, Microsoft 365, Outlook, Teams, and Surface. About six months later, however, that experiment scaled back. Many of the directly contracted Claude Code licenses were cut, and affected engineers were notified to migrate to GitHub Copilot CLI by June 30, 2026 (the end of the fiscal year) (sources: The Next Web, "Microsoft's quiet Claude Code retreat and the real cost of enterprise AI" https://thenextweb.com/news/microsoft-claude-code-retreat-ai-cost ; Windows Central https://www.windowscentral.com/microsoft/microsoft-cancels-claude-code-licenses-shifting-developers-to-github-copilot-cli-a-move-likely-driven-by-financial-motives ).

The official explanation is "consolidating the toolchain," but multiple outlets point to cost as the real deciding factor.

Why the Retreat? Token-Based Billing and Enterprise AI Cost Dynamics

At the heart of the retreat is the fact that coding agents use token-based, pay-per-use pricing. Unlike traditional per-seat licenses, the bill grows the more you use it — making costs hard to predict upfront. One article described it as "the meter keeps running even when nobody's watching."

Cited examples suggest individual engineers consumed tokens worth $500 to $2,000 per month. The irony is that because the tool is excellent, engineers use it constantly — and that constant use drives costs through the roof. A tool too good to stop using is, at current token prices, harder to justify than a mediocre tool that sits idle. This is the current dilemma of enterprise AI coding.

The fact that even a giant like Microsoft ran into this math carries a heavy lesson for other companies looking to roll out AI coding tools internally.

How to Read "Claude We Distribute" vs. "Claude We Don't Use"

Here's how to make sense of the duality. Microsoft embeds Claude in its products because users want Claude — offering it as an option is itself a competitive advantage for Microsoft 365 and Azure. On the other hand, what Microsoft uses internally is purely a cost optimization question, and there it concluded it made more economic sense to rely on its own GitHub Copilot.

This isn't contradiction — it's a difference in role. Microsoft as a platform provider "lines up models neutrally for users"; Microsoft as a business "cuts costs with its own tools." The same company is simply doing both at once. For a direct comparison of Claude Code and Copilot CLI themselves, see the Claude Code vs Copilot CLI article and the Claude Code vs GitHub Copilot comparison.

Choosing How to Use Claude in a Microsoft Environment

Finally, here's a decision guide from the user's perspective. Your entry point depends on where you're coming from.

1. Individuals or teams who want to use Claude for Office work: Install the Claude for Microsoft 365 add-in (Word/Excel/PowerPoint; Outlook is in beta) on a paid plan.
2. Those who want to search across internal data: Connect the Microsoft 365 Connector (read-only) (setup steps).
3. Those who want to run Copilot's research tasks with Claude: Have an admin enable Anthropic models, then select Claude in Researcher's model selector.
4. Enterprises that need data to stay within their own cloud: Route through Microsoft Foundry / Azure Databricks / Bedrock / Vertex AI (Azure routing guide).
5. Coding use cases: Compare the cost and autonomy of Claude Code vs. Copilot CLI and choose accordingly (CLI comparison).

Summary: The Current State of Microsoft × Claude

The conclusion as of June 2026 is clear. The environment for using Claude within Microsoft products has never been more complete — the Office integration is GA, it's selectable in Copilot's Researcher, and enterprise pathways via Azure/Foundry exist. At the same time, Microsoft itself chose not to continue using Claude Code for internal development — migrating to Copilot CLI by the June 30 deadline.

"Integration advances; internal use retreats." This duality is the most accurate description of the Claude-Microsoft relationship in 2026. For users, the practical takeaway is: take full advantage of the integration pathways on offer — but for coding use cases specifically, look at your own usage volume and costs before deciding. That's the optimal approach for now.