GitHub Adds Expiration Dates for User Budgets in Copilot Plans
James Ding Sep 03, 2026 09:29
GitHub introduces user budget expiration dates for Copilot Business and Enterprise plans, streamlining billing management for admins.
GitHub has rolled out a new feature allowing administrators to set expiration dates for individual user budgets. Announced on September 1, 2026, this update simplifies billing management for Copilot Business and Enterprise plans by automating the cleanup of temporary budget overrides.
Previously, admins had to manually remove temporary budgets, a task that could become cumbersome at enterprise scale. Now, with the introduction of the expires_at field in the Budgets REST API, administrators can specify when a user budget should end. Once the expiration date is reached, the individual budget is removed, and the user transitions to the next applicable budget, such as a cost center or organization-wide budget.
Administrators have three options when creating or editing a budget:
- No expiration, which mirrors the current behavior.
- Expiration at the start of the next billing cycle.
- Expiration on a specific date.
This feature is part of GitHub’s broader effort to enhance usage-based billing controls, particularly for Copilot AI credits. Individual budgets are critical for monitoring and capping consumption, especially as Copilot users may fall under multiple budget levels, including individual, cost center, and organization-wide scopes. If a budget limit is reached, admins can choose to either block further usage or simply monitor overages depending on their setup.
For developers managing budgets programmatically, the Budgets REST API now supports the new expiration functionality. This addition allows teams to streamline budget management workflows, reducing manual intervention and improving efficiency.
This update follows other recent enhancements to GitHub's billing tools. In July 2026, GitHub introduced features for tracking AI credit usage per billing cycle, and earlier that month, added per-user states for multi-user budgets in the REST API. These updates collectively aim to provide enterprises with granular control over resource consumption, ensuring predictable costs while supporting scalable AI development environments.
GitHub's documentation provides comprehensive guidance on setting up budgets and using the REST API. For enterprises using Copilot at scale, these changes could significantly lower administrative overhead while improving budget predictability.
Image source: Shutterstock.jpg)