GitHub Enterprise Copilot Access: Costs and Limits

GitHub announced a new Copilot access model for GitHub Enterprise Cloud on October 28, 2026. Eligible enterprises can provide Copilot to already-licensed developers without paying an additional Copilot seat charge. That does not mean AI usage is free: the model includes no monthly AI credits, and metered requests draw from the enterprise budget from the first use. Access is also staged, currently through GitHub or Microsoft account teams rather than an automatic self-service upgrade. Administrators should evaluate total AI spend before switching.

Who can get the new Copilot access?

GitHub says the model is currently available to eligible GitHub Enterprise Cloud customers working with a GitHub or Microsoft account team. Self-service subscriptions are not yet eligible, and no universal self-service date has been confirmed. GitHub Free, Team and self-service Enterprise Cloud trials are excluded. Existing Copilot Business and Copilot Enterprise customers can keep their plans; moving is voluntary. Even users with Enterprise Cloud licenses need an enterprise owner to assign Copilot seats explicitly, so a qualifying license does not automatically enable Copilot features.

Compare seat prices and included credits

The new access model offers the same feature and model eligibility as Copilot Enterprise, subject to administrator controls. An eligible enterprise may combine access for Enterprise Cloud-licensed users with $10-per-user Copilot Standalone for people without those licenses. It cannot, however, mix the new Copilot access billing model with Copilot Business or Copilot Enterprise seats in different organizations under the same enterprise. That distinction matters when estimating a phased migration or supporting contractors.

Which AI features still cost money?

GitHub measures metered usage in AI credits; one credit equals $0.01. Copilot Chat, CLI, cloud agents, Spaces, Spark and third-party coding agents can consume credits. Inline code completions and next-edit suggestions do not consume AI credits and remain available even if an enforced spending limit blocks other features. Actual costs depend on the model and tokens consumed. The old Business and Enterprise plans include monthly pooled credit allowances, while the new access model has no included allowance, so removing a seat fee can increase total spend for heavy users.

Migration checklist for enterprise administrators

1. Export current Copilot seat charges and AI credit usage for the same month, including usage inside the pooled allowance.
2. Estimate metered usage under the new model at applicable model rates and add $10 for each Copilot Standalone user.
3. Confirm eligibility, contract terms and transition timing with your GitHub or Microsoft account team; changes are voluntary.
4. Assign Copilot seats, enable the required AI credits paid usage policy, and configure enforceable user and enterprise budgets.
5. Review firewall rules: an environment permitting only the Business endpoint may need the Copilot Enterprise endpoint added.

GitHub says transitions take effect on the first day of a month after coordination with an account team. Budget controls are particularly important because the new plan bills eligible AI interactions immediately, without a prepaid credit pool. A spending cap may block metered Chat or agent functions while leaving code completion available. Monitor usage after migration and reassess the cost estimate against real workloads; neither a $0 seat charge nor a published credit conversion guarantees a lower monthly invoice.