Effective immediately, enterprises that partner with a GitHub or Microsoft account team receive Copilot automatically with each GitHub Enterprise license. The pricing model no longer requires separate seat purchases; instead, every request is metered against the organization’s existing AI budget, and the same feature set is delivered as Copilot Enterprise.
Copilot billing integration details
The new arrangement eliminates the dual‑track management of Copilot seats and AI consumption. Organizations now track a single budget line, using the same policies, alerts, and attribution mechanisms already in place for other cloud spend. There is no longer an included credit allowance; usage is charged from the first request. Users without a GitHub Enterprise license can still obtain Copilot via the standalone offering at $10 per user per month, but this option also lacks any monthly AI credits.
Operational impact for engineers
- Budget‑driven feature gating: Code completion and next‑edit suggestions remain functional even when the budget is exhausted, while Copilot Chat, code review, and cloud‑based Copilot features require remaining budget.
- Monitoring continuity: Existing budget policies and alerting configurations continue to apply, so teams should verify that thresholds and notifications are calibrated for the new usage pattern.
- Self‑serve rollout: The bundled offering is currently limited to accounts managed by a GitHub or Microsoft sales team. Self‑serve customers will receive access in staged releases; existing subscriptions are unaffected.
- Legacy options remain: Copilot Business and Copilot Enterprise can still be purchased separately, allowing teams to retain the previous model if it better fits their cost or governance strategy.
Security and policy considerations
Since AI usage is now metered directly against the enterprise budget, any policy that restricts spend will implicitly limit access to budget‑dependent Copilot features. Teams should audit their budget‑approval workflows to ensure that a depleted budget does not unintentionally block critical review or chat capabilities. The fact that code completion continues without budget means that baseline assistance is always available, but more advanced assistance can be denied, which may affect security‑related code‑review automation.
Related CloudNinjas coverage: AI engineering.
What This Means For Practitioners
Review and, if necessary, adjust your AI‑budget policies to reflect the new per‑request metering. Enable or tighten alerts for budget thresholds to avoid surprise loss of Copilot Chat or code‑review functionality. Document the distinction between always‑available completion features and budget‑gated capabilities so that incident‑response playbooks account for potential feature loss. Finally, track the upcoming self‑serve rollout schedule to plan migration or adoption paths for teams that are not currently managed by a sales account team.