Free tools Windows power users keep installed
One-click scans. No signup required.
GitHub’s planned removal of $0 Copilot premium request budgets for qualifying enterprise and organization accounts is no longer upcoming: the announced dates were in 2025. GitHub’s announcement page gives December 2, 2025, while a separate changelog post gives November 18, 2025, so the official sources do not establish one uncontested date. For current spending decisions, administrators should use GitHub’s AI-credit billing documentation and the controls shown in their account—not the old premium-request instructions.
What the 2025 change announced
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. GitHub said its premium-request paid-usage policy would govern paid usage after removal. A separate GitHub changelog post dated November 3 said the $0 budgets would be removed November 18, 2025; the announcement page’s later editor’s note says December 2, 2025. The pages conflict, and neither should be treated as proof of a single definitive date. GitHub’s announcement and November changelog post preserve the differing dates.
GitHub said the separate zero-dollar budgets would become cumbersome as it introduced dedicated usage SKUs for AI tools. Its announcement explained: “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.” The same announcement said individual Copilot Pro and Pro+ users were not affected by this particular change.
The announcement described three choices for administrators under the policy then in effect: disable paid usage to block charges, enable it for uninterrupted paid use, or set a positive budget to cap overage spending. These are historical explanations, not reliable current navigation or instructions: the present organization and enterprise billing model is documented in AI credits.
#1 Best Overall
How organization and enterprise Copilot billing works now
GitHub’s current organization and enterprise documentation describes Copilot usage in AI credits. Credits from Copilot licenses are pooled across the enterprise. When that shared pool is exhausted, additional usage may be metered, depending on the applicable paid-usage policy and budget controls. GitHub labels its legacy premium-request documentation as applying only 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 overview for organization and enterprise billing. See GitHub’s Copilot billing documentation.
Which spending controls apply—and when
GitHub documents budget controls at user, cost center, organization, and enterprise levels. The important distinction is whether a control works during the shared-credit phase or only after usage becomes metered, and whether reaching the limit blocks usage or merely sets a spending threshold.
| Control scope | When it applies | What happens at the limit |
|---|---|---|
| User budget | During both the shared-pool and metered phases | Always enforces a hard stop; a $0 user budget blocks usage immediately. |
| Cost center budget | Metered charges after the shared pool is exhausted | GitHub says “Stop usage when budget limit is reached” is off by default for these spending limits. Without enabling it, charges can continue beyond the configured limit. |
| Organization budget | Metered charges after the shared pool is exhausted | GitHub says “Stop usage when budget limit is reached” is off by default for these spending limits. Without enabling it, charges can continue beyond the configured limit. |
| Enterprise budget | Metered charges after the shared pool is exhausted | GitHub says “Stop usage when budget limit is reached” is off by default for these spending limits. Without enabling it, charges can continue beyond the configured limit. |
For cost center, organization, and enterprise limits, setting a budget amount alone may not stop billing. Check that the stop-usage behavior is enabled if the goal is to prevent metered usage from continuing past the limit. Paid usage must also be enabled for additional metered usage to occur. Current options and their scope are described in GitHub’s budgets and alerts documentation and GitHub’s budget setup instructions.
What administrators should check before relying on a limit
- Open the current billing controls. Use the organization or enterprise billing settings and GitHub’s current AI-credit documentation; do not assume the old premium-request policy interface or steps still apply.
- Identify the level that owns the spend. Confirm whether the relevant budget is attached to a user, cost center, organization, or enterprise, and who has authority to change it.
- Check whether usage is still drawing from pooled credits. Organization, cost center, and enterprise spending budgets govern metered charges after the shared pool is exhausted, while user budgets apply during both stages.
- Verify enforcement, not just the amount. User budgets are hard stops. For cost center, organization, and enterprise limits, inspect whether “Stop usage when budget limit is reached” is on if you need a hard limit.
- Review paid-usage policy and alerts. Paid usage must be enabled before additional metered usage can occur; make sure the policy and notifications match the organization’s intended spending controls.
Current published plan figures
GitHub’s published plan details list the following prices and credit allocations. These are vendor-listed figures, not independent estimates, and can change; confirm the current billing page before budgeting.
Rank #3
| Plan or usage | GitHub-published figure |
|---|---|
| Copilot Business | $19 USD per user per month; 1,900 AI credits per user |
| Copilot Enterprise | $39 USD per user per month; 3,900 AI credits per user |
| Additional usage beyond the shared pool | $0.01 USD per AI credit |
These figures are listed in GitHub’s Copilot plans information. The actual amount an organization pays depends on its plan, usage, pooled credits, and enabled billing controls.
Quick Recap
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.
