GitHub Copilot CLI has added Microsoft Entra sign-in in public preview
GitHub Copilot CLI has added Microsoft Entra sign-in in public preview — enabling silent SSO for GitHub Enterprise Managed Users as well as access to Microsoft 365 Copilot models without a GitHub account. Currently on Windows and macOS only, requiring CLI 1.0.113+.
GitHub has made Microsoft Entra sign-in available in GitHub Copilot CLI in public preview. The feature enables silent single sign-on (SSO) to a linked GitHub Enterprise Managed User (EMU) account or use of a Microsoft 365 Copilot license, or both options at once, depending on permissions in the given organization.
For enterprises using EMU via OIDC, Copilot CLI now supports silent SSO using a Microsoft Entra identity without the need for a separate GitHub sign-in. This requires an assigned Copilot Business or Copilot Enterprise license and the Copilot CLI policy enabled in the organization; in this mode the CLI uses GitHub inference and consumption is governed by the organization's GitHub Copilot plan. This SSO experience is currently limited to GitHub Copilot CLI and VS Code and is available only to organizations using OIDC for EMU.
For organizations in the Frontier program with a Microsoft 365 Copilot license and usage-based billing, signing in via Microsoft Entra enables access to models available through Microsoft Copilot directly from the terminal, without needing a GitHub account. In this scenario the CLI uses Microsoft 365 inference, and management of models and consumption limits takes place via the organization's Microsoft 365 Copilot settings, not via GitHub. Optionally, via the Work IQ MCP server, the Copilot tool can be given access to Microsoft 365 work data as context.
The feature is available on Windows and macOS, with Linux support to be added later. It requires GitHub Copilot CLI version 1.0.113 or higher; the update can be performed with the command copilot update.
Why it matters
For companies with GitHub Enterprise Managed Users, this simplifies access to Copilot CLI by removing duplicate sign-ins and centralizes identity management under Microsoft Entra. At the same time, organizations with a Microsoft 365 Copilot license gain an alternative path to models without being tied to a GitHub account, which may influence decisions about which platform (GitHub or Microsoft 365) is used to manage the tool's access and consumption.
Two audiences, two different impacts
What this means
For individuals
A user with a Microsoft Entra identity can sign in to GitHub Copilot CLI without a separate GitHub account, or alternatively use a Microsoft 365 Copilot license directly from the terminal.
For a business
Enterprises with GitHub Enterprise Managed Users via OIDC can simplify employee access to Copilot CLI thanks to silent SSO without a separate GitHub sign-in, and companies with a Microsoft 365 Copilot license (Frontier program, usage-based billing) can deploy the tool without requiring a GitHub account, with access control and limits moving to Microsoft 365 settings…
ProcessesCheck the original
Event sources
clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.