Microsoft is canceling most of its internal Claude Code licenses by June 30, 2026, and redirecting thousands of engineers to GitHub Copilot CLI instead. The cutoff lands on the final day of Microsoft's fiscal year, and the wind-down covers the Experiences + Devices group — the org that ships Windows, Microsoft 365, Outlook, Teams, and Surface. Internal adoption of Anthropic's coding tool had run for roughly six months after a December 2025 rollout.
The problem, by Microsoft's own framing, is that Claude Code worked too well. Engineers who were supposed to be benchmarking both tools in parallel ended up favoring Claude Code over Copilot CLI in recent months, undermining the in-house product Microsoft wants its developers to be improving. Last year Microsoft said 91% of its engineering teams were using GitHub Copilot — a number that took a visible hit once Claude Code landed on developer machines.
Rajesh Jha, executive vice president of Microsoft's experiences and devices group, framed the shift as convergence in an internal memo. "When we began offering both Copilot CLI and Claude Code, our goal was to learn quickly, benchmark the tools in real engineering workflows, and understand what best supported our teams," Jha wrote. "Claude Code was an important part of that learning… at the same time, Copilot CLI has given us something especially important: a product we can help shape directly with GitHub for Microsoft's repos, workflows, security expectations, and engineering needs."
Key facts
- 01Microsoft is removing most Claude Code licenses across its Experiences + Devices group by June 30, 2026, the final day of its fiscal year.
- 02Engineers are being told to transition to GitHub Copilot CLI in the weeks before the cutoff, with Copilot CLI positioned as the standard agentic command-line tool.
- 03Microsoft first rolled out Claude Code internally in December 2025, opening access to thousands of developers alongside designers and project managers.
- 0491% of Microsoft engineering teams were on GitHub Copilot last year, a figure dented by six months of internal Claude Code adoption.
- 05Anthropic's models remain available through Copilot CLI, and the November 2025 Microsoft Foundry deal covering Claude Sonnet 4.5, Opus 4.1, and Haiku 4.5 is unaffected.
The fiscal-year timing is not subtle. Canceling Claude Code seats on June 30 trims operating expenses heading into July, the start of Microsoft's new financial year, and removes a line item that had grown faster than expected as adoption spread beyond developers to designers and project managers prototyping with natural language.
“Microsoft engineers favored Claude Code over GitHub Copilot CLI in recent months — a problem when 91% of internal engineering teams are supposed to be using Copilot.”— Jaeden Schafer
The pitch to engineers is shared ownership of the in-house tool. "We are partnering closely with GitHub and continue to improve Copilot CLI for Microsoft engineers," Jha wrote. "The GitHub team has already shipped significant improvements based on Microsoft feedback, and Experiences + Devices will remain closely involved in shaping the product. This is a shared accountability across GitHub and E+D leadership: to make Copilot CLI the best agentic coding experience for Microsoft engineers."
Anthropic's models themselves are not being purged from Microsoft. Claude Sonnet 4.5, Claude Opus 4.1, and Claude Haiku 4.5 remain available to Microsoft Foundry customers under a November 2025 commercial deal, and Anthropic's models will still be selectable inside Copilot CLI alongside OpenAI's models and Microsoft's internal-only models. Inside Microsoft 365 Copilot, employees continue to prefer Claude for several task types where it outperforms OpenAI counterparts, and Microsoft worked with Anthropic recently to bring the technology behind Claude Cowork into Microsoft 365 Copilot.
Microsoft had reportedly weighed an acquisition of Cursor in recent months to narrow the gap between Copilot CLI and Claude Code before pivoting to look at other AI startups, in part to avoid regulatory scrutiny. That hunt fits a broader pattern: Microsoft has spent 2026 quietly diversifying away from any single AI dependency, including its OpenAI relationship, while still leaning on Anthropic for capability gaps Copilot has yet to close.
The commercial relationship with Anthropic remains substantial. Microsoft became one of Anthropic's top customers earlier in 2026 and has reportedly counted Anthropic model sales toward its Azure quotas. Pulling Claude Code from internal seats trims a cost line without breaking the Foundry distribution arrangement that pushes Claude to enterprise buyers through Microsoft's cloud.
The transition will not be clean. Microsoft had spent months encouraging non-engineers — designers, PMs, employees with no coding background — to prototype with Claude Code, and those users now have to relearn workflows on Copilot CLI ahead of the June 30 cutoff. Microsoft is asking developers to file bug reports against Copilot CLI in the meantime, an acknowledgment that real gaps remain between the two tools.
There is also the awkward optics of an internal preference being overridden by procurement logic. Microsoft is asking engineers who chose Claude Code on the merits to switch to the product Microsoft sells, which is a coherent business decision but a measurable signal about which tool won the bake-off when employees were free to pick.
For Anthropic, losing the Microsoft internal seat count is a revenue dent but not a strategic blow — Claude Code retains the developer mindshare that drove the internal preference in the first place, and Anthropic's distribution through Foundry continues. For GitHub, the mandate is harder: Copilot CLI now has to earn back the engineers it lost to Claude Code, with the people writing the bug reports being the same people who picked the rival product when given a choice. Whether that produces a better Copilot CLI or just a captive one is the question the next two quarters will answer.
Working on something we should cover, or seeing a story we missed? Send leads, documents, or feedback to hello@aichatdaily.com. For sensitive tips, see our secure tips page for Signal and PGP options.
Spotted an error? Email hello@aichatdaily.com with the URL and the issue, or read our full corrections policy.
