🔍 Read the full analysis: What’s Involved In Switching From Claude? Meta And Microsoft Weigh In 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 and Microsoft have reduced projected or actual internal use of Anthropic’s Claude tools, directing employees toward alternatives they already operate or back. The reported reasons are cost controls and available substitutes, not a stated finding that Claude performs worse; both companies are still reported to use Anthropic technology in some customer-facing products.
Meta and Microsoft are directing some employees away from Anthropic’s Claude tools and toward alternatives they already operate or support, according to an Oct. 5 report by The Information. The reported changes concern internal use and budgets, not an end to Claude access or a public decision to stop using Anthropic technology; the stated drivers are cost controls and available substitutes.
The Information reported that Meta reduced the number of employees using Claude Code from about 60,000 earlier this year to about 30,000. The report said Meta has steered engineers toward its own coding products: MetaCode, which it said has more than 30,000 internal users, and Muse Code, with more than 6,000. Those figures describe internal users, not external customers, and the report does not establish how the tools compare in performance.
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 said Microsoft later cut that projection by more than a third and directed employees toward GitHub Copilot and OpenAI models. A separate detail in the source material, attributed to a single report, says some monthly team budgets may have fallen from about $100,000 to about $10,000. The basis and scope of that budget figure are not independently established here.
The reported shift does not mean the companies have stopped using Claude. The source material says Microsoft continues to spend heavily on Anthropic models for some customer-facing Copilot features, while customer spending on Claude through Microsoft platforms is reported to be growing. The report describes internal deployment choices; it does not document a company-wide withdrawal or a change in access for customers.
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 technology companies can respond to rising AI costs: they can redirect work to tools already built, deployed or backed internally. Meta and Microsoft are not typical buyers. Both have substantial engineering capacity and credible alternatives, giving them more room to move than an organization dependent on a single vendor. The reported usage changes are evidence of procurement and deployment choices, not proof that switching is easy for other companies.
For most organizations, a model change can require more than changing an API setting. Teams may need to rerun evaluations, adjust prompts and tool definitions, rebuild integrations and train staff on different behavior. They also need to check whether the replacement delivers acceptable results on their own tasks. Costs can include extra review and rework, not just model charges; the report does not quantify those effects for Meta or Microsoft.
The source material also argues that model routing—sending different tasks to different providers—can limit dependence on any one supplier. That is a proposed operating approach, not a confirmed explanation of the two companies’ decisions. Their moves may be easier because they already have substitutes. A company without such tools may face significant work and quality risks before any price savings become real.
As an affiliate, we earn on qualifying purchases.
Internal Use Is Not Customer Withdrawal
The distinction between employee use and customer products is central to understanding the report. It describes Meta and Microsoft changing how their own workers use coding assistants and models. Microsoft’s reported spending projection includes several Anthropic products and use cases, while the source material says Anthropic models remain part of some customer-facing Copilot features. A reduction in one category should not be treated as evidence that every relationship or product integration has ended.
Both companies also have interests in alternatives. Meta develops its own AI models and coding tools. Microsoft owns GitHub Copilot and has a major relationship with OpenAI. That makes internal substitution commercially plausible, but it does not by itself show that Claude was inferior. The source material says the reported reasons were cost, spending controls and in-house tools; it does not report a quality-based verdict from either company.
The available figures have different meanings: Meta’s numbers concern reported employee usage, while Microsoft’s concern a spending projection and subsequent reduction. They should not be combined as a single measure of adoption or treated as audited company-wide totals. The article’s underlying information comes from The Information’s report as summarized in the supplied source material.
Performance and Final Spending Remain Unclear
The supplied material does not include direct statements from Meta, Microsoft or Anthropic confirming the figures or explaining the decisions. The reported reasons include costs and tighter budgets, but the companies’ own accounts are not provided. It is also unclear how the companies measured the usefulness or quality of the replacement tools, or how much employee work was actually transferred.
Microsoft’s reported figure is a projection, and the source does not specify the final annual amount or the precise period covered by the reduction. The reported monthly team-budget changes come from one account and lack detail about which teams they cover. Meta’s user counts likewise do not show how often employees use each product, how many remain active, or whether access varies by team.
The effects on customer-facing services are also not fully detailed. The source material says Microsoft continues to use Anthropic models for some Copilot features and that customer spending through its platforms is growing, but gives no figures or timeframe. Nothing in the available account confirms that Claude access has been withdrawn from employees or customers.
Watch for Confirmed Usage and Costs
The next useful evidence would be direct company confirmation of the reported usage and spending changes, including the relevant time periods and definitions. Any updated figures could clarify whether these are targeted adjustments, broader internal policy changes or changes in projected budgets that have not yet translated into actual spending.
For buyers, the practical next step is to compare alternatives on representative work before shifting large workloads. That means tracking both model charges and the time needed for review, correction and integration. The report does not provide a timeline for further changes at either company, so whether their internal shifts expand—or affect customer-facing products—remains unknown.
Key Questions
Are Meta and Microsoft ending their use of Claude?
No such company-wide exit is confirmed. The report concerns internal employee use and spending projections. The source material says Microsoft continues to use Anthropic models for some customer-facing Copilot features.
Why are the companies reportedly shifting some work?
The reported reasons are rising costs, tighter spending controls and existing alternatives. The supplied material does not say either company concluded that Claude performs worse.
What did Meta reportedly change?
The Information reported that Meta’s Claude Code user count fell from about 60,000 earlier this year to about 30,000, with employees directed toward MetaCode and Muse Code. These are reported internal-use figures.
What did Microsoft reportedly change?
Microsoft reportedly cut by more than a third a projection of over $1 billion a year in internal Anthropic spending and steered employees toward GitHub Copilot and OpenAI models. The projection is not a confirmed final spending total.
What can other companies learn from the report?
Having alternatives ready may make it easier to shift AI workloads, but switching can involve evaluation, integration and staff costs. The report does not establish that every company will save money by changing providers; buyers need to test replacement tools on their own work.
Source: ThorstenMeyerAI.com
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
