Hot AI News

Copilot CLI can now sign in with Entra, and bill Microsoft 365 instead of GitHub

GitHub Copilot CLI now takes a Microsoft Entra login in public preview, routing to GitHub inference or Microsoft 365 inference depending on the license. Windows and macOS only for now.

Copilot CLI can now sign in with Entra, and bill Microsoft 365 instead of GitHub
Image: Microsoft

Microsoft’s GitHub said GitHub Copilot CLI now supports Microsoft Entra sign-in in public preview. Depending on the employer’s licenses, one work login can reach a linked GitHub account, a Microsoft 365 Copilot license, or both.

Two licenses, two different back ends

The preview covers two scenarios, and which one applies depends on what the organization has bought. The first is for enterprises that use Enterprise Managed Users (EMU) through OIDC. There, a Microsoft Entra login silently authenticates the user to the linked EMU account, so no separate GitHub sign-in is needed. The user needs an assigned Copilot Business or Copilot Enterprise license, and the organization must switch on the Copilot CLI policy. In this case the CLI uses GitHub inference, and usage falls under the organization’s GitHub Copilot plan.

GitHub changelog header for the Copilot app Microsoft Ignite releases
Image: Microsoft

The second scenario is for organizations that are in Frontier and hold a Microsoft 365 Copilot license with usage-based billing. Entra sign-in then opens the models available through Microsoft Copilot from the terminal. The CLI uses Microsoft 365 inference, and no GitHub account is required. According to GitHub, model access and usage limits are then managed in the organization’s Microsoft 365 Copilot settings rather than on GitHub. Users can also attach the Work IQ MCP server, which gives Copilot access to Microsoft 365 work data as context.

Advertisements

Windows and macOS first, version 1.0.113 required

Entra authentication for both paths works on Windows and macOS today. GitHub says Linux support will follow but gives no date. The CLI must be at version 1.0.113 or later, and running copilot update upgrades an existing install. Step-by-step enablement for each capability sits in the Copilot CLI documentation, according to the post.

Copilot CLI can now sign in with Entra, and bill Microsoft 365 instead of GitHub
Image: Microsoft

The silent single sign-on for EMU is limited to Copilot CLI and VS Code, and only for enterprises that use OIDC for EMU. GitHub points administrators to its Enterprise Managed Authorization documentation for enabling the feature on GitHub Enterprise Cloud. The post does not say how long the preview will run, whether pricing changes at general availability, or which Microsoft 365 plans besides the usage-billed Frontier case qualify.

The terminal now has two inference paths

The notable technical change is not the login itself but what it decides. Until now, the CLI was tied to a GitHub identity and to GitHub’s own inference. With this preview, the identity token also selects where model calls run and who meters them. A GitHub-backed user draws on the organization’s Copilot plan. A Microsoft 365-backed user draws on tenant settings that an IT admin already manages in a different console. The same copilot command can therefore be governed by two separate sets of controls, which matters for anyone deciding which team owns the policy.

Copilot CLI can now sign in with Entra, and bill Microsoft 365 instead of GitHub
Image: Microsoft

That fits a pattern in the other Ignite-day posts. GitHub’s separate post on Microsoft Agent 365 says enterprises on GitHub Enterprise Cloud with EMU can stream Copilot activity, including from the CLI, into Agent 365, where admins can review prompts, responses and tool calls and pull in risk data from Microsoft Purview and Defender. A single Entra identity across CLI sessions makes that kind of audit trail easier to attribute to a person, though GitHub does not state this link in either post.

The CLI is also gaining capabilities that raise the stakes of identity. GitHub’s Copilot app release notes say browser use, which lets Copilot fill forms, read pages and test web apps in Chromium browsers, is in public preview and also available in Copilot CLI. It is off by default and needs the GitHub Copilot Chrome extension. We covered the app side of that release in our report on Azure DevOps pull requests and browser control.

Advertisements

What admins can and cannot assume yet

For a team on EMU with Copilot Business or Enterprise, the practical gain is one fewer login on Windows or macOS, provided the CLI policy is on. For a Frontier organization with usage-billed Microsoft 365 Copilot, the gain is bigger: developers without GitHub accounts can use a terminal agent, and spend lands on the Microsoft side.

The source leaves several things open. It does not list which models are reachable through Microsoft 365 inference, so parity with the GitHub model picker is unknown. It gives no usage limits or prices for the Microsoft 365 path. Linux, the platform many developers and CI machines run, is excluded for now. All behavior described is GitHub’s own account of a preview and has not been independently verified. Admins who already restrict what Copilot can load can look at the plugin-only customization policy, which applies to a separate layer of control.

Sign Up for the Daily AI Pulse

One email a day. All the stories that matter.

Leo MartinsAI Tools, Prompts & Practical AI Expert

Leo Martins is the AI Tools & Practical AI Expert at Aiholics, focused on helping readers use artificial intelligence to improve productivity, creativity and everyday work.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may also like