Microsoft cancels Claude Code licenses and shifts developers to Copilot CLI

Yesterday 14:40

By: Dakir Madiha

Microsoft cancels Claude Code licenses and shifts developers to Copilot CLI

Microsoft has begun cancelling licenses for Claude Code across parts of its engineering organization and is directing developers toward GitHub Copilot CLI. The move affects teams within its Experiences and Devices division, which includes major products such as Windows, Microsoft 365, Outlook, Teams, and Surface. The decision marks a rapid reversal from earlier internal adoption of Anthropic’s coding tool.

The company had previously rolled out Claude Code to several engineering groups, including large internal software teams, and encouraged broader experimentation across technical and non-technical roles. Employees were asked to compare Claude Code with GitHub Copilot and provide feedback on performance and workflow integration. At the time, the strategy reflected an open evaluation of competing AI coding assistants.

Microsoft is now phasing out most Claude Code access and instructing engineers to transition their workflows to Copilot CLI in the coming weeks. The Experiences and Devices division is expected to complete the transition by the end of June. The timeline aligns with the end of Microsoft’s fiscal year, a period often associated with operational restructuring and cost adjustments.

The shift also reflects a broader consolidation strategy around Microsoft’s own AI coding ecosystem. GitHub Copilot CLI is being positioned as the primary command line tool for development workflows, integrating multiple model providers within a single environment. While Anthropic’s models will remain available through Copilot CLI, direct reliance on Claude Code is being reduced.

The decision highlights increasing competition in AI-assisted software development tools, where companies balance access to best-in-class external models with the need for platform control and cost predictability. Microsoft’s earlier adoption of Claude Code signaled gaps in its own tooling, while the current rollback suggests a priority shift toward tighter integration and internal product alignment.