TL;DR<\/p>\n
June 30 Cutoff: Microsoft is winding down internal Claude Code on June 30, 2026, moving Experiences + Devices engineers onto GitHub Copilot CLI. Convergence Rationale: EVP Rajesh Jha framed the move as benchmarking-then-convergence, letting Microsoft shape security review, repository integration, and workflow tooling directly with GitHub. Anthropic Deal Intact: The wider Microsoft-Anthropic relationship stays in force, including the November 2025 Foundry agreement and Copilot Cowork inside Microsoft 365 Copilot. <\/p>\n
Microsoft appears to be winding down Claude Code inside its Experiences + Devices organization and is moving engineers across Windows, Microsoft 365, Outlook, Teams, and Surface onto GitHub Copilot CLI. Six months earlier, in December 2025, the company had started inviting thousands of its own developers to use Anthropic\u2019s terminal-based agentic coding tool daily. That internal experiment now reverses on a fiscal-year deadline.<\/p>\n
By the close of Microsoft\u2019s fiscal year, Experiences + Devices will finish consolidating agentic command-line work onto GitHub Copilot CLI. Cutting external Claude Code seats also trims software spending heading into the new fiscal year and narrows the company\u2019s agentic coding stack to a product Microsoft can shape directly with GitHub. As part of the same change, Microsoft is preparing to pull most of its internal Claude Code licenses and redirect the affected engineers to Copilot CLI for daily repository work.<\/p>\n
Inside The June 30 Cutoff <\/p>\n
Rajesh Jha<\/a>, Executive Vice President of Microsoft\u2019s Experiences and Devices group, oversees the affected division until his retirement in July, which houses engineers behind Windows, Microsoft 365, Outlook, Microsoft Teams, and Surface. In an internal memo, Jha reportedly<\/a> encouraged engineers to make the move to Copilot CLI in the coming weeks.<\/p>\n He framed the change as a benchmarking-then-convergence decision rather than a verdict on Anthropic\u2019s product. License cancellations are already underway, and many internal Claude Code seats are expected to come down before the fiscal-year cutoff.<\/p>\n Inside Experiences + Devices, that framing translates into specific operational changes. Engineers who had been running Claude Code against Microsoft repositories now need to migrate their workflows, custom scripts, and review processes onto Copilot CLI before the deadline. Team managers are expected to track that migration alongside their normal product schedules, treating it as a near-term engineering deliverable rather than a background cleanup task. Microsoft has not detailed any extension path for engineers still mid-project on Claude Code at the cutoff. Jha\u2019s memo positions GitHub\u2019s Copilot CLI engineering team as the front door for any open feature gaps, and sets out the rationale in his own words:<\/p>\n \u201cWhen 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. Claude Code was an important part of that learning\u2026 Copilot CLI has given us something especially important: a product we can help shape directly with GitHub for Microsoft\u2019s repos, workflows, security expectations, and engineering needs.\u201d<\/p>\n Rajesh Jha, Executive Vice President, Microsoft Experiences and Devices group (via The Verge<\/a>) A Convergence Argument Meets A Fiscal-Year Deadline <\/p>\n Two arguments sit behind the cutoff. One is convergence. By routing internal agentic coding work onto Microsoft\u2019s own command-line agent, Jha and GitHub leadership argue Microsoft can shape security review, repository integration, and workflow tooling directly rather than tailor an outside vendor\u2019s product. Jha added that GitHub has already shipped Copilot CLI improvements driven by Microsoft engineering feedback, and cast Experiences + Devices and GitHub as jointly accountable for turning Copilot CLI into the company\u2019s primary agentic coding experience. A single tool also gives Microsoft tighter control over how agentic actions interact with internal source-control policies, secret scanning, and code-review gates that vary across Windows, Microsoft 365, and Surface engineering groups.<\/p>\n Money is the other half. June 30, 2026 lands on Microsoft\u2019s fiscal-year close, and pulling external Claude Code seats reduces external software spending heading into the new fiscal year that begins in July. Microsoft had been paying for thousands of enterprise Claude Code seats, an expense Copilot platform billing shifts<\/a> make easier to bring back in-house as GitHub moves more of its agentic features onto usage-based pricing. Cutting that line item also resolves a quieter tension: Claude Code is popular inside the company, and some internal comparisons appear to show it outpacing Copilot CLI on real engineering tasks. Convergence asks developers to give up a tool they had begun to prefer, in exchange for a Microsoft-shaped product on a Microsoft-controlled roadmap and a billing path that flows back through GitHub.<\/p>\n What The Move Does Not Touch <\/p>\n A wind-down inside Experiences + Devices is scoped to Microsoft\u2019s internal engineering use of Claude Code. Anthropic\u2019s product is unaffected, and the wider Microsoft-Anthropic commercial relationship stays in place. A November 2025 Foundry agreement<\/a> gives Microsoft Foundry customers access to Claude Sonnet 4.5, Claude Opus 4.1, and Claude Haiku 4.5, and that contract remains in force. Claude models stay reachable through Copilot CLI alongside Microsoft\u2019s internal-only models and OpenAI\u2019s range. Engineers who still need a Claude model for a specific task can call it inside Copilot CLI rather than through Anthropic\u2019s standalone tool.<\/p>\n