Playbooks · Teams
Copilot CLI signs in with Microsoft Entra
Written November 18, 2026
GitHub Copilot CLI now signs in with Microsoft Entra in public preview: silent SSO for Enterprise Managed Users, or a Microsoft 365 Copilot license.
For a team whose people already sign in with Microsoft Entra all day, GitHub Copilot CLI asked for one more sign-in: a separate GitHub one, standing between the developer and the terminal. The GitHub Changelog post of November 17, 2026 removes that step for two distinct setups. Copilot CLI now supports Microsoft Entra authentication in public preview. A person can sign in with an Entra account to silently authenticate to a linked GitHub Enterprise Managed User account, use a Microsoft 365 Copilot licence, or both, depending on the organization's entitlements. Which of those paths applies is an admin question before it is a developer one, because each path carries different licences, policies, and billing.
The Enterprise Managed User path: silent single sign-on
For enterprises using Enterprise Managed Users through OIDC, the post says Copilot CLI now supports silent single sign-on using Microsoft Entra authentication. The developer accesses GitHub from Copilot CLI using the Entra identity, with no separate GitHub sign-in. Two conditions sit on the organization's side: the person must have an assigned Copilot Business or Copilot Enterprise licence, and the organization must enable the Copilot CLI policy.
On this path the CLI uses GitHub inference, and usage is governed by the organization's GitHub Copilot plan. In other words, Entra changes how the person signs in, not which plan pays for the work. The enterprise-side step the post names is enabling Enterprise Managed Authorization for the enterprise on GitHub Enterprise Cloud, and the post links its documentation for that step.
The scope is narrower than the headline suggests. The single sign-on experience is currently limited to Copilot CLI and VS Code, and only to enterprises using OIDC for Enterprise Managed Users. An enterprise that manages its users another way does not get this path yet, however tidy it would be.
The Microsoft 365 Copilot path: no GitHub account at all
The second path starts from a different licence entirely. If an organization is in Frontier and has a Microsoft 365 Copilot licence with usage-based billing, the post says Entra authentication lets people access the models available through that licence directly from the terminal. Here Copilot CLI uses Microsoft 365 inference rather than GitHub inference, and the person does not need a GitHub account.
That difference decides who manages what. Model access and usage limits are managed through the organization's Microsoft 365 Copilot settings, not GitHub. An admin looking for a usage limit in GitHub settings on this path is looking in the wrong console. The post also notes that the Work IQ MCP server can give Copilot access to Microsoft 365 work data as context, and links its overview for the details.
An organization can hold both entitlements at once. The post frames the choice as depending on the organization's entitlements, so a team may find some people arriving through the managed-user path and others through the Microsoft 365 licence, with different inference and limits behind what looks like the same sign-in screen.
Platforms, versions, and the limits to plan around
Microsoft Entra authentication for both managed users and Microsoft 365 Copilot is currently supported on Windows and macOS. Linux support will follow, in the post's words. A team with Linux developers should treat this as a partial rollout: those developers keep their existing sign-in until support lands, and an admin who announces one sign-in for everyone on day one will hear about it.
Getting started needs GitHub Copilot CLI version 1.0.113 or later. The post says the CLI can be updated by running copilot update in the terminal, and that the steps for enabling each capability in the CLI are provided in the Copilot CLI documentation, which the post links. What version a machine is running is therefore the first thing to check when Entra sign-in does not appear.
An admin's short checklist
- Work out which path each group uses. Managed users need an assigned Copilot Business or Copilot Enterprise licence and the Copilot CLI policy enabled. The Microsoft 365 path needs a Frontier organization and a licence with usage-based billing.
- Do the enterprise step for the managed-user path. Enable Enterprise Managed Authorization on GitHub Enterprise Cloud, following the documentation the post links.
- Set expectations by platform. Windows and macOS are covered now; Linux is not.
- Update before troubleshooting. Bring machines to version 1.0.113 or later with
copilot updatebefore chasing sign-in problems. - Keep the billing homes separate. GitHub inference follows the organization's GitHub Copilot plan; Microsoft 365 inference follows Microsoft 365 Copilot settings.
None of this changes what the CLI itself does release by release. The version history is covered separately in Copilot CLI 1.0.112: the November 13 build.
Related playbooks
- Microsoft 365 Copilot connectors can now write
- Copilot Agent Merge: watch a PR and fix its blockers
- The Copilot app now takes GHES accounts
- Copilot Automations learn from real outcomes
Sources
- GitHub Copilot CLI adds Microsoft Entra sign-in as a preview — GitHub Changelog — the Entra preview, the managed-user silent sign-on path and its licence and policy conditions, the Microsoft 365 Copilot licence path, platform support, and the version 1.0.113 requirement.
Back to: Teams playbooks hub · Also: Copilot CLI 1.0.112: the November 13 build