Managing Copilot usage-based billing
GitHub Copilot usage-based billing (UBB) uses a shared pool of AI Credits (AICs) where all licensed users draw from a central enterprise pool. When the pool runs out, metered billing kicks in, and layered budgets control what happens next.
For the full governance framework — layered budget design, cost center configuration, operating model, and API automation — see the Managing AI credits and operating model article in the GitHub Well-Architected Framework. For billing mechanics, see Usage-based billing for organizations and enterprises. For budget definitions and how controls interact, see the Understanding Copilot budgeting product guide.
This page covers tactical sizing guidance, operational tips, and troubleshooting that complement the WAF article.
Important
Enterprise and Cost Center budgets only cap spending after included credits run out. Universal and Individual User Budgets are always active and limit how much of the pool each person can draw, even while the pool still has capacity.
Promotional period (June 1 – September 1, 2026)
For the first three months of usage-based billing, existing customers get more included credits:
| Plan | Standard | Promotional |
|---|---|---|
| Copilot Business | 1,900 AICs/user/month | 3,000 AICs/user/month |
| Copilot Enterprise | 3,900 AICs/user/month | 7,000 AICs/user/month |
Why this matters for Enterprise seats
During the promo, Enterprise seats include 7,000 AICs vs. 3,000 for Business, a 2.3× difference. If you have developers who will burn through 3,000 credits/month, putting them on Enterprise seats during this window gets you more pooled credits at no extra per-credit cost.
Note
Copilot Enterprise requires a GitHub Enterprise Cloud (GHEC) seat. This only works for users who already have GHEC. If they don’t, you’d also need to purchase a GHEC seat, so factor that cost in before upgrading.
After September 2026 the advantage disappears. Both tiers include credits proportional to their license cost ($0.01/AIC), so upgrading from Business to Enterprise adds $20/month in cost alongside $20 in credit value. No net gain. At that point, raising Individual User Budgets is cheaper than upgrading tiers (see Tip #4).
Tip
Use the promotional window to find your power users and get them on Enterprise seats. After the promo ends, switch to Individual User Budgets for anyone who needs more headroom.
Recommended budget strategy
The approach that works best for most organizations is progressive: start generous, then use the limits to discover who your heavy users are and what they’re working on.
Step 1: Set the Universal User Budget at 2.5–3× entitled credits
Give every user a Universal User Budget (ULB) of 2.5–3× their per-seat entitlement:
- Business users (1,900 AICs included): set ULB to 4,750–5,700 AICs
- Enterprise users (3,900 AICs included): set ULB to 9,750–11,700 AICs
This lets heavier users borrow from lighter users’ unused portions without anyone monopolizing the pool. If credits are left over at month end, raise it. You want near-zero remaining credits with nobody blocked mid-month.
Tip
Capping at exactly 1× the per-license value defeats the purpose of pooling. Heavy users get blocked while light users waste credits. 2.5–3× is the sweet spot.
Step 2: When someone hits the limit, find out why
When a developer hits their Universal User Budget, don’t just raise it. Instead:
- Grant them an Individual User Budget with a higher cap. This is the only way to give a specific user more headroom within the pool — Cost Center budgets won’t help here since they only track overage after the pool is exhausted.
- Find out what project they’re working on. This context is how you build the case for AI investment.
Step 3: Build your champions program
The developers who consistently hit their budgets are your power users. They’re also the foundation of a good AI adoption story:
- Identify them through budget notifications and usage data
- Collect their stories: what they’re shipping faster, what problems Copilot is solving for them
- Use those stories to demonstrate business value and justify continued investment
Note
This turns cost management into a discovery exercise. Budget notifications become a signal for where AI is delivering real returns, not just a spending alert.
Configuration tips
1. Always set a Universal User Budget
Here’s how to set it in the enterprise billing settings:
2. Enable “Stop usage” on User-Level Budgets
Enable “Stop usage” on Universal and Individual User Budgets — this is your hard enforcement cap per user. At the enterprise and cost center level, the WAF recommends disabling “Stop usage” to avoid a single global cap that disrupts all engineers. Use threshold alerts (75%, 90%, 100%) at those levels instead.
3. Budgets only track from their creation date
When you first create a budget, it applies only to metered usage from that date forward. Prior consumption isn’t counted. This means you can exceed your budget in the first cycle even with “Stop usage” enabled. Create or adjust budgets at the start of a billing cycle whenever possible. If creating mid-cycle, set the limit conservatively. See Budgets and alerts for details.
4. Raise Individual User Budgets before upgrading tiers (post-promotional period)
After September 2026, an Individual User Budget on a Business license lets a user borrow more from the pool at no extra cost. Upgrading from Business to Enterprise adds $20/month in licensing alongside $20 in credit value. No net gain. If someone needs more capacity post-promo, raise their Individual User Budget first.
Note
During the promotional period (June 1 – September 1, 2026), Enterprise seats include disproportionately more AICs (7,000 vs. 3,000), so the upgrade is worthwhile for power users who already have a GHEC seat. See the Promotional period section.
5. Gate budget increases on prior-month usage data
Individual User Budgets don’t expand the pool. They raise the per-user ceiling, which accelerates depletion for everyone. Require usage data before granting increases: if someone didn’t hit their limit last month, they don’t need a higher one.
6. Share pool depletion metrics monthly
Publish a simple end-of-month summary (“Pool was 74% consumed, no one was blocked”). When people can see the pool is healthy, they’re less likely to inflate usage defensively or rush to consume credits early in the cycle.
When developers are blocked
When someone reports being blocked, work through these checks in order:
- Did they hit their Universal or Individual User Budget?
- Yes: raise their budget or grant an Individual User Budget with a higher cap. This is the cause nine times out of ten.
- No: keep checking.
- Is the shared pool depleted?
- No: the pool still has capacity. The issue is the user’s personal budget (step 1) or their license/feature access. Cost Center budgets are irrelevant here — they only track overage after the pool is exhausted.
- Yes: keep checking.
- Has the Enterprise Budget been reached?
- Yes: raise it. It’s capping total metered charges.
- Are they in a cost center with a budget that has “Stop usage” enabled?
- Yes and the pool is depleted: the cost center budget is capping their overage. Raise it or remove the cap.
- No: check whether “Stop usage” is enabled on the Enterprise Budget, or whether their license was removed.
Tip
Mid-month blocks are almost always the Universal User Budget. Cost Center budgets only matter after the pool runs out — they cannot unblock a user who hit their personal cap while pooled credits remain.
Note
A common misconception is that placing a user in a Cost Center with a higher budget will let them exceed their Universal User Budget. It won’t. Cost Center budgets track overage spend, not pooled entitlement usage. The only way to give a user more headroom within the pool is to raise their Universal User Budget or assign an Individual User Budget.
Budget guidance adapted from xrvk