Skip to content

GitHub Copilot CLI adds Microsoft Entra sign-in preview

Enterprises using managed users or Microsoft 365 Copilot licenses can now authenticate the CLI through Microsoft Entra, with Linux support still to come.

Draftship Editorial3 min read

What GitHub shipped on November 17

GitHub Copilot CLI now accepts Microsoft Entra authentication, in public preview, according to GitHub's changelog entry for the release. The Microsoft Entra sign-in for Copilot CLI covers two separate situations: signing in to a linked GitHub Enterprise Managed User (EMU) account, using a Microsoft 365 Copilot license, or both, depending on what an organization is entitled to. Entra authentication for both cases works on Windows and macOS, and GitHub says Linux support will follow.

Version 1.0.113 or later is required. The CLI can be updated by running copilot update in a terminal, and the per-capability setup steps live in the GitHub Copilot CLI documentation.

Two paths, two different billing models

The EMU path is about single sign-on. For enterprises running EMUs through OIDC, Copilot CLI supports silent SSO with a Microsoft Entra identity, so a developer reaches GitHub from the terminal without a separate GitHub sign-in. The conditions are specific: an assigned Copilot Business or Copilot Enterprise license, plus the organization enabling the Copilot CLI policy. In this mode the CLI uses GitHub inference and usage falls under the organization's GitHub Copilot plan. GitHub notes the SSO experience is limited to Copilot CLI and VS Code, and only for enterprises using OIDC for EMU. Enabling Enterprise Managed Authorization on GitHub Enterprise Cloud is done through GitHub's documentation.

The Microsoft 365 path is different in kind. If an organization is in Frontier and holds a Microsoft 365 Copilot license with usage-based billing, Entra authentication lets people reach models available through Microsoft Copilot from the terminal. Here the CLI uses Microsoft 365 inference rather than GitHub inference, and a GitHub account is not required. Model access and usage limits are governed by the organization's Microsoft 365 Copilot settings, not GitHub. GitHub also points to the Work IQ MCP server as a way to give Copilot access to Microsoft 365 work data as context.

What changes for teams building apps

Identity is usually the friction point when rolling a coding tool out across an enterprise. An EMU shop that already runs OIDC can now let developers use the CLI under their existing corporate identity, which reduces a separate credential to manage and keeps usage attributed to the GitHub Copilot plan the company already pays for.

The Microsoft 365 route matters for a different reason: it decouples terminal access to models from having a GitHub account at all. A team whose commercial relationship is with Microsoft rather than GitHub can, in the Frontier and usage-based billing case the source describes, reach those models from the command line and have consumption tracked in Microsoft's settings.

Limits and open questions

The source is narrow. It does not say when Linux support arrives, what the Frontier program requires beyond the license and billing arrangement mentioned, or which specific models the Microsoft 365 path exposes. It also does not describe how the two inference paths behave if an organization qualifies for both, beyond saying usage follows the relevant plan. Nothing in the announcement covers pricing, seat counts, or whether the preview has an end date. Whether the Entra sign-in changes anything for individual Copilot subscribers is not stated; the described scenarios are all organizational.

What this suggests for AI-assisted building

This is enterprise plumbing rather than a new capability for the models themselves. The pattern it signals is that access to coding agents is increasingly tied to whichever identity and billing system a company already runs, and that vendors are willing to let inference be billed by a party other than themselves. For a developer building an app with AI, the practical read is that tool access will keep arriving through corporate single sign-on rather than personal accounts, which is worth knowing when you plan how a team shares tooling. If you are putting together your own app and want to see how sign-in and hosting are handled in one place, Draftship's docs on managing login and registration cover the built-in option. Draftship is not affiliated with GitHub or Microsoft, and this announcement does not mention it.

Primary sources

This article was drafted with AI assistance from the primary sources listed below and checked automatically against them. An editor hasn't reviewed it yet.