A developer works at a laptop beside a diagram of admin-controlled access to Copilot tools and cloud inference.
GitHub is giving the Copilot CLI a new front door. As of November 17, 2026, GitHub Copilot CLI supports Microsoft Entra authentication in public preview. Developers in Entra-managed organizations can sign in with their work identity instead of going through a separate GitHub login, as long as their organization has the right entitlements.

The headline sounds like one feature, but it's really two. One path is single sign-on into a GitHub Enterprise Managed User (EMU) account. The other lets you use a Microsoft 365 Copilot license from the terminal. They run on different inference back ends, use different billing, and are run by different admin teams. If you skip that detail, expect some confused help-desk tickets.

A developer works at a laptop beside a diagram of admin-controlled access to Copilot tools and cloud inference. What GitHub announced​

According to GitHub's changelog, signing in with an Entra account can do one or both of these things, depending on what your organization is licensed for:

  • Silently authenticate to a linked GitHub EMU account, or
  • Use your Microsoft 365 Copilot license to access models from the terminal.

Here are the basic limits:

  • Platforms: Both scenarios currently work on Windows and macOS. GitHub says Linux support will come later.
  • Version: You need Copilot CLI 1.0.113 or later. To update, run copilot update.
  • Status: This is a public preview. GitHub's documentation says Entra use with Copilot CLI is subject to change.

The installation docs have already been updated for the new option. On first launch, the CLI tells users to run the /login slash command and follow the on-screen instructions to authenticate with your GitHub account or your Microsoft Entra account.

One note for Windows users: GitHub's general CLI documentation lists Windows support from both PowerShell and Windows Subsystem for Linux. Since GitHub has said Linux support for Entra sign-in is still coming, don't assume it works inside a WSL distro yet. The changelog doesn't address WSL directly, so test it before you promise it to your developers.

Section summary: This is a public preview on Windows and macOS, you need CLI 1.0.113 or later, and there are two separate paths.

Path one: EMU single sign-on (GitHub inference)​

This path is for enterprises that connect GitHub Enterprise Managed Users to Entra using OIDC. Users who qualify get silent SSO. They reach GitHub from the CLI with their Entra identity and don't need a separate GitHub sign-in.

GitHub lists these requirements:

  1. Your Entra tenant uses OIDC to connect to GitHub EMU. SAML-based EMU setups don't qualify for this preview.
  2. The user has an assigned Copilot Business or Copilot Enterprise license.
  3. The organization has enabled the Copilot CLI policy.

On this path, the CLI uses GitHub inference, and usage is governed by the organization's GitHub Copilot plan. GitHub says the SSO experience currently works only in Copilot CLI and VS Code. Admins who need to turn it on are pointed to GitHub's Enterprise Managed Authorization documentation for GitHub Enterprise Cloud.

Section summary: If you're an OIDC-backed EMU shop with Copilot Business or Enterprise seats and the CLI policy enabled, the login step goes away. Billing and governance stay with GitHub.

Path two: Microsoft 365 Copilot models (Microsoft 365 inference)​

The second path matters more strategically. If your organization is in Microsoft's Frontier program and has a Microsoft 365 Copilot license with usage-based billing, Entra sign-in lets you use models available through Microsoft Copilot straight from the terminal. On this path:

  • The CLI uses Microsoft 365 inference, not GitHub inference.
  • You don't need a GitHub account.
  • Model access and usage limits are controlled in your organization's Microsoft 365 Copilot settings, not in GitHub.

GitHub's authentication documentation lists the admin setup in the Microsoft 365 admin center:

SettingWho can enable it
Microsoft Copilot Code spending policy (usage-based billing)Billing Administrator or Global Administrator
Copilot Frontier settingAI Administrator or Global Administrator
GitHub Copilot access (Frontier), off by defaultGlobal Administrator

The third row is the one to watch. Because that setting starts disabled, a licensed Frontier tenant won't get this feature until a Global Administrator turns it on.

Work IQ comes along​

GitHub's changelog also mentions the Work IQ MCP server, which can give Copilot your Microsoft 365 work data as context. GitHub's CLI documentation says signing in with a Microsoft 365 Copilot account makes Work IQ available, and Work IQ usage is charged to the Microsoft Copilot Code spending policy.

Microsoft's own Work IQ quickstart for Copilot CLI describes the access model. Once connected, Copilot can discover Work IQ MCP tools, authenticate with Microsoft Entra ID, and use those tools to work with Microsoft 365 data according to the signed-in user's permissions and tenant policy. Microsoft also says users can ask the CLI to retrieve Microsoft 365, Power Platform, and Dynamics 365 business data through Work IQ. In other words, the agent only sees what the signed-in user can already see. Whether that reassures you depends on how clean your SharePoint permissions are.

Section summary: Frontier tenants with usage-based Microsoft 365 Copilot billing get terminal access to Microsoft's models without a GitHub account. Admins in the Microsoft 365 admin center control access, and the GitHub Copilot access (Frontier) setting starts off.

How to sign in​

GitHub's documentation describes a short process:

  1. Update the CLI: Run copilot update and confirm you're on 1.0.113 or later.
  2. Start the CLI: Run copilot, then type /login.
  3. Choose the account type. The prompt lists GitHub.com, GitHub Enterprise Cloud with data residency (*.ghe.com), and Your organization (Microsoft Entra). Pick the Entra option, and the CLI signs you in with your existing Entra account automatically.
  4. Check the result: Open the /model picker. The docs say models allowed by your entitlements should appear there.

If no Entra-backed models show up, check these first: the CLI version, the operating system (Linux isn't supported yet), whether your EMU setup uses OIDC rather than SAML, whether the Copilot CLI policy is enabled, and, for the Microsoft 365 path, whether a Global Administrator has turned on the GitHub Copilot access (Frontier) setting.

The project's recent release notes suggest the sign-in flow is still being tidied up. One recent entry says GitHub will avoid unnecessary error popups during Microsoft Entra sign-in when an organization account is available. Another says copilot workflow run --help now lists a Microsoft 365 account among the sign-ins that can run workflows. If you see odd error dialogs, update first before troubleshooting further.

What Entra-only sign-in doesn't give you​

GitHub's authentication documentation says GitHub authentication isn't required when you sign in with an Entra account. Without GitHub authentication, though, some features don't work:

  • /delegate, because it needs Copilot cloud agent running on GitHub's servers
  • The GitHub MCP server, because it needs authentication to call GitHub APIs
  • GitHub Code Search, because it needs authentication to query GitHub's search index

The docs say you can combine Entra authentication with GitHub authentication to get both: Microsoft 365 models for responses, plus GitHub-hosted features. A developer who signs in only through Microsoft 365 will have a capable terminal agent that can't open pull requests on their behalf.

Governance: what security teams should check​

This is where IT administrators should read carefully. GitHub's CLI documentation makes several points:

  • Your choice of model decides where data goes. If you pick a Microsoft 365 Copilot model, prompts and context are sent to Microsoft 365 Copilot services instead of GitHub. Usage counts against the Microsoft 365 Copilot license, and your organization's Microsoft 365 Copilot policies apply.
  • Local copies aren't covered by Microsoft 365 retention. The CLI runs on the device. Conversation history and generated files may be stored locally, and Microsoft 365 service-side retention, legal hold, and eDiscovery policies don't apply to those copies. Compliance teams that assumed Purview would cover everything should take note.
  • Inference sessions are kept separate. Even users with both services use only one inference service per session. Switching from Microsoft 365 Copilot to GitHub Copilot starts a new session, and the Microsoft 365 conversation context doesn't carry over.
  • That separation only covers the model conversation. GitHub says it doesn't isolate the device or stop connected tools and commands from reading files or contacting other services.

GitHub's standard warnings also still apply. If you allow automatic tool approval with flags like --allow-all-tools, Copilot gets the same file and shell access you have. Entra sign-in changes who you are to the CLI. It doesn't change what the agent can do on your machine.

The bigger picture​

This preview didn't come out of nowhere. In a GitHub issue on the Copilot SDK, a developer testing Copilot CLI 1.0.105 on macOS said they couldn't find an Entra option in the CLI. They also found that the SDK's provider enumeration listed an Entra provider as "Your organization (Microsoft Entra)" with available: false. The groundwork was already in the code before 1.0.113 turned it on.

Strategically, it's a significant change. Until now, using Copilot meant having a GitHub identity. With this preview, a Microsoft 365 Copilot license can power a coding agent in the terminal without any GitHub account, governed from the Microsoft 365 admin center. For organizations that standardized on Entra and Microsoft 365 but have no GitHub Enterprise presence, that removes a barrier. It also raises a fair question: with two Copilot entitlements that can cover the same terminal session, who owns the developer AI budget, the GitHub admins or the Microsoft 365 admins?

There are limits on both sides. The Microsoft 365 path is limited to Frontier customers with usage-based billing, so most tenants can't use it yet. The EMU path skips SAML-based EMU deployments entirely. And with Linux still on the to-do list, the platform where many developers actually live is left out for now. This is a preview with real potential, not something to roll out across your whole fleet.

Bottom line: Update to 1.0.113, find out which of the two paths your organization qualifies for, and before anyone selects a Microsoft 365 model, confirm with your compliance team where prompts are sent and what stays on local disks.

 

References

  1. GitHub Copilot CLI adds Microsoft Entra sign-in as a preview GitHub Changelog 2026-11-17T18:00:35+00:00
  2. Can the SDK use an existing Microsoft 365 Copilot subscription via Entra sign-in, without registering an Entra app? · Issue #2882 · github/copilot-sdk · GitHub github.com
  3. GitHub Copilot CLI - GitHub Enterprise Cloud Docs docs.github.com