18584 billing enable premium request and feature level budgeting for ai tools ga (#58263)

Co-authored-by: Copilot <[email protected]>
Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: Felicity Chapman <[email protected]>

Author: 4 people

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

@@ -11,6 +11,9 @@ contentType: concepts
 
 Usage of {% data variables.product.prodname_copilot_short %} is measured through a combination of licenses and monthly usage tracking. For more information about how license costs in {% data variables.product.prodname_copilot_short %} work, see [AUTOTITLE](/billing/concepts/product-billing/github-copilot-licenses).
 
+> [!IMPORTANT]
+> {% data reusables.billing.pru-sku-split-notice %}
+
 ## What are premium requests?
 
 Some {% data variables.product.prodname_copilot_short %} features use premium requests.
@@ -21,8 +24,15 @@ Examples include:
 * Using {% data variables.copilot.copilot_chat_short %} with premium models
 * Large context windows or advanced reasoning models
 * Features like {% data variables.copilot.copilot_coding_agent %}
+* {% data variables.product.prodname_spark_short %} app creation
+
+Each product's premium request usage is attributed to a premium request SKU:
+
+* **Copilot premium requests** - Chat, CLI, Code Review, Extensions, and Spaces
+* **{% data variables.product.prodname_spark_short %} premium requests** - {% data variables.product.prodname_spark_short %} app creation
+* **{% data variables.copilot.copilot_coding_agent %} premium requests** - {% data variables.copilot.copilot_coding_agent %} sessions
 
-See [AUTOTITLE](/copilot/concepts/billing/copilot-requests) for details on which models and features consume premium requests.
+See [AUTOTITLE](/copilot/concepts/billing/copilot-requests) for details on which models and features consume premium requests and their SKU attribution.
 
 ## How usage of premium requests is measured
 
@@ -50,14 +60,17 @@ If you receive licenses from multiple enterprises, you must choose which entity
 When you use {% data variables.copilot.copilot_coding_agent %}, including any {% data variables.copilot.copilot_custom_agents %}, both **{% data variables.product.prodname_actions %} minutes** and **premium requests** are consumed:
 
 * **{% data variables.product.prodname_actions %} minutes** come from your account’s monthly allowance of free minutes for {% data variables.product.github %}-hosted runners. This allowance is shared with all {% data variables.product.prodname_actions %} workflows. See [AUTOTITLE](/billing/managing-billing-for-github-actions/about-billing-for-github-actions#included-storage-and-minutes).
-* **Premium requests** come from your monthly allowance of premium {% data variables.product.prodname_copilot_short %} requests. This allowance is shared with other features, such as {% data variables.copilot.copilot_chat_short %}.
+* **Premium requests** come from the monthly allowance associated with your {% data variables.product.prodname_copilot_short %} license. This allowance is shared with other features, such as {% data variables.copilot.copilot_chat_short %}.
 
 Each coding agent **session** consumes one premium request. A session begins when you:
+
 * Ask {% data variables.product.prodname_copilot_short %} to create or edit a pull request
 * Assign {% data variables.product.prodname_copilot_short %} to an issue
 
 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 variables.copilot.copilot_coding_agent %} uses a dedicated {% data variables.copilot.copilot_coding_agent %} premium request SKU. This SKU still pulls from your monthly allowance of premium requests, but allows for more granular budget control and monitoring.
+
 For more information about {% data variables.copilot.copilot_coding_agent %} and {% data variables.copilot.copilot_custom_agents %}, see [AUTOTITLE](/copilot/concepts/about-copilot-coding-agent) and [AUTOTITLE](/copilot/concepts/agents/coding-agent/about-custom-agents).
 
 ## Using more than your included premium requests
@@ -70,8 +83,9 @@ If you exceed your allowance, set a budget for additional premium requests or up
 
 ### Organizations and enterprises
 
-* Admins can control whether members are allowed to exceed their allowance using the **Premium request paid usage** policy. See [AUTOTITLE](/copilot/how-tos/manage-and-track-spending/manage-request-allowances).
-* Budgets can be set to either monitor or block overages.
+* Admins can control whether members are allowed to exceed their premium request allowance across AI features using the **Premium request paid usage** policy.
+* Separate policy options are available for Copilot, {% data variables.product.prodname_spark_short %}, and {% data variables.copilot.copilot_coding_agent %}. See [AUTOTITLE](/copilot/how-tos/manage-and-track-spending/manage-request-allowances).
+* Premium request budgets can be set to either monitor or block overages, with options for bundled or individual SKU management.
 * Enterprises can also upgrade frequent users to {% data variables.copilot.copilot_enterprise_short %} for higher included allowances.
 
 ## Paying for premium requests
@@ -84,19 +98,25 @@ If you are billed through Azure, premium request usage appears on your Azure inv
 
 To help manage your budget for premium requests, consider the following strategies.
 
-### Personal accounts
+### Budget options for personal accounts
 
-You can set a budget in your personal billing settings to receive alerts when you reach 75%, 90%, or 100% of your budget.
+You can set a budget in your personal billing settings to receive alerts when you reach 75%, 90%, or 100% of your budget. Setting a premium request budget depends on the level of granularity you need:
 
-### Organizations and enterprises
+* **Bundled premium request budget** - Combines all premium requests into a single budget (Recommended for most users)
+* **Individual SKU budgets** - Set separate budgets for each AI product (Copilot, {% data variables.product.prodname_spark_short %}, {% data variables.copilot.copilot_coding_agent %})
+
+### Budget options for organizations and enterprises
 
 You can set budgets at the organization, enterprise, or cost center level. If you enable **stop usage when budget is reached**, extra premium requests are blocked when the budget runs out.
 
+For detailed setup instructions, see [AUTOTITLE](/billing/tutorials/set-up-budgets).
+
 {% data reusables.copilot.zero-budget-changes-link %}
 
 ## Monitoring usage
 
 * Track your monthly usage in your IDE, in {% data variables.product.prodname_copilot_short %} settings on {% data variables.product.prodname_dotcom %}, or by downloading a usage report.
 * Usage reports show all premium requests, both within and beyond the allowance, and can be used to identify high-usage users.
+* Premium request analytics display usage by dedicated SKUs, providing detailed insights into which AI products consume your allowance.
 
-For more information about monitoring your usage, see [AUTOTITLE](/copilot/managing-copilot/understanding-and-managing-copilot-usage/monitoring-your-copilot-usage-and-entitlements).
+For more information about monitoring your usage, see [AUTOTITLE](/copilot/how-tos/manage-and-track-spending/monitor-premium-requests).

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

@@ -19,7 +19,31 @@ contentType: concepts
 
 ## Billing for {% data variables.product.prodname_spark_short %} app creation
 
-Each prompt consumes 4 premium requests, which draw from your plan's premium request allowance. If you have enabled premium requests over your plan's allowance, additional premium requests beyond your plan’s included amount are billed at {% data variables.copilot.additional_premium_requests %} per request, meaning that one prompt to {% data variables.product.prodname_spark_short %} would cost **$0.16**. See [AUTOTITLE](/copilot/concepts/copilot-billing/understanding-and-managing-requests-in-copilot).
+Each prompt consumes 4 premium requests, which draw from your plan's premium request allowance. If you have enabled premium requests over your plan's allowance, additional premium requests beyond your plan's included amount are billed at {% data variables.copilot.additional_premium_requests %} per request, meaning that one prompt to {% data variables.product.prodname_spark_short %} would cost **$0.16**. See [AUTOTITLE](/copilot/concepts/copilot-billing/understanding-and-managing-requests-in-copilot).
+
+> [!NOTE]
+> Beginning November 1, 2025, {% data variables.product.prodname_spark_short %} premium requests are attributed to a dedicated **{% data variables.product.prodname_spark_short %} Premium Requests** SKU instead of the shared {% data variables.product.prodname_copilot_short %} premium request SKU. This provides better cost visibility and allows you to set separate budgets specifically for {% data variables.product.prodname_spark_short %} usage.
+
+## Managing {% data variables.product.prodname_spark_short %} costs
+
+You now have more granular options for managing {% data variables.product.prodname_spark_short %} costs:
+
+### Budget options
+
+* **Bundled budget**: Combine {% data variables.product.prodname_spark_short %} premium requests with other AI product costs in a single premium request budget for simplified management.
+* **Individual product budget**: Set a dedicated budget specifically for {% data variables.product.prodname_spark_short %} for granular cost control.
+
+For detailed information about setting up budgets, see [AUTOTITLE](/billing/tutorials/set-up-budgets).
+
+### Analytics and monitoring
+
+With the dedicated SKU, you can:
+
+* Track {% data variables.product.prodname_spark_short %} usage separately from other {% data variables.product.prodname_copilot_short %} features in billing analytics
+* Set up alerts when {% data variables.product.prodname_spark_short %} usage approaches budget limits
+* Generate reports specifically for {% data variables.product.prodname_spark_short %} premium request consumption
+
+For monitoring guidance, see [AUTOTITLE](/copilot/how-tos/manage-and-track-spending/monitor-premium-requests).
 
 ## Billing and limits for {% data variables.product.prodname_spark_short %} app deployment
 

content/billing/tutorials/set-up-budgets.md

@@ -47,12 +47,14 @@ We recommend that you avoid creating overlapping budgets for the use of a produc
 You can set budgets and receive alerts when your usage of a product reaches 75%, 90%, or 100% of a defined budget. Budgets can be set for a specific repository or for your whole account.
 
 {% data reusables.user-settings.access_billing_settings_url %}
+
 1. Click **Budgets and alerts**.
 1. To create a new budget, click **New budget**.
-1. Under "Budget Type" select either **Product-level budget** or **SKU-level budget**.
+1. Under "Budget Type" select **Product-level budget**, **SKU-level budget**, or **Bundled premium requests budget**.
 
    * To limit spending at a Product-level, in "Product-level budget" choose a product from the dropdown, for example: {% data variables.product.prodname_codespaces %}.
    * To limit spending at a SKU-level, in "SKU-level budget" choose a Product and then a SKU, for example: {% data variables.product.prodname_codespaces %} and {% data variables.product.prodname_codespaces %} storage.
+   * To limit spending on premium requests across all features, enable "Bundled premium requests budget" or to limit spending for a specific feature, set a SKU-level budget for the feature (such as {% data variables.product.prodname_copilot_short %} premium requests, {% data variables.product.prodname_spark_short %} premium requests, or {% data variables.copilot.copilot_coding_agent %} premium requests).
 
 1. Under "Budget scope", set the scope of spending for this budget.
 1. Under "Budget", set a budget amount.
@@ -68,12 +70,16 @@ To edit or delete a budget, on the "Budget and alerts" page, click **Edit** or *
 
 ## Managing budgets for your organization or enterprise
 
+> [!IMPORTANT]
+> * {% data reusables.billing.pru-sku-split-notice %} 
+> * Existing {% data variables.product.prodname_copilot_short %} premium request budgets will automatically migrate to a **bundled premium requests budget** on November 1, 2025. This ensures that your budget continues to account for all of your premium request usage.
+
 You can set budgets and receive alerts when your usage of a product or license type reaches 75%, 90%, or 100% of a defined budget. For budgets that control metered use of a product, you can also block further use when the budget is exhausted. Each budget has a scope.
 
 * **Organization budget scopes**: the whole organization or a single repository within the organization
 * **Enterprise budget scopes**:
-   * Metered products: the whole enterprise, a single organization, a single repository, or a single cost center
-   * Enterprise licenses (metered): the whole enterprise or a single cost center
+  * Metered products: the whole enterprise, a single organization, a single repository, or a single cost center
+  * Enterprise licenses (metered): the whole enterprise or a single cost center
 
 ### Viewing budgets
 
@@ -95,11 +101,11 @@ If you are an organization owner, enterprise owner, or billing manager, any acco
 As the owner of an enterprise or organization account, or as a billing manager, you can set a budget at the account level, or at any level below this.
 
 1. In the "Budgets and alerts" view, click **New budget**.
-1. Under "Budget Type" select either **Product-level budget** or **SKU-level budget**.
+1. Under "Budget Type" select **Product-level budget**, **SKU-level budget**, or **Bundled premium requests budget**.
 
    * To limit spending at a Product-level, in "Product-level budget" choose a product from the dropdown, for example: {% data variables.product.prodname_codespaces %}.
    * To limit spending at a SKU-level, in "SKU-level budget" choose a Product and then a SKU, for example: {% data variables.product.prodname_copilot_short %} and {% data variables.product.prodname_copilot_short %} Premium Request.
-
+To limit spending on premium requests across all features, enable "Bundled premium requests budget" or to limit spending for a specific feature, set a SKU-level budget for the feature (such as {% data variables.product.prodname_copilot_short %} premium requests, {% data variables.product.prodname_spark_short %} premium requests, or {% data variables.copilot.copilot_coding_agent %} premium requests).
 1. Under "Budget scope", set the scope of spending for this budget.
 1. Under "Budget", set a budget amount.