Why Microsoft Is Dropping Claude Code Despite Its Superior Performance

Microsoft will revoke internal Claude Code licenses and force engineers to switch to GitHub Copilot CLI, citing cost savings and ecosystem control, even though benchmark data shows Claude Code outperforms Copilot on SWE‑bench, multi‑file refactoring, and large‑context tasks.

21CTO
21CTO
21CTO
Why Microsoft Is Dropping Claude Code Despite Its Superior Performance

Microsoft announced that, by June 30, the Experiences + Devices team will discontinue most internal Claude Code licenses and require all engineers to adopt the GitHub Copilot CLI.

Benchmarking on SWE‑bench shows Claude Code achieving an 80.8% score, 8.3 points higher than the GPT‑4o‑based Copilot (72.5%). For tasks involving changes to more than five files, Claude Code’s success rate is 23% higher than Copilot’s, and on cross‑file refactoring/debugging scenarios Claude Code completes 89% of tasks versus Copilot’s 60%.

Since its internal release in December, Claude Code rapidly attracted thousands of engineers, diverting core users from Copilot CLI and becoming the preferred tool for many Microsoft developers.

The move occurs amid a broader Microsoft‑Anthropic partnership: Microsoft has invested heavily in Anthropic, integrated Claude models into Azure Foundry and Microsoft 365 Copilot, and even considered acquiring the AI‑coding startup Cursor before abandoning the plan for antitrust reasons.

According to an internal memo from Rajesh Jha, the decision serves two purposes: cutting the sizable subscription cost for thousands of Claude Code licenses at fiscal‑year‑end, and consolidating the internal tooling ecosystem to boost Copilot adoption and close the product loop.

Technical differences reinforce the strategic shift: Claude Code offers a million‑token context window and can handle roughly 3,000 files per session, whereas Copilot CLI is limited to a 128 KB token context, making large‑scale migrations challenging.

Engineers now face a six‑week migration window, during which they must adapt to a less mature Copilot CLI, effectively experiencing a forced downgrade in tooling capability.

While Microsoft will continue to use Anthropic models in Azure Foundry and Microsoft 365, the company’s stance remains clear: external tools may be valuable, but internal tooling priority prevails.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

MicrosoftGitHub CopilotAnthropicSWE-benchAI coding assistantsClaude Codetooling migration
21CTO
Written by

21CTO

21CTO (21CTO.com) offers developers community, training, and services, making it your go‑to learning and service platform.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.