GitHub Copilot Budgets Now Support Expiration Dates for Individual Users
GitHub now lets admins set expiration dates on individual Copilot user budgets. Available for Copilot Business and Enterprise plans via UI or REST API.
GitHub has shipped expiration dates for individual user budgets in GitHub Copilot, and the feature is now generally available. Admins on Copilot Business or Copilot Enterprise plans can set a budget override to expire automatically at the next billing cycle, on a specific date, or never. Before this change, removing temporary budget overrides was a manual task that compounded into recurring cleanup work at enterprise scale.
What happened
| Detail | Fact |
|---|---|
| Feature status | Generally available |
| Plans supported | GitHub Copilot Business and Copilot Enterprise |
| Expiration options | No expiration (default), start of next billing cycle, specific date |
| API field | expires_at in the Budgets REST API |
| Fallback behavior | Cost center per-user budget, then universal budget |
GitHub now lets enterprise admins attach an optional expiration date to any individual user budget override in GitHub Copilot. On the chosen date, GitHub removes the override automatically and the user falls back to whichever budget sits next in the hierarchy: their cost center per-user budget first, then the organization’s universal budget.
Previously there was no automatic removal. Every temporary budget increase had to be deleted by hand, which meant admins at large enterprises were carrying a growing list of cleanup tasks with no tooling to manage them.
How to set an expiration date
There are two ways to configure this:
- Go to your billing settings, open the individual user budget you want to edit, and choose an expiration option from the UI.
- Use the Budgets REST API. When creating or updating a budget, pass the expires_at field with your target date. You can change or clear the date at any time after setting it.
Why does this matter for teams using Copilot at scale?
Temporary budget overrides are common at enterprise scale. A developer spins up a heavy project, gets a raised limit for a sprint or a quarter, and then the limit should return to normal. Without automated expiry, those overrides stack up and become invisible costs if no one remembers to clean them up.
The new fallback chain is also worth understanding. When a budget expires, the user does not lose access to Copilot. They simply drop to the next applicable budget tier. That means finance teams can model the fallback behavior in advance rather than scrambling when a developer suddenly hits a different limit.
For teams already using the Budgets REST API as part of a wider workflow automation setup, the expires_at field fits neatly into provisioning and deprovisioning scripts, removing the need for a separate scheduled cleanup job.
Our take
This is a small but genuinely useful admin quality-of-life fix. The manual cleanup problem it solves is real: anyone who has managed Copilot seats across dozens of users in a cost-center structure knows that temporary overrides quietly accumulate. Automating expiry via either the UI or the API is the right call.
The fallback hierarchy (individual budget, then cost center, then universal) is sensible design. It means the change is safe to roll out without worrying about users losing functionality on expiry day. Our only note: if you are managing budgets programmatically, audit your existing overrides now. Any override without an expiration date stays in place indefinitely under the new system as well, since “no expiration” is still the default.
If you are building AI tooling on top of GitHub Copilot for client teams, this is worth adding to your provisioning playbook. See our AI integration services if you need help structuring that kind of workflow.
Frequently asked questions
What happens when a GitHub Copilot user budget expires?
When an individual user budget expires, GitHub removes the override and the user automatically falls back to their cost center per-user budget, or to the organization's universal budget if no cost center budget applies.
How do I set an expiration date on a Copilot user budget?
You can set an expiration date in GitHub billing settings when creating or editing an individual user budget, or by passing the expires_at field when using the Budgets REST API to create or update a budget.
Is the budget expiration feature available on all Copilot plans?
Expiration dates for individual user budgets are available on GitHub Copilot Business and GitHub Copilot Enterprise plans.
Can I change or remove a Copilot budget expiration date after setting it?
Yes. GitHub lets you change or clear an expiration date at any time after it has been set, either through the billing settings UI or via the Budgets REST API.
