Microsoft tells engineers to stop using Anthropic's Claude

Home Top stories Microsoft tells engineers to stop using Anthropic's Claude
Microsoft tells engineers to stop using Anthropic's Claude
Microsoft tells engineers to stop using Anthropic's Claude, as canceling Claude Code licenses becomes an easy way to…

Microsoft is canceling most internal Claude Code licenses by June 30, pushing engineers to its own GitHub Copilot CLI. The catch? Anthropic’s tool got too popular, undercutting Microsoft’s homegrown product. The official reason is toolchain unification, but The Verge reports the fiscal-year-end timing points to cost-cutting. It fits a wider AI spending crunch hitting Uber and others. Claude models stay available through Copilot CLI, so this isn’t a full break with Anthropic.Microsoft handed thousands of its own engineers a free pass to Anthropic’s Claude Code back in December, no strings attached. It wasn’t just developers either. Project managers, designers, and other non-technical staff were nudged to try it out and prototype ideas they’d never have touched before. The tool caught on fast. Too fast, as it turns out, and now it’s being taken away.Six months later, Microsoft is pulling most of those licenses and pushing developers toward its own GitHub Copilot CLI instead, with a hard cutoff of June 30. That date isn’t random. It’s the last day of Microsoft’s fiscal year. The official line for the switch is toolchain unification. The unofficial one, according to The Verge, is the bill, a story playing out everywhere from Uber to Amazon as the real cost of heavy AI use starts to bite.

A popular tool became an inconvenient one

Microsoft’s pitch for Claude Code was simple: let people experiment, learn what works, and see where AI coding fits across the company. It worked, maybe better than anyone planned. Warren reported that Claude Code became “perhaps a little too popular” inside Microsoft, with engineers consistently reaching for Anthropic’s tool over Microsoft’s own Copilot CLI.That preference is exactly the catch. A product Microsoft doesn’t own had started eating into one it’s trying to build and sell to its own cloud customers. The two were never supposed to compete head-to-head like this. Engineers were meant to use both, compare them, and file feedback.The fallout lands on Microsoft’s Experiences + Devices team, the group behind Windows, Microsoft 365, Outlook, Teams, and Surface. That division is winding down Claude Code usage and shifting engineers to Copilot CLI over the coming weeks, ahead of the June cutoff.Rajesh Jha, Microsoft’s EVP of experiences and devices, framed it as a learning exercise that ran its course in an internal memo seen by The Verge. “Claude Code was an important part of that learning,” he wrote, adding that Copilot CLI gives Microsoft a product it can shape directly with GitHub for its own repos, workflows, and security expectations.

The deadline lines up with the books, not the strategy

Here’s the detail that gives the real motive away. June 30 is the last day of Microsoft’s fiscal year. Canceling Claude Code licenses right before the books close is a clean, low-effort way to trim operating expenses heading into the new financial year in July.Microsoft is telling staff the decision is about converging on a single command-line tool across Experiences + Devices. But sources told The Verge the financial angle is just as real, even if it isn’t the headline reason.It fits a much wider pattern across the industry. Token-based pricing, where every prompt and code generation request chips away at a budget, scales fine for one developer and gets ugly fast across thousands of them. Agentic coding tools run for hours, spawn parallel threads, and burn through volumes of compute that the old autocomplete pricing models never accounted for.Uber is the cautionary tale everyone keeps pointing to. It burned through its entire planned 2026 AI coding budget in four months, with some engineers racking up between $500 and $2,000 a month in tokens. Its CTO said he was back to the drawing board because the budget he thought he’d need was already gone.

The bet now rides on GitHub

This move is less about dropping Anthropic than it is about Microsoft betting on GitHub. Copilot CLI is the destination, and the whole point is that Microsoft can shape it directly with the GitHub team for its own repos, workflows, and security needs. That’s something it could never do with a third-party tool like Claude Code. It also means the spend stays in-house rather than flowing to a competitor every time an engineer fires off a prompt.Anthropic isn’t disappearing from the picture, either. Claude models stay reachable through Copilot CLI, sitting alongside OpenAI’s models and Microsoft’s own internal ones. The November Foundry deal that gives Microsoft customers access to Claude Sonnet 4.5, Opus 4.1, and Haiku 4.5 stays in place. Microsoft also still leans on Claude inside Microsoft 365 and Copilot for tasks where it outperforms OpenAI’s models, and the two firms recently brought the technology behind Claude Cowork into Microsoft 365 Copilot.What’s actually ending is the experimental phase, the stretch where Microsoft was happy to absorb open-ended token costs just to see what its workforce would do with the tools. Microsoft told The Verge last year that 91 percent of its engineering teams used GitHub Copilot, a number Claude Code clearly dented over six months. Now the pressure shifts to the GitHub team to make Copilot CLI good enough that engineers don’t miss what they’re giving up.Whether that lands is another question. For now, Microsoft’s own engineers are losing a tool they actually liked, and being handed one they’ll have to learn to. The bigger test isn’t the deadline. It’s whether Copilot CLI can win them back on merit once the free Claude Code seats are gone.

source

Leave a Reply

Your email address will not be published.