Employees with an eligible Microsoft 365 Copilot licence can now use GitHub Copilot CLI without a GitHub account. The public preview announced on November 17, 2026 requires Frontier enrolment, administrator approval and usage-based billing. An existing licence alone does not provide unlimited terminal use.
Copilot CLI brings AI assistance into the terminal—the text-based interface used to run commands. It can help explain, write and debug code. For a team already paying for Microsoft 365 Copilot, the new decision is whether its existing entitlement plus metered usage fits the work, or whether GitHub-hosted features require a different arrangement.
Who qualifies for Microsoft 365 access?
You need a work account with Microsoft 365 Copilot access and enrolment in Frontier, Microsoft’s opt-in preview programme. Administrators can enrol selected users or groups; Frontier membership does not replace the required product licence. A personal Microsoft subscription is not evidence of eligibility for this organisational route.
The Entra sign-in preview supports Windows and macOS, with Copilot CLI version 1.0.113 or later. GitHub says Linux support will follow but gives no date. Do not confuse general Linux support for the CLI with support for this new sign-in option.
There is also a separate route for organisations using GitHub Enterprise Managed Users linked through OpenID Connect (OIDC), a work-account sign-in standard. That route requires an assigned Copilot Business or Enterprise licence and an enabled CLI policy. Model requests go through GitHub, with usage governed by the organisation’s GitHub Copilot plan. The two routes can coexist.
Which three settings must your admin enable?
GitHub’s authentication guide assigns these actions in the Microsoft 365 admin centre:
Code spending policy: a Billing Administrator or Global Administrator enables usage-based billing for Microsoft Copilot Code.
Copilot Frontier: an AI Administrator or Global Administrator enables the preview setting.
GitHub Copilot access (Frontier): a Global Administrator enables this separate setting, which is off by default.
For Frontier enrolment, Microsoft is rolling out new release-preference navigation while retaining the existing Copilot settings route. Labels can therefore differ between organisations. Microsoft says Frontier access can take about three hours to reach users.
Who pays, and how do you limit the bill?
With Microsoft 365 models selected, usage belongs to the organisation’s Microsoft 365 billing arrangement. Microsoft measures consumption in Copilot Credits and lists Code as a service that requires a Copilot licence. Depending on the supported billing arrangement, consumption can use prepaid credits or pay-as-you-go funding; it is not automatically covered without limit by the seat subscription.
Before activation, identify the funding subscription and the intended users. The billing setup guide says default setup covers the whole organisation unless customised. For a pilot, scope the policy to the intended group and Code service, set spending limits and alerts, and review whether future services should be added automatically.
A small pilot policy is not necessarily the effective budget. Under Microsoft’s policy-selection rules, when several identity-based policies cover the same user and service, the highest per-user limit wins. Ties favour the larger policy budget, then the newest policy. Without a per-user cap, the overall policy limit supplies the comparison value.
That makes overlapping group membership a budget check: a more generous policy can defeat the pilot’s intended cap. The selected policy applies as a whole; exhausting it does not automatically move the user to another policy.
The same guidance currently specifies at least 2,000 credits for a configured monthly user budget. This is a spending allowance, not free credits or a minimum bill. Access stops at the applicable limit until the monthly reset unless the allowance is changed. Additional policies also have independent limits; the default policy is not an umbrella cap for all of them.
A credit budget is not a forecast of completed tasks. Neither the announcement nor the billing overview specifies a fixed cost per CLI task or a guaranteed included CLI allowance. Before expanding access, use Microsoft’s consumption reports to review actual usage by user, service and policy.
Which features still need GitHub sign-in?
Without GitHub authentication, three capabilities remain unavailable: /delegate for cloud-agent work, the GitHub MCP server for API tools, and GitHub Code Search. Microsoft Entra and GitHub authentication can be combined, but check the required feature entitlements and permissions separately.
If the next requirement is access to self-hosted repositories, the GitHub Enterprise Server setup guide for the Copilot desktop app addresses that separate task. Its app workflow is not a setup guide for this CLI preview.
What happens to prompts and local files?
When Microsoft 365 models are selected, GitHub says prompts and inference context go to Microsoft 365 services. Switching to GitHub inference starts a separate session without carrying over the existing Microsoft 365 conversation context. That separation does not isolate the computer or connected tools.
Commands and file operations still run locally. Conversation copies and generated files can remain on the device, outside Microsoft 365’s service-side retention, legal-hold and eDiscovery policies. In practical terms, approval of the billing route does not settle how the team should handle local work files.
For organisations also governing GitHub Copilot customisations, the guide to restricting Copilot to approved plugin sources covers a separate control. Its GitHub enterprise requirements should not be read as benefits granted by a Microsoft 365 licence.
Start with a bounded pilot
After the administrator checks, update an existing installation with copilot update. Then follow the documented sign-in flow: run /login, choose Your organization (Microsoft Entra), and inspect /model for permitted models. Successful sign-in does not substitute for the required licence or spending policy.
Choose a small code or documentation change whose output a colleague can review. Expand only after checking the effective spending policy, recorded consumption and any GitHub features the task needs. If the organisation cannot accept preview access or has not assigned a billing owner, resolve those conditions before rollout.
