From All-In to Walk It Back

It wasn't that long ago that Microsoft was genuinely excited about Claude Code. Like, rolling it out to thousands of engineers excited. The kind of rollout that signals real commitment — not just a pilot program buried in some experimental team.

In January, Microsoft pushed Claude Code to some of its biggest engineering divisions: CoreAI, and the Experiences + Devices team, which handles Windows, Microsoft 365, Outlook, Teams, and Surface. And here's the part that really stands out — even non-technical folks like designers and project managers were encouraged to use it. For prototyping, for experimenting, for getting a feel for what agentic coding could actually do.

Engineers were even asked to run Claude Code alongside GitHub Copilot and compare the two. That's not how you treat a tool you're lukewarm about.

But now? Those same teams are being told to wind things down.

What's Actually Changing — and Why

Microsoft has started canceling Claude Code licenses across its Experiences + Devices division, directing developers to move to GitHub Copilot CLI instead.

The Experiences + Devices team is facing a cutoff at the end of June, with engineers urged to shift their workflows to Copilot CLI in the coming weeks ahead of that deadline.

The timing isn't random. The June 30 deadline lines up with the end of Microsoft's fiscal year, making the license cancellations a clean way to trim costs before the new fiscal year kicks off in July. But it's not purely about the money, either.

Microsoft has framed the move as part of an effort to consolidate around Copilot CLI as the primary command-line tool for the division. Think about it this way: when you're a company the size of Microsoft, having your engineers split across multiple competing tools — especially tools that serve similar purposes — creates friction. Licensing costs, context-switching, support overhead. At some point, platform alignment starts to win out over best-in-class.

And honestly, GitHub has been managing its AI economics carefully more broadly — in April, it paused new sign-ups for Copilot Pro, Pro+, and Student plans to better manage service commitments. The whole division is tightening things up.

Anthropic's Models Aren't Gone Completely

Here's the nuance that's easy to miss in the headline: this isn't Microsoft walking away from Anthropic entirely.

Anthropic's models will still be accessible through Copilot CLI, alongside Microsoft's internal models and offerings from OpenAI. So the underlying AI capability stays — it's the standalone Claude Code product that's being phased out. The wrapper changes; the engine can still run underneath.

That's actually a pretty important distinction. It means this is less about Microsoft losing faith in Anthropic's technology and more about consolidating the interface through which engineers access it.

The Bigger Story Here

There's a tension playing out across the whole tech industry right now, and Microsoft's move captures it perfectly.

The shift reflects the pull between the appeal of best-in-class tools and the gravity of platform-native integration and cost predictability. Microsoft's initial embrace of Claude Code was itself an acknowledgment that Copilot had gaps — particularly in agentic coding and accessibility for non-developers. The retreat suggests that strategic alignment ultimately outweighed the tool's popularity among engineers.

That's a real thing, and it happens in enterprise software all the time. The "best tool" loses to the "our tool" more often than anyone wants to admit. Engineers love Claude Code. But love doesn't renew licenses — budgets and platform strategies do.

For Anthropic, losing thousands of enterprise seats at one of the world's largest software companies is a setback, even as Claude Code continues to gain traction elsewhere in the developer community.