Redmond: Microsoft is reportedly encouraging many of its engineers to reduce their use of Anthropic’s Claude Code and transition to GitHub Copilot CLI, marking a significant shift in the company’s internal AI coding strategy. The move is expected to affect developers within Microsoft’s Experiences + Devices division, which oversees major products including Windows, Microsoft 365, Teams, Outlook and Surface.

According to reports, Microsoft plans to scale back access to Claude Code by the end of June 2026 as it increases its focus on GitHub Copilot CLI, an AI-powered coding assistant developed within its own ecosystem.

Microsoft doubles down on Copilot CLI

Microsoft initially introduced Claude Code to thousands of employees in 2025 as part of its broader push to integrate artificial intelligence into software development workflows. The tool quickly gained traction among developers for coding assistance, prototyping, debugging and workflow automation.

However, the company’s latest directive signals a change in priorities.

GitHub Copilot CLI, a command-line version of GitHub Copilot, is now being positioned as Microsoft’s preferred AI coding assistant. Unlike traditional coding assistants integrated directly into development environments, Copilot CLI operates through the terminal, allowing developers to interact with AI during various stages of software development.

By encouraging employees to adopt its own platform, Microsoft hopes to strengthen internal usage, improve product feedback loops and accelerate development of Copilot CLI.

Why developers reportedly preferred Claude Code

One of the challenges Microsoft may face is that many engineers reportedly developed a preference for Claude Code during internal testing.

Employees were previously encouraged to compare Claude Code with GitHub Copilot CLI and provide feedback on their experiences. Reports suggest that Claude Code earned praise for its coding accuracy, ease of use and ability to assist with complex development tasks.

Developers reportedly found the tool particularly useful for generating code, explaining technical concepts and assisting with rapid prototyping.

This popularity has led to speculation that the transition may not be universally welcomed among Microsoft’s engineering teams.

The official reason: Cost and strategic focus

The most visible explanation for the move is Microsoft’s effort to consolidate its AI tooling and reduce operational expenses.

Running multiple AI coding platforms across thousands of employees can be expensive, especially when external AI providers are involved. By encouraging greater adoption of GitHub Copilot CLI, Microsoft can direct resources toward improving its own product while potentially lowering licensing costs.

The strategy also aligns with Microsoft’s broader ambition to establish GitHub Copilot as a leading AI coding platform globally.

Internal adoption often serves as a valuable testing ground for software companies. Engineers who use the tool daily can identify bugs, suggest features and help refine performance before updates reach customers.

The unofficial reason: Competition in the AI race

Industry observers believe there may be another factor behind the decision.

Claude, developed by Anthropic, has increasingly been viewed as one of the strongest competitors to AI models from OpenAI and Microsoft’s own AI offerings. Claude’s coding capabilities have received positive reviews from developers, leading some organisations to adopt it for software engineering tasks.

By encouraging engineers to spend more time using Copilot CLI, Microsoft can gather valuable feedback and improve its own AI coding ecosystem while reducing reliance on a rival platform.

This does not mean Microsoft is ending its relationship with Anthropic. Reports indicate that Claude models will remain accessible through GitHub Copilot CLI alongside OpenAI models and Microsoft’s internal AI systems.

What this means for Microsoft’s AI strategy

The decision highlights how major technology companies are increasingly seeking to control their AI infrastructure and development tools.

Rather than depending heavily on third-party AI coding assistants, Microsoft appears focused on building a unified ecosystem around GitHub Copilot. The company is betting that stronger internal adoption will help improve the platform and make it more competitive in a rapidly evolving market.

At the same time, the continued availability of Claude models within Copilot suggests Microsoft is not completely shutting the door on external AI technologies. Instead, it is aiming to make Copilot the central hub through which developers access multiple AI models.

Conclusion

Microsoft’s push away from Claude Code appears to be driven by a combination of business strategy, cost considerations and product development goals. While many developers reportedly favour Claude Code for certain tasks, Microsoft is investing heavily in GitHub Copilot CLI and wants its engineers to play a larger role in shaping the future of its in-house AI coding platform. The move reflects the growing competition among AI companies as they race to become the preferred assistant for software developers worldwide.