Free Intensive Nov 21–22Free 2-day hands-on Vibecoding Intensive on Nov 21–22 at 16:00 MSK (Sat–Sun) · Live Cohort 3 starts Nov 23Join Free →Cohort 3 (Nov 23)
ReleaseInsight · On RadarGitHub Changelog→ original

GitHub Copilot CLI Adds Sign-In via Microsoft Entra Without a Separate GitHub Login

GitHub Copilot CLI now accepts Microsoft Entra work accounts, so you no longer need a separate GitHub login. In companies with Enterprise Managed Users, sign-in happens silently through SSO and uses the organization's plan. With a Microsoft 365 Copilot license, the terminal runs on Microsoft's models without a GitHub account. For now this is a preview for Windows and macOS, so admins should check their policies first.

AI-processed from GitHub Changelog; edited by Hamidun News
GitHub Copilot CLI Adds Sign-In via Microsoft Entra Without a Separate GitHub Login
Source: GitHub Changelog. Collage: Hamidun News.
Listen to article
Article Fact Sheet & Key Figures
ParameterDetails
Primary sourceGitHub Changelog ↗
Editor-in-Chief
Key metric #1Linux support is promised later; only Windows and macOS work right now
Key metric #2SSO for EMU requires a Copilot Business or Enterprise license and OIDC
Key metric #3The Work IQ MCP server gives Copilot context from Microsoft 365 work data

Enterprise developers know the pain: to run an AI assistant in the terminal, you have to go through one more authorization, then another. GitHub is removing part of that friction. Copilot CLI now supports sign-in via Microsoft Entra, and the feature has entered public preview.

What Changed

Previously, using Copilot CLI meant signing in to GitHub separately. Now you can authenticate with your Microsoft Entra work account. From there, the setup depends on what your organization allows: signing in to a linked GitHub Enterprise Managed User (EMU) account, using a Microsoft 365 Copilot license, or both at once.

Windows and macOS are supported for now. Linux support is promised later, and that is a notable limitation: many developers work in the terminal on Linux, including on servers and in containers.

Scenario One: Silent SSO for EMU

In the first scenario, Copilot CLI signs in to GitHub through your Entra identity, with no separate login window. This is called silent SSO. The requirements are:

  • you are assigned a Copilot Business or Copilot Enterprise license;
  • your organization has enabled the relevant Enterprise Managed Authorization policy on GitHub Enterprise Cloud;
  • the enterprise uses OIDC for EMU.

In this mode, Copilot CLI runs on GitHub inference, and usage is governed by your organization's Copilot plan. For admins, this means billing, limits, and model access stay where they were. Only the sign-in method changes. Silent SSO is currently available only in Copilot CLI and VS Code, so the login remains unchanged in other Copilot clients.

Scenario Two: Microsoft 365 Copilot License

The second scenario is more interesting. If your organization is enrolled in the Frontier program and holds a Microsoft 365 Copilot license with pay-as-you-go billing, Entra can give you access to the models available in Microsoft Copilot directly in the terminal. No GitHub account is needed.

Here, too, the resource accounting changes. Copilot CLI uses Microsoft 365 inference, not GitHub's. Model access and limits are set in your organization's Microsoft 365 Copilot settings, not in GitHub. If IT used to manage AI spending across two consoles, a single console now covers part of the workforce.

GitHub also mentions the Work IQ MCP server. It gives Copilot access to Microsoft 365 work data as context. For example, a terminal assistant can take into account email, documents, and meetings related to a task, not just the code in a repository. The announcement does not detail which data is accessible or with what permissions, so read the documentation and align with your security team before enabling it.

What to Do in Practice

You need a recent version of Copilot CLI. You can update it with the CLI's usual command, and step-by-step instructions for each scenario are in the documentation. We recommend this order:

  1. Determine how your Copilot is licensed: through GitHub (Business or Enterprise) or through Microsoft 365 Copilot.
  2. Verify that EMU runs over OIDC and that the Enterprise Managed Authorization policy is enabled.
  3. Start with a pilot group on Windows or macOS and compare the sign-in experience with your current one.
  4. Decide in advance whose limits and whose models you want to use for terminal tasks.

Here are the honest caveats. This is a preview, so behavior and requirements may change. Linux support is not yet available. Silent SSO is limited to two clients and only the OIDC variant of EMU. In addition, the source does not specify the minimum CLI version; check the documentation for that.

The main takeaway for teams: AI tools in the terminal are becoming part of corporate identity. Sign-in, spending oversight, and access control are moving into the familiar Entra infrastructure. For those already living in the Microsoft ecosystem, this removes an extra login and simplifies administration. Others may have to wait for broader support.

Story

Key Questions Answered

What Changed?

Previously, using Copilot CLI meant signing in to GitHub separately. Now you can authenticate with your Microsoft Entra work account. From there, the setup depends on what your organization allows: signing in to a linked GitHub Enterprise Managed User (EMU) account, using a Microsoft 365 Copilot license, or both at once. Windows and macOS are supported for now. Linux support is promised later, and that is a notable limitation: many developers work in the terminal on Linux, including on servers and in containers.

What are the key details on Scenario One: Silent SSO for EMU?

In the first scenario, Copilot CLI signs in to GitHub through your Entra identity, with no separate login window. This is called silent SSO. The requirements are: you are assigned a Copilot Business or Copilot Enterprise license; your organization has enabled the relevant Enterprise Managed Authorization policy on GitHub Enterprise Cloud; the enterprise uses OIDC for EMU. In this mode, Copilot CLI runs on GitHub inference, and usage is governed by your organization's Copilot plan.

What are the key details on Scenario Two: Microsoft 365 Copilot License?

The second scenario is more interesting. If your organization is enrolled in the Frontier program and holds a Microsoft 365 Copilot license with pay-as-you-go billing, Entra can give you access to the models available in Microsoft Copilot directly in the terminal. No GitHub account is needed. Here, too, the resource accounting changes. Copilot CLI uses Microsoft 365 inference, not GitHub's. Model access and limits are set in your organization's Microsoft 365 Copilot settings, not in GitHub.

ZK
Zhemal Khamidun — CPO at Alpina Digital, product manager of AlpinaGPT. Building AI products since 2019. Hamidun News is a pet project that grew into a production aggregator with 6,000+ readers.
✦ Hands-On AI Engineering · Hamidun Academy

Build & Ship Production AI Agents Without Boilerplate Code

Start your free 72-hour trial at Hamidun Academy (academy.hamidun.com) — interactive lessons on Claude Code & Cursor, live Tech Radar, and production agent templates.

Start 72h Free Trial →Vibe-Coding Intensive
What do you think?
Loading comments…