Back to News
EnterpriseAI Understanding briefing

Meta and Microsoft slash Claude spending, pivot to in‑house AI tools

Meta and Microsoft, two of Anthropic’s biggest enterprise customers, have sharply reduced internal use of Claude, cutting budgets by more than a third and shifting to their own AI offerings such as GitHub Copilot, Muse Code and MetaCode.

4 min readRead the linked source
Source-provided image accompanying Meta and Microsoft slash Claude spending, pivot to in‑house AI tools
Source referenceSource recorded
Publisher
the-decoder.com
Source link
the-decoder.comhttps://the-decoder.com/meta-and-microsoft-pull-back-from-claude-as-anthropic-transforms-from-partner-into-competitor/
Source type
Linked source — primary-source status has not been established.
ContextUnderstand this in 60 seconds

Start here

Test yourselfAI Models Explained Quiz

What happened

Meta and Microsoft are dramatically scaling back internal deployments of Anthropic’s Claude. According to reporting by The Information, Microsoft’s cloud division cut its per‑employee Claude budget from roughly $100,000 to about $10,000, a reduction of more than 90 % and a cut of over a third of its projected annual spend that had been estimated at more than $1 billion. At Meta, the number of employees using Claude Code fell from roughly 60,000 to 30,000 within weeks, and a 28‑day period saw Meta spend over $105 million on Claude Code alone. The decline is attributed to a combination of recent layoffs, cost‑cutting measures introduced in June, and a strategic push toward Meta‑developed tools such as Muse Code and MetaCode. Executives Scott Guthrie and Jay Parikh at Microsoft have instructed staff to favor in‑house solutions like GitHub Copilot and OpenAI models, while Meta’s internal communications emphasize the company’s own AI stack.

The Information reports that Microsoft’s cloud division, which had projected annual Claude spend exceeding $1 billion, instructed staff to replace Claude with internal tools. The per‑employee budget was slashed from $100,000 to roughly $10,000, representing a cut of more than a third of the originally forecast spend.

At Meta, internal usage of Claude Code dropped from about 60,000 users to 30,000 within a short period. In a single 28‑day window, Meta’s spend on Claude Code topped $105 million, reflecting both high prior usage and the rapid scale‑back that followed cost‑cutting measures announced in June.

Both companies cited cost savings as a primary driver, but internal memos suggest strategic motives as well: Microsoft wants to consolidate AI work under its own Azure‑OpenAI partnership, while Meta is promoting its Muse Code and MetaCode products and appears intent on limiting Anthropic’s access to Meta‑generated training data.

Source details: the-decoder.com ↗

Why it matters

The pull‑back by Meta and Microsoft—Anthropic’s two largest enterprise customers—has immediate revenue implications for Anthropic, whose business model relies heavily on high‑value corporate contracts. A reduction of this magnitude could pressure Anthropic to reassess pricing, accelerate product differentiation, or seek new customers to offset lost spend. Strategically, the shift underscores a broader trend where tech giants are consolidating AI capabilities within their own ecosystems to reduce dependence on external providers and protect proprietary data. For the industry, the move signals heightened competition among large‑scale AI platforms (Claude, OpenAI, GitHub Copilot) and may accelerate the development of internal AI tooling across other enterprises. It also raises questions about data‑sharing arrangements, as Meta reportedly wants to limit Anthropic’s access to its training data, highlighting emerging concerns over data ownership in AI collaborations.

Revenue Impact: Anthropic’s financial health is closely tied to large‑scale contracts. A multi‑hundred‑million‑dollar reduction from two flagship customers could affect quarterly earnings and valuation.

Competitive Landscape: The shift illustrates how dominant cloud and social media firms are building self‑sufficient AI stacks, potentially reducing market share for third‑party providers like Anthropic.

Data Governance: Meta’s reported desire to restrict Anthropic’s access to its data highlights growing concerns over data ownership and the strategic value of proprietary training datasets in AI development.

Industry Signal: Other enterprises may follow suit, evaluating whether to continue licensing external AI models or to invest in building comparable in‑house solutions.

Interactive Mechanism

Interactive Mechanism: How It Actually Works

Explore the underlying technology behind this development interactively.

Agent Lifecycle Stage:
1
User Intent & Planning: "Audit customer refund request #4092 and settle payment."
2
Tool Calling: Emits structured JSON call crm_get_transaction(id='4092').
3
Guardrail & Verification:🛡️ Paused: High-value action requires human operator sign-off.
4
Final Settlement: Refund recorded, email receipt dispatched, and audit log stored.
Core takeaway: An AI agent is not just a language model—it is a closed loop of planning, tool invocation, and environment feedback. Production systems require self-healing retries and strict human approval guardrails.
Interactive Concept Check+10 Points
AI Models Explained Quiz

Which component of an AI application is the machine-learning model itself?

What to watch next

Key signals to monitor include Anthropic’s response—whether it will adjust pricing, introduce new features, or seek alternative enterprise partners. Watch for any public statements from Microsoft or Meta about long‑term AI strategy, especially regarding the rollout of GitHub Copilot and Meta’s Muse/MetaCode suites. Analysts will also track Anthropic’s quarterly revenue reports for evidence of the financial impact. Finally, any regulatory scrutiny over data‑sharing agreements between AI providers and large tech firms could shape future partnership models.

Anthropic’s next public statements on pricing, product roadmap, or new enterprise partnerships.

Microsoft’s rollout timeline for GitHub Copilot and OpenAI models within Azure, and any official commentary on the decision to de‑prioritize Claude.

Meta’s product announcements for Muse Code, MetaCode, and related AI developer tools, including pricing and availability.

Regulatory developments concerning data‑sharing agreements between AI providers and large tech platforms, which could affect future collaborations.

Related guides & quizzes

AI Models ExplainedAI AgentsAI EthicsTest what you know — try a free AI quizLook up an AI term in our glossaryFollow the AI funding tracker
Found this useful?