GitHub's October 28 announcement gives eligible Enterprise Cloud customers a new way to provide Copilot to licensed users. The option separates access from an included AI-credit allowance, making the controls on metered use central to the purchase decision.

The big change

  • Copilot access can reach eligible Enterprise Cloud users without a separate Copilot seat charge, but that does not turn AI work into a fixed-price benefit. The purchasing question moves toward how much work people run and which features they use.
  • A spending control can serve very different purposes: warning an administrator or stopping requests. That choice connects financial oversight to everyday availability, so the person setting the budget needs to understand the effect on the people doing the work.
  • Procurement teams comparing the options need a view of total expected consumption as well as license costs. An estimate built from the organization’s own usage and purchasing records can make that choice more informative than a comparison based on headcount alone.

Access does not include AI credits

GitHub says the new option includes Copilot Enterprise features and models but no monthly AI credits per seat. Eligible Enterprise Cloud users have no additional Copilot seat charge; Standalone access for unlicensed enterprise users costs $10 per user per month. Account-managed customers can arrange the change now. Self-serve access is unavailable for now and will arrive in stages; current self-serve subscriptions are unaffected.

The billing documentation says seats still need to be assigned and the new access model cannot be combined with Business or Enterprise seats in the same enterprise. Transition is voluntary. That makes the decision an enterprise purchasing choice, rather than just a switch for an individual developer.

The announcement does not establish what a particular customer will pay. An estimate needs the number of eligible users, applicable license charges and expected credit-consuming work. The feature mix matters too: a calculation based only on headcount cannot establish total usage.

A spending threshold is not always a cap

According to GitHub's budget guide, user-level limits always hard-stop credit-consuming features. Enterprise, organization and cost-center limits stop metered use only when the stop-usage setting is enabled; it is off by default. Otherwise charges continue beyond the threshold. License fees are outside the enterprise spending budget.

An administrator who wants a spending ceiling must check the enforcement setting. The choice affects availability as well as cost.

The paid-usage policy must also be enabled for access-plan credit consumption. On Business and Enterprise it governs usage after the shared pool is exhausted.

The announcement says code completion and next-edit suggestions continue without available budget, whereas Chat, code review and cloud use require it. Support teams need the affected feature and the applicable policy to explain a blocked request; the presence of a seat alone does not answer that question.

Compare usage covered by existing seats

Business and Enterprise seats contribute credits to a shared pool, with metered charges beginning after it is exhausted.

An overage bill omits usage covered by the pool. The comparison needs expected total usage as well as license charges and budget settings. Published terms alone cannot tell an individual enterprise whether switching will save money.

For cloud work, a separate GitHub announcement says sandbox compute can draw on a shared Actions entitlement; sandbox billing begins in November 2026. That compute entitlement is separate from Copilot's AI-credit controls and belongs in a cloud-use cost assessment alongside them.

BIG CHANGE reviewed GitHub's announcements and documentation. It did not inspect a customer contract, migrate an account or measure usage.