[Copilot-assisted] Add change notices for upcoming $0 budget removal for Copilot premium requests (#57549)

Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com>
Co-authored-by: Holly 🦒 <104800384+holly-kassel@users.noreply.github.com>
Co-authored-by: Vanessa <vgrl@github.com>

Author: 4 people

content/billing/concepts/budgets-and-alerts.md

@@ -15,7 +15,7 @@ Budgets and alerts allow you to track spending on metered products for your ente
 
 By setting a monthly budget, you can monitor your spending and receive notifications by email when your spending exceeds certain preset percentages of your budget threshold. This can help you stay within your budget and avoid overspending.
 
-Many accounts already have default budgets for certain products. {% data reusables.billing.migrated-budgets %}
+{% data reusables.billing.migrated-budgets %}
 
 ## Stopping usage
 

content/billing/concepts/product-billing/github-copilot.md

@@ -83,7 +83,7 @@ If you run out of free Actions minutes or free premium requests, and you have se
 
 If you run out of free minutes or premium requests, and you have _not_ set up billing, a message is displayed explaining why {% data variables.product.prodname_copilot_short %} cannot work on the task.
 
-{% data reusables.copilot.zero-budget-changes %} See [AUTOTITLE](/copilot/how-tos/premium-requests/manage-for-enterprise).
+{% data reusables.copilot.zero-budget-changes-link %}
 
 ### Monitoring your use of Actions minutes and premium requests
 

content/copilot/concepts/billing/copilot-requests.md

@@ -73,7 +73,7 @@ If you need more premium requests beyond your monthly allowance:
 * For an individual subscription, set a budget for additional premium requests or upgrade to a higher plan. See [AUTOTITLE](/billing/managing-your-billing/using-budgets-control-spending).
 * If you're an enterprise or organization owner, ensure that the "Premium request paid usage" policy is enabled and that extra spending is not prevented by a budget. See [AUTOTITLE](/copilot/how-tos/premium-requests/manage-for-enterprise).
 
-{% data reusables.copilot.zero-budget-changes %}
+{% data reusables.copilot.zero-budget-changes-link %}
 
 ## Model multipliers
 

content/copilot/how-tos/manage-and-track-spending/manage-company-spending.md

@@ -41,7 +41,7 @@ This report includes all premium request usage by user, both within and beyond t
 
 Your organization or enterprise's policies and budgets determine whether users can use premium requests over their included allowance. See [AUTOTITLE](/copilot/how-tos/premium-requests/manage-for-enterprise).
 
-{% data reusables.copilot.zero-budget-changes %}
+{% data reusables.copilot.zero-budget-changes-link %}
 
 ## Mapping spending to groups of users
 

content/copilot/how-tos/manage-and-track-spending/manage-request-allowances.md

@@ -74,6 +74,7 @@ You can set a higher budget for premium requests over the allowance for specific
 At a high level, the required steps are:
 
 1. Ensure the "Premium request paid usage" policy is enabled. See [Setting a policy for paid usage](#setting-a-policy-for-paid-usage).
-1. Delete the default $0 budget if it applies to your organization or enterprise.
+1. If there is a $0 budget for premium requests set at your enterprise or organization account level, delete it.
+
 1. Create a new budget for the users who need a higher allowance. For example, create an organization or cost center containing just these users, then create a Premium Request SKU budget for the organization or cost center.
 1. Create a separate, more restrictive budget that covers every other {% data variables.product.prodname_copilot_short %} user in your enterprise. You will likely need to integrate with the API to ensure that this budget covers new users as they are added to your enterprise.

content/copilot/how-tos/manage-and-track-spending/monitor-premium-requests.md

@@ -85,16 +85,18 @@ You can use the following strategies to maximize the value of your premium reque
 
 * **Choose the right model for the task**. Some models are better suited to different tasks. If you're using a premium request, you can strategically choose which model you use to get the best result from {% data variables.product.prodname_copilot_short %}. See [AUTOTITLE](/copilot/reference/ai-models/model-comparison).
 
-* **Setting a budget**. Set a budget to track your overages and receive alerts when you reach 75%, 90%, or 100% of your budget. See [AUTOTITLE](/billing/managing-your-billing/preventing-overspending#managing-budgets-for-your-personal-account).
+* **Define whether users can use premium requests over their included allowance**. Set a policy to control whether users can incur extra costs for premium requests when they use up their included allowance. See [AUTOTITLE](/copilot/how-tos/manage-and-track-spending/manage-request-allowances).
 
-  {% data reusables.copilot.zero-budget-changes %}
+* **Setting a budget**. Set a budget to track your overages and receive alerts when you reach 75%, 90%, or 100% of your budget. See [AUTOTITLE](/billing/managing-your-billing/preventing-overspending#managing-budgets-for-your-personal-account).
 
 * **Monitor your usage regularly**. Check your usage in your {% data variables.product.github %} account settings to see how many premium requests you’ve used. This helps you plan how much you can use for the rest of the month.
 
 * **Upgrade if needed**. If you find yourself consistently hitting your monthly allowance, consider upgrading to a plan with more premium requests included.
 
 * **Avoid retrying large prompts unnecessarily**. Submitting the same long or complex prompt multiple times may use more premium requests. Try rephrasing or simplifying your request when needed.
 
+{% data reusables.copilot.zero-budget-changes-link %}
+
 ## Managing premium request billing with multiple {% data variables.product.prodname_copilot_short %} licenses
 
 If you have {% data variables.product.prodname_copilot_short %} licenses from multiple standalone organizations or enterprises, you must define which entity is charged for your use of premium requests. Until you define a billing entity, all premium requests you make will be rejected.

data/reusables/copilot/zero-budget-changes-link.md

@@ -0,0 +1,7 @@
+<!-- expires 2026-01-10 -->
+<!-- Check with HC on whether or not references to this reusable can be deleted.
+See pr 57549 for details. -->
+
+{% data reusables.copilot.zero-budget-changes %} See [AUTOTITLE](/copilot/how-tos/manage-and-track-spending/manage-request-allowances#setting-a-policy-for-paid-usage).
+
+<!-- end expires 2026-01-10 -->

data/reusables/copilot/zero-budget-changes.md

@@ -1,3 +1,12 @@
-Many accounts have a default $0 budget for {% data variables.product.prodname_copilot_short %} premium requests. Premium requests over the allowance are rejected unless this budget is edited or deleted.
+<!-- expires 2026-01-10 -->
+<!-- Check with HC on whether or not references to this reusable can be deleted.
+See pr 57549 for details. -->
 
-> [!NOTE] Accounts with a **{% data variables.copilot.copilot_business_short %}** or **{% data variables.copilot.copilot_enterprise_short %}** plan that started after August 22, 2025, do **not** have the default $0 budget, and premium requests are uninterrupted by default. You can limit spending on premium requests by creating a budget or disabling the "Premium request paid usage" policy.
+Accounts created **before August 22, 2025** have a default $0 budget for {% data variables.product.prodname_copilot_short %} premium requests. Premium requests over the allowance are rejected unless you edit or delete this budget.
+
+> [!IMPORTANT]
+> **Beginning November 18, 2025:**
+>
+> **Account-level $0 {% data variables.product.prodname_copilot_short %} premium request budgets** for {% data variables.product.prodname_enterprise %} and {% data variables.product.prodname_team %} will be removed. See [Upcoming removal of Copilot premium request $0 budgets for enterprise and team accounts](https://github.blog/changelog/2025-09-17-upcoming-removal-of-copilot-premium-request-0-budgets-for-enterprise-and-team-accounts/) in the {% data variables.product.github %} changelog.
+
+<!-- end expires 2026-01-10 -->