Skip to content
NewsProduct launch

GitHub Enterprise now bundles Copilot access for every licensed seat

· by

The short version

GitHub folded Copilot into GitHub Enterprise licensing on October 28, 2026, replacing the old per-seat allowance with uncapped usage metered straight against the enterprise's own AI budget.

GitHub Enterprise now bundles Copilot access for every licensed seat

GitHub stopped selling Copilot as a separate line item to its biggest customers. As of October 28, 2026, every licensed GitHub Enterprise user gets Copilot access folded into that license, but the monthly AI-credit allowance that used to come with it is gone entirely, per GitHub's changelog post.

What changed

Admins used to track two separate numbers: how many Copilot seats they were buying and how much of each seat's included AI allowance got used. Per GitHub, that first number disappears for GitHub Enterprise accounts. GitHub Copilot access now ships with the Enterprise license itself, and every request is metered from the first token against the enterprise's own budget, with no included allowance to track or top up. Employees who do not hold a GitHub Enterprise seat can still buy standalone access separately at $10 per user per month. The rollout starts with enterprises that work with a GitHub or Microsoft account team; self-serve customers get it in later stages, with no date yet announced, and existing Copilot Business and Copilot Enterprise subscriptions keep working unchanged.

Not every feature stops when the budget runs out. Code completion and next-edit suggestions keep running even against a zero balance, GitHub says, while Copilot Chat, code review, and cloud-agent sessions pause until more budget is available. Seats and the no-cost features are never revoked for lack of funds.

Budget overruns, not seat math, become the thing to watch

The practical shift is where the cost risk sits. A flat per-seat allowance capped the downside: a team could only burn through its included credits, then had to buy more. An uncapped enterprise budget with no included allowance has no such ceiling built in, so a spike in Chat or code-review usage across thousands of seats draws straight down shared funds instead of hitting a per-seat wall first. Finance and platform teams running GitHub Enterprise at scale now need usage alerts and attribution policies in place before this ships to their account, not after, since GitHub's own billing documentation describes metering starting on day one with no grace allowance. Teams already comparing per-seat AI coding tools should weigh this against flat-fee competitors that still cap monthly spend by seat.

What to watch next

Two things worth tracking: when self-serve (non-account-team) enterprises get access to the bundled model, and whether GitHub publishes default budget caps or alert thresholds for admins who want a ceiling the old plan provided automatically.

Sources