Skip to main content
GPUBeat Frontier Models Microsoft Shifts Focus from Anthropic’s Claude…

Microsoft Shifts Focus from Anthropic’s Claude Code to GitHub Copilot CLI

Microsoft plans to phase out Anthropic's Claude Code in favour of its own GitHub Copilot CLI, emphasising internal tool standardisation and cost reductions.

A significant pivot is underway at Microsoft as the company prepares to scale back its reliance on Anthropic's AI coding tool, Claude Code. This decision reflects a push to unify development processes around GitHub Copilot CLI, which is set to become the primary command line interface for AI-assisted coding within the organization.

Microsoft first introduced access to Claude Code in December, attracting a diverse group of employees, including those without extensive coding backgrounds, to explore AI-enhanced programming. The tool quickly gained popularity among engineers and project managers. However, recent reports indicate that Microsoft plans to eliminate most Claude Code licenses, particularly within its Experiences + Devices division, which includes key platforms like Windows, Microsoft 365, Outlook, Teams, and Surface.

Transitioning to GitHub Copilot CLI

Sources suggest that this transition is expected to be completed by the end of June, aligning with the conclusion of Microsoft's financial year, a timing factor believed to influence this shift. Engineers are being encouraged to start using GitHub Copilot CLI in the coming weeks as part of this strategic realignment. Rajesh Jha, Executive Vice President of Microsoft's Experiences and Devices group, noted in an internal memo that the initial intent behind offering both tools was to evaluate their effectiveness in real-world engineering scenarios.

By consolidating around Copilot CLI, Microsoft aims to create a more tailored product that aligns with its development workflows, security protocols, and engineering requirements. Jha stated, "a product we can help shape directly with GitHub for Microsoft’s repos, workflows, security expectations, and engineering needs."

Cost Considerations and Developer Preferences

In addition to the push for standardization, cost-cutting measures appear to influence Microsoft's decision-making. The end of the financial year often prompts companies to reassess expenditures, and the shift away from Claude Code may align with broader budgetary constraints. Notably, despite the popularity of Claude Code among developers in recent months, Microsoft’s strategic focus seems to be shifting toward its own solutions, reinforcing its position in AI development.

See also  Anthropic and Gates Foundation Launch $200M Initiative for AI in Health

Previously, Microsoft considered acquiring the AI coding startup Cursor to enhance GitHub Copilot. However, concerns over potential regulatory scrutiny led to a pivot towards engaging with other AI startups instead.

Implications for AI Development at Microsoft

This transition indicates a broader trend within Microsoft toward integrating its AI tools more closely with existing services, thereby simplifying development and enhancing efficiency. As the company prioritizes its own Copilot CLI, it reflects a commitment to building innovation within its engineering teams while navigating a competitive market.

Moving forward, Microsoft's focus on standardizing its AI tools is likely to influence its development culture and capabilities. By emphasizing in-house solutions, the tech giant aims to create a more cohesive and efficient ecosystem for its developers, ultimately shaping the future of its AI offerings.

Quick answers

What tools is Microsoft prioritising over Claude Code?

Microsoft is shifting its focus to GitHub Copilot CLI as its primary AI coding tool.

Why is Microsoft phasing out Claude Code?

The decision is part of an effort to standardise tools and implement cost-cutting measures.

When is the transition expected to be completed?

The transition away from Claude Code is expected to be completed by the end of June.

GD

GPUBeat Desk

Desk · joined 2026

GPUBeat Desk covers AI infrastructure — chips, foundation models, inference economics, datacenter buildouts, and the geopolitics of compute.