Live
Cloudflare Images Analytics Dashboard Adds 30‑Day Delivery VisibilityAmazon ECS Adds Native Blue/Green, Canary, and Linear Deployments for Safer Container RolloutsGemini agentic tools add LLM‑driven automation to Partner Marketing StudioGitHub Actions makes RHEL 9/10 runner images generally available for larger workloadsIntegrating Decider Models to Reduce Latency and Cost in AI Agent WorkflowsAWS Emulator Enables Local Testing of 200+ Services, but Lacks IAM ValidationSageMaker AI monitoring adds automatic latency drift, idle GPU, and configuration gap detection for inference endpointsEmbedding Proactive Governance into Enterprise‑Scale Agentic AICloudflare Images Analytics Dashboard Adds 30‑Day Delivery VisibilityAmazon ECS Adds Native Blue/Green, Canary, and Linear Deployments for Safer Container RolloutsGemini agentic tools add LLM‑driven automation to Partner Marketing StudioGitHub Actions makes RHEL 9/10 runner images generally available for larger workloadsIntegrating Decider Models to Reduce Latency and Cost in AI Agent WorkflowsAWS Emulator Enables Local Testing of 200+ Services, but Lacks IAM ValidationSageMaker AI monitoring adds automatic latency drift, idle GPU, and configuration gap detection for inference endpointsEmbedding Proactive Governance into Enterprise‑Scale Agentic AI
GitHub

GitHub Copilot CLI introduces Microsoft Entra SSO for EMU and Microsoft 365 Copilot (preview)

AI SummaryPowered by AI

GitHub Copilot CLI now supports Microsoft Entra authentication in public preview, enabling silent sign‑in for Enterprise Managed Users and Microsoft 365 Copilot licenses. This change reduces credential friction for AI‑driven workflows and shifts inference source depending on the entitlement.

GitHub Copilot CLI version 1.0.113+ adds public‑preview support for Microsoft Entra authentication. Practitioners can now log in with a Microsoft Entra identity to either a linked GitHub Enterprise Managed User (EMU) or a Microsoft 365 Copilot license, eliminating a separate GitHub sign‑in step.

What Changed

The CLI now offers two distinct Entra‑based paths:

  • Enterprise Managed User (EMU) SSO: For organizations that provision EMUs via OIDC, Entra credentials silently authenticate to GitHub, provided the tenant has a Copilot Business or Enterprise license and the Copilot CLI policy is enabled. The CLI continues to use GitHub inference, and usage is billed under the organization’s Copilot plan.
  • Microsoft 365 Copilot access: For Frontier customers with a usage‑based Microsoft 365 Copilot license, Entra authentication lets the CLI call Microsoft‑hosted models directly. No GitHub account is required, and usage limits follow the Microsoft 365 Copilot settings. The optional Work IQ MCP server can supply work‑data context.

Support is currently limited to Windows and macOS; Linux support is announced for a future release.

Why It Matters to Engineers and Operators

Eliminating a second sign‑in reduces friction in automated pipelines, CI/CD jobs, and local development environments. The split between GitHub‑hosted and Microsoft‑hosted inference also means that cost and quota management now depend on which entitlement is used, affecting budgeting and capacity planning.

Architectural and Operational Implications

Adopting Entra SSO introduces a single identity source for both GitHub and Microsoft 365 Copilot workloads. Practitioners should consider the following:

  • Identity provisioning: Ensure that the Microsoft Entra accounts are correctly linked to EMUs or Microsoft 365 Copilot licenses. Mis‑alignment will result in authentication failures.
  • Policy enforcement: The organization must enable the Copilot CLI policy for EMU SSO. This is a configuration step in GitHub Enterprise Cloud’s Enterprise Managed Authorization settings.
  • Inference routing: When using a Microsoft 365 Copilot license, the CLI bypasses GitHub inference entirely. Monitoring and alerting should be adjusted to capture usage from the Microsoft side.
  • Platform compatibility: Current support is limited to Windows and macOS. Scripts that run on Linux must either wait for future support or fall back to the existing GitHub token flow.
  • Work IQ MCP integration: If contextual work data is required, the Work IQ MCP server must be configured. This adds an additional service dependency that should be included in the operational run‑book.

Related CloudNinjas coverage: AI engineering.

What This Means For Practitioners

Upgrade to Copilot CLI 1.0.113 or later (copilot update) and verify that your Entra accounts are correctly mapped to the appropriate entitlement. Enable the Copilot CLI policy if you rely on EMU SSO, and confirm that your Microsoft 365 Copilot license is active for terminal‑based model calls. Begin testing on supported OSes, and plan for Linux support in upcoming releases. Monitor both GitHub and Microsoft usage dashboards to keep cost and quota visibility aligned with the new dual‑inference model.

Originally published atGitHub Changelog