The planned removal of GitHub Copilot’s $0 premium-request budgets for some enterprise and organization accounts is no longer upcoming: GitHub’s two official announcements give different 2025 removal dates, November 18 and December 2. For current spending decisions, administrators should use GitHub’s AI-credit billing documentation and their account’s current billing settings; the old premium-request instructions describe a past policy transition.
What happened to the $0 premium-request budgets?
In a September 17, 2025 announcement, edited November 13, GitHub said it would remove account-level $0 Copilot premium-request budgets from qualifying enterprise and organization accounts created before August 22, 2025. A separate GitHub changelog post published November 3 gave November 18, 2025 as the removal date; the edited announcement instead says removal would begin December 2, 2025. GitHub’s public pages do not resolve that discrepancy, and both dates have passed. GitHub’s September announcement and its November changelog post are the relevant historical notices.
![The Microsoft Copilot Bible for Beginners & Busy Professionals: [5 in 1] How to Boost Productivity, Save Hours Every Week, and Automate Your Work with AI](https://m.media-amazon.com/images/I/41tTEg9fueL._SL160_.jpg)
The change concerned premium-request budgets at the account level for qualifying enterprise and organization accounts. GitHub said its premium-request paid-usage policy would govern paid usage after removal. The announcement said individual Copilot Pro and Pro+ users were not affected by that particular change; this historical distinction should not be mistaken for a description of all current billing arrangements.
Why GitHub said it was changing the model
GitHub explained that dedicated usage SKUs for AI tools would make separate $0 budgets cumbersome to create and maintain. Its announcement said: “Keeping the $0 budget model would require you to manually create and manage separate $0 budgets for each new AI tool, creating unnecessary administrative burden as we expand our AI capabilities.”
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
How Copilot organization and enterprise billing is described now
GitHub’s current organization and enterprise billing documentation uses AI credits rather than the historical premium-request framing. Credits associated with Copilot licenses are pooled across the enterprise. When the shared pool is exhausted, additional usage may be metered, depending on the applicable paid-usage policy and budget controls. See GitHub’s current Copilot billing documentation.
GitHub’s legacy premium-request documentation is narrower: it applies to certain Copilot Pro and Pro+ subscribers on existing annual plans who remained on legacy request-based billing after June 1, 2026. It is not the current billing overview for organizations and enterprises.
Which current budget controls can limit Copilot spending?
GitHub documents budgets at user, cost-center, organization, and enterprise scopes. Their effect depends on whether usage is drawing on the shared pool or has moved to metered usage. The table summarizes GitHub’s documented behavior; consult the current budget setup guide and budget concepts before changing an account.
| Budget scope | When it applies | Enforcement behavior |
|---|---|---|
| User | During both the shared-pool and metered phases | Always a hard stop. A $0 user budget blocks usage immediately. |
| Cost center | Metered charges after the shared pool is exhausted | To stop usage at the configured limit, enable “Stop usage when budget limit is reached.” Otherwise, charges can continue. |
| Organization | Metered charges after the shared pool is exhausted | To stop usage at the configured limit, enable “Stop usage when budget limit is reached.” Otherwise, charges can continue. |
| Enterprise | Metered charges after the shared pool is exhausted | To stop usage at the configured limit, enable “Stop usage when budget limit is reached.” Otherwise, charges can continue. |
The paid-usage policy must also be enabled for additional metered usage to occur. Budget limits at cost-center, organization, and enterprise scopes should not be treated as automatic hard stops unless the stop-usage behavior is enabled.
Recommended Free Tools
What administrators should check before relying on a limit
- Open the account’s current billing and budget controls. Confirm the organization or enterprise scope and the settings actually available to your account; the 2025 premium-request instructions are historical, not a reliable current UI guide.
- Check whether paid usage is allowed. Additional metered usage depends on the applicable paid-usage policy being enabled.
- Identify the budget scope and billing phase. A user budget applies during the shared-pool and metered phases, while cost-center, organization, and enterprise spending budgets govern metered charges after the shared pool is exhausted.
- Set the enforcement behavior deliberately. For cost-center, organization, or enterprise limits, verify that “Stop usage when budget limit is reached” is enabled if the goal is to prevent further usage at the limit. User-level budgets are always hard stops.
Published plan figures are not the same as a spending cap
GitHub’s published plan details list Copilot Business at $19 USD per user per month with 1,900 AI credits per user, Copilot Enterprise at $39 USD per user per month with 3,900 credits per user, and additional usage beyond the shared pool at $0.01 USD per AI credit. These are GitHub’s listed commercial figures, not an independent price assessment; confirm the current Copilot plans and billing terms for your account. A plan’s included credits do not by themselves establish that metered charges will stop when a budget limit is reached.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
