🔍 Read the full analysis: Meta And Microsoft Pulled Back From Claude—What Would Switching Cost? on ThorstenMeyerAI.com
Get tech for your team delivered free — and shop member deals
- Fast, free delivery on millions of items
- Access to Prime Big Deal Days deals on October 6–7
- Prime Video, Amazon Music and more included
TL;DR
The Information reported on Oct. 5 that Meta reduced employee use of Claude Code and Microsoft lowered its projected internal spending on Anthropic technology. The reported shifts are driven by cost controls and available alternatives, not a stated finding that Claude performs worse; both companies reportedly continue to use Anthropic technology in other ways.
Meta and Microsoft are reducing some employees’ use of Anthropic’s Claude tools and redirecting internal work to alternatives, according to an Oct. 5 report by The Information. The reported moves reflect cost controls and existing in-house or partner tools, not a public claim that Claude performed worse, and do not indicate that either company has ended its broader use of Anthropic technology.
Meta reportedly cut the number of employees using Claude Code from about 60,000 earlier this year to about 30,000. The company has been directing staff toward its own coding tools: MetaCode, which the source report says has more than 30,000 internal users, and Muse Code, with more than 6,000. These figures describe internal use, not customer adoption.
Microsoft had reportedly projected more than $1 billion a year in internal spending on Anthropic technology, including Claude Code, Claude models used in Copilot and Claude Mythos. The Information reported that Microsoft later cut that projection by more than a third and steered employees toward GitHub Copilot and OpenAI models. The available source material does not specify the revised spending figure or the exact period over which the changes took place.
The shifts are not described as a complete break. The source material says Microsoft continues to spend heavily on Anthropic models for customer-facing Copilot features, while customer spending on Claude through Microsoft platforms is reportedly growing. Neither the report as summarized here nor the companies’ stated reasons establish that Claude has been discontinued or judged inferior.
Meta and Microsoft pulled back from Claude. Here’s what switching actually costs.
The Information reports both companies steering their own employees away from Claude. Read as a verdict on Claude, it misleads. Read as a demonstration of switching — and who can afford it — it’s the most useful enterprise-AI signal this month.
Staff steered to GitHub Copilot and OpenAI models; stricter token budgets. One unconfirmed report: some team budgets ~$100k → ~$10k/month.
Microsoft reportedly still spends heavily on Claude for customer-facing Copilot — and that spending is reported to be growing.
Reported drivers: rising token costs and owned alternatives. Neither company is reported to have called Claude worse.
Meta builds coding tools; Microsoft owns Copilot and backs OpenAI. This is ordinary vertical integration.
Keep a second vendor live on real work.
A few hundred tasks with pass criteria.
Logic, prompts, tools in your layer.
Tokens are the cheap half.
Know what you’d rebuild.
On the evidence reported, Meta and Microsoft didn’t reject Claude. They brought spending in-house where they could and kept buying where they couldn’t — Microsoft remains a large Anthropic customer for the products it sells. The signal is the mechanism: the most sophisticated buyers treat models as interchangeable suppliers behind a layer they control.Meta could halve its Claude usage because it had built somewhere else to go. Build somewhere else to go.
Switching Depends on Ready Alternatives
The reported changes show that a large buyer can redirect work when it has credible alternatives already deployed. Meta has internal coding tools, while Microsoft has GitHub Copilot and access to OpenAI models. That makes their decisions different from a typical organization’s: the substitutes and engineering capacity are already in place, so a shift may be easier to carry out.
For companies without those resources, the listed price of another model is only part of the cost. Teams may need to repeat evaluations, adapt prompts and tool integrations, retrain employees on a different coding assistant and accept a temporary productivity drop. Workflows can also behave differently on a replacement model, creating more review and rework even when the tool still produces usable results.
Those costs can change whether switching saves money. The source material calculates that a reduction of more than a third from a projection above $1 billion would represent more than $300 million annually if the projection and reduction are comparable. That is an illustration based on reported figures, not a confirmed realized saving. At smaller organizations, migration costs could outweigh near-term savings; the actual balance depends on workload, performance and implementation effort.
As an affiliate, we earn on qualifying purchases.
Internal Use Is Not Customer Exit
The report concerns employees’ internal use at Meta and Microsoft. It does not establish that either company has stopped offering Claude to customers, nor that customers have moved away from Anthropic. Microsoft’s reported continued use of Claude in customer-facing Copilot features is a significant distinction when interpreting the internal cutbacks.
Both companies also have interests in alternatives. Meta develops its own models and coding products. Microsoft owns GitHub Copilot and is a major backer of OpenAI. That competitive position provides a business reason to route some employee work to their own or affiliated tools, alongside the reported pressure to manage token costs and spending.
The source material also describes a possible tightening of Microsoft team budgets: one account put some monthly budgets at about $100,000 before a reduction to around $10,000. This detail is attributed to a single report and should not be treated as a company-wide policy. It illustrates the kind of spending control that may accompany tool changes, but the scope and application are not established.
As an affiliate, we earn on qualifying purchases.
Costs and Quality Remain Unmeasured
The available reporting does not give the exact dates, revised Microsoft spending total or the precise amount of work redirected at either company beyond the reported Meta user count. It also does not establish the resulting savings, whether the moves apply across all teams, or how long any transition took.
Neither company is reported here as saying Claude’s quality was the reason for the changes. The reported factors are rising token costs, tighter spending controls and the availability of alternatives. The operational effects—including whether replacement tools deliver comparable results on each team’s tasks—remain unclear.
The migration costs described for other enterprises are practical considerations, not figures measured in this report. No data is supplied on evaluation results, employee productivity, cache expenses, review time or errors after the changes. Those gaps make it difficult to judge the net financial effect or to generalize the companies’ experience to a smaller buyer.
As an affiliate, we earn on qualifying purchases.
Watch for Spending and Usage Data
The next useful evidence would be updated company disclosures or reporting that clarifies how much internal Claude use remains, what Microsoft’s revised projection is, and whether either company reports measurable savings or changes in output quality. Customer-facing use should be tracked separately from employee use.
For other organizations evaluating model providers, the development points to a practical preparation step: test alternatives on representative work before a price or policy change forces a decision. Maintaining evaluations and portable integrations can lower the cost of a future switch, but the report does not show that every company should move away from Claude—or that a second provider will be cheaper once engineering and review costs are counted.
As an affiliate, we earn on qualifying purchases.
Key Questions
Have Meta and Microsoft stopped using Claude?
No complete exit is established. The report concerns reductions in internal employee use. The supplied material says Microsoft continues to use Anthropic models in customer-facing Copilot features.
Why are the companies reportedly reducing internal use?
The reported reasons are token costs, tighter spending controls and access to alternatives. The material does not attribute the moves to a finding that Claude performed worse.
How much did Meta reduce Claude Code use?
Meta reportedly went from about 60,000 employees using Claude Code earlier this year to about 30,000. The figures refer to internal users, not customers.
What did Microsoft reportedly change?
Microsoft reportedly cut by more than a third its projected internal annual spending on Anthropic technology, from a projection above $1 billion a year, and redirected employees toward GitHub Copilot and OpenAI models. The revised projection is not provided.
What can make switching AI tools costly?
Organizations may need to retest workflows, revise prompts and integrations, retrain employees and account for changes in review, rework and model performance. The overall cost depends on the organization’s tools and workloads.
Source: ThorstenMeyerAI.com
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
