🔍 Read the full analysis: Meta And Microsoft Pulled Back From Claude. Is Switching Worth The Cost? on ThorstenMeyerAI.com
Get office and shipping supplies 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 roughly halved internal use of Claude Code and Microsoft cut its projected annual internal Anthropic spending by more than a third. The reported reasons were costs and available alternatives, not a stated finding that Claude performed worse. The scale of the companies’ existing tools makes their ability to switch different from that of most businesses.
Meta and Microsoft are steering some employees away from Anthropic’s Claude tools, according to a report by The Information published Oct. 5, citing internal use and spending changes at the two companies. The reported shifts point to cost controls and available alternatives, not a public finding that Claude performed worse; both companies have built or backed other AI tools that can take on some work.
The report said Meta’s internal use of Claude Code fell from about 60,000 employees earlier this year to about 30,000. It also said Meta has directed staff toward its own coding tools: MetaCode, which had passed 30,000 internal users, and Muse Code, which had passed 6,000. The supplied account does not specify the precise measurement dates for those user totals.
At Microsoft, The Information reportedly said the company had projected more than $1 billion a year in internal spending on Anthropic technology, including Claude Code and Claude models used in Copilot. The company has since cut that projection by more than a third and is steering employees toward GitHub Copilot and OpenAI models, according to the report. A projected budget is not the same as confirmed realized spending or savings.
The reported figures concern employees’ internal use and spending plans. They do not establish that either company has stopped offering Claude to customers. The supplied source says Microsoft continues to spend on Anthropic models for customer-facing Copilot features and that customer spending on Claude through Microsoft platforms is growing. Those details also come from reporting, not a company statement included here.
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 Existing Alternatives
The report matters because it shows how large AI buyers can respond when costs or budgets change: they can redirect work among suppliers and tools they already have. Meta and Microsoft are not typical customers. Meta develops its own models and coding products; Microsoft owns GitHub Copilot and is a major backer of OpenAI. Those investments give the companies options that many organizations have not built.
For other businesses, the price of a model is only part of the switching decision. Teams may need to rerun evaluations, adapt prompts and integrations, retrain employees, and account for new review or rework. The report offers no measured total for those costs, nor evidence that switching produced equal or better results. A lower token bill alone does not establish a lower cost per accepted task.
The practical implication is not that companies should automatically leave Claude. It is that they should know how dependent their workflows are on one model and whether another can handle the same tasks at acceptable quality. Maintaining a tested alternative may give a buyer negotiating leverage and a fallback, but doing so also takes engineering time and can add operating expense.
As an affiliate, we earn on qualifying purchases.
Why Both Companies Have Other Tools
Meta and Microsoft are both customers of AI providers and developers or backers of alternatives. That makes their internal choices different from a company with no in-house models, coding tools, or close supplier relationships. Using a product a company owns or supports can reflect integration and cost decisions; by itself, it is not evidence that a competing product failed.
The reported changes also concern different measures. Meta’s figure is the number of employees using Claude Code, while Microsoft’s is a reduction in a projected annual internal spending figure. Neither metric, on its own, shows how much work moved, how much was saved, or whether productivity changed. The source account says rising token costs and tighter spending controls were among the reported drivers, but gives no detailed cost comparison across tools.
The article’s source also cites a report from SemiAnalysis saying AI subscription limits can change and may vary by account. That observation is separate from the Meta and Microsoft reporting; it does not verify the details of either company’s internal decisions. For buyers, the broader issue is to track both usage terms and the work delivered, rather than treating a list price or user count as a complete measure of value.
“Meta reduced the number of employees using Claude Code from about 60,000 earlier this year to about 30,000.”
— The Information, as summarized in the supplied source
As an affiliate, we earn on qualifying purchases.
Performance and Savings Remain Unreported
The supplied reporting does not include direct statements from Meta or Microsoft explaining the changes, or independent performance comparisons between Claude and the tools taking on work. It remains unclear how much work was transferred, whether employees are still using Claude for selected tasks, and whether the changes affected output quality or productivity.
Microsoft’s stated-in-report spending figure is a projection, so the realized amount and the savings from lowering it are not established here. The source also mentions one account of monthly team budgets dropping from around $100,000 to around $10,000, but attributes that detail to a single report. Without further confirmation, it should not be treated as a company-wide policy or a verified measure of savings.
The supplied material does not establish that access to Claude has ended for either company or that customer-facing Claude use has been reduced. It reports the opposite for Microsoft’s customer-facing products: continued use of Anthropic models and growing customer spending through Microsoft platforms. The extent and timing of any future changes are unknown.
As an affiliate, we earn on qualifying purchases.
Watch for Usage and Cost Updates
Further reporting or statements from Meta and Microsoft could clarify the scope of the changes, the actual spending involved, and whether internal teams measured productivity or quality after switching. Any comparison will need to distinguish internal use from customer-facing services and projected budgets from realized expenses.
For organizations weighing a similar move, the relevant next step is to compare tools on representative work, including review time and rework as well as model charges. Keeping a small, evaluated alternative in use can make future changes easier, though it does not remove the costs of maintaining integrations and testing results. No company-specific timeline for further changes was provided in the supplied source.
As an affiliate, we earn on qualifying purchases.
Key Questions
Have Meta and Microsoft stopped using Claude?
The report describes reductions or changes in some internal use and planned spending, not a complete end to access. The supplied source says Microsoft continues to use Anthropic models in customer-facing Copilot features.
Why are the companies reportedly moving work?
The reported reasons include token costs, tighter spending controls and available alternatives. The supplied material does not report either company saying Claude performed worse.
Does the report prove that switching saves money?
No. Microsoft reportedly reduced a projected annual spending figure, but the actual savings and the costs of moving work were not established. A fair comparison would also account for quality, review time, rework and integration costs.
Should other companies switch away from Claude?
The report does not support a blanket recommendation. Meta and Microsoft have alternatives that many buyers lack. Other organizations would need to test their own tasks and weigh total operating costs and results before deciding.
Source: ThorstenMeyerAI.com
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
