Set an expiration date for individual user budgets

GitHub has made generally available an optional expiration date for individual user budgets in GitHub Copilot Business and Copilot Enterprise plans, allowing administrators to set a budget to expire at the start of the next billing cycle or on a specific date, after which the user falls back to the next applicable budget. This removes the need for manual cleanup of temporary budget overrides, and can be configured via billing settings or the `expires_at` field in the Budgets REST API.

Set an expiration date for individual user budgets You can now set an optional expiration date on an individual user budget, and GitHub removes the budget on that date. This capability is generally available. The user then falls back to the next budget that applies to them i.e., their cost center per-user budget or otherwise your universal budget . Previously, you had to remove every temporary budget override by hand, creating recurring cleanup work at enterprise scale. When you create or edit an individual user budget, you can choose: - No expiration, which is the default and matches current behavior. - Expiration at the start of the next billing cycle. - Expiration on a specific date. You can change or clear an expiration date at any time. Set an expiration date in your billing settings, or use the expires at field in the Budgets REST API when you create or update a budget. Expiration dates are available for the GitHub Copilot Business and Copilot Enterprise plans. Learn more about setting up budgets https://docs.github.com/enterprise-cloud@latest/billing/how-tos/set-up-budgets and the Budgets REST API https://docs.github.com/enterprise-cloud@latest/rest/billing/budgets .