Repo sync

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

@@ -9,22 +9,22 @@ category:
   - Track spending and control costs
 ---
 
-Budgets and alerts allow you to track spending on metered products for your enterprise, organizations, cost centers (enterprise only), and repositories. Budgets and alerts are not available for pre-paid volume licenses.
+Budgets and alerts allow you to track spending on metered products for your enterprise, organizations, cost centers (enterprise only), users, and repositories. Budgets and alerts are not available for pre-paid volume licenses.
 
 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.
 
 ## Stopping usage
 
 For most license-based products such as {% data variables.product.prodname_copilot %}, {% data variables.product.prodname_team %}, and {% data variables.product.prodname_enterprise %}, setting a budget does not prevent usage over the budget amount but does provide alerts. {% data variables.product.prodname_GHAS %} SKUs are an exception to this, as they can be set to stop usage when the budget amount is reached. See [AUTOTITLE](/billing/concepts/product-billing/github-advanced-security#hard-budgets-for-github-advanced-security-skus).
 
-For metered products such as {% data variables.product.prodname_actions %} or {% data variables.product.prodname_copilot %} premium requests, you can choose for budgets to prevent usage once the budget amount is reached.
+For metered products such as {% data variables.product.prodname_actions %} or {% data variables.product.prodname_copilot_short %} {% data variables.product.prodname_ai_credits_short %}, you can set budgets to prevent usage once the budget threshold is reached.
 
 ## Types and scopes
 
 Each budget has a type and a scope that define which paid use contributes to spending against the budget.
 
 * **Type**: Defines which metered product or SKU is measured.
-* **Scope**: Defines whether the budget applies to the whole account, or to a subset of repositories, organizations, or cost centers (enterprise only).
+* **Scope**: Defines whether the budget applies to the whole account, or to a subset of repositories, organizations, cost centers (enterprise only), or users. User-scoped budgets are currently only supported for {% data variables.product.prodname_copilot_short %} {% data variables.product.prodname_ai_credits_short %}. There are two types: a universal budget that applies to all licensed users by default, and individual budgets that override the universal for specific users. See [AUTOTITLE](/copilot/concepts/billing/budgets-for-usage-based-billing).
 
 ## Budget alerts
 

content/billing/concepts/enterprise-billing/combined-enterprise-use.md

@@ -38,7 +38,9 @@ There are two types of {% data variables.product.prodname_enterprise %} (GHE) li
 * **GHE (Usage-based, also called metered)**: A cloud-first license where users must first be assigned to a {% data variables.product.prodname_ghe_cloud %} organization.
     * All Cloud users automatically receive a right to use {% data variables.product.prodname_ghe_server %}.
     * Billing is based on the number of active users each month.
-    * Users can generate their own Server license, which covers the number of assigned Cloud seats at the time of generation and is valid for one year.
+    * Users can generate their own Server license, and the seat count is based on the number of consumed enterprise Cloud licenses at the time of generation. The license is valid for one year.
+
+      You can find your enterprise's consumed Cloud license count on your enterprise's **Billing & Licensing > Licensing** page. Do **not** use the "Total consumed" licenses count on the **People > Members** page: that number will be higher than the Cloud-only count used for license generation.
     * Server-only users will be added to GHE (Metered) billing. These users are de-duplicated with email matching to avoid double billing.
 
 * **GHE (Volume/Subscription, also called GHE Unified)**: A bundled license for both {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}.
@@ -57,7 +59,7 @@ There are two types of {% data variables.product.prodname_enterprise %} (GHE) li
 | **Cloud vs. Server**             | Cloud-first, with a Server use right for Cloud users | 1 user license covers both Cloud and Server (hybrid, Cloud-only, or Server-only)              |
 | **Setup**            | Self-service | Manual setup via {% data variables.product.github %} Sales                                    |
 | **Server license generation**    | Users generate their own {% data variables.product.prodname_ghe_server %} license | Enterprise owners download their own {% data variables.product.prodname_ghe_server %} license |
-| **License file scope**        | Covers Cloud-assigned users at time of generation | Covers all purchased users for both Cloud and Server                                          |
+| **License file scope**        | Covers consumed Cloud licenses at time of generation | Covers all purchased users for both Cloud and Server                                          |
 | **License expiration**           | Expires in 12 months | Aligned with volume license term                                                              |
 | **License key usage**            | Limits max Server users | Covers all users in the volume subscription                                                   |
 | **Required {% data variables.product.prodname_enterprise %} version**        | {% data variables.product.prodname_enterprise %} 3.13+, with {% data variables.product.prodname_github_connect %} | No specific version required                                                                  |

content/billing/concepts/enterprise-billing/ghes-license-files.md

@@ -17,6 +17,8 @@ In order to use a {% data variables.product.prodname_ghe_server %} instance, you
 
 A license file has an expiration date and controls the number of people who can use {% data variables.location.product_location_enterprise %}. After you download and install {% data variables.product.prodname_ghe_server %}, you must upload the license file to unlock the application for you to use.
 
+If your enterprise uses metered (usage-based) billing, the seat count in your license file is based on the number of consumed Cloud licenses at the time you generated the license. To see this count, go to your enterprise's **Billing & Licensing > Licensing** page.
+
 If your license expires, you won't be able to access {% data variables.product.prodname_ghe_server %} via a web browser or Git. If needed, you will be able to use command-line utilities to back up all your data.
 
 ## Next steps

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

@@ -31,6 +31,15 @@ For **private repositories**, each {% data variables.product.github %} account r
 > [!TIP]
 > Anyone with write access to a repository can run actions. Any costs of running the actions are billed to the repository owner.
 
+### {% data variables.copilot.copilot_code-review_short %} and {% data variables.product.prodname_actions %} minutes
+
+Each {% data variables.copilot.copilot_code-review_short %} consumes {% data variables.product.prodname_actions %} minutes in addition to {% data variables.product.prodname_ai_credits_short %}.
+
+* **Private repositories:** Minutes are consumed from your account or organization's existing plan entitlement. Any usage beyond your included minutes is billed at standard {% data variables.product.prodname_actions %} rates.
+* **Public repositories:** Minutes remain free.
+
+{% data variables.copilot.copilot_code-review_short %} runs on standard {% data variables.product.github %}-hosted Ubuntu Linux runners by default. You can also configure {% data variables.actions.github_hosted_larger_runners %} or self-hosted runners via Actions Runner Controller (ARC), which are billed at different rates.
+
 ## How storage billing works
 
 {% data variables.product.prodname_actions %} storage billing operates on an **hourly accrual model**:
@@ -48,11 +57,13 @@ It's important to understand the difference between what you see on {% data vari
 * **Accrued storage:** The cumulative total of storage used throughout the billing cycle (determines your bill)
 
 **When you delete artifacts:**
+
 * Current storage decreases immediately
 * Future hourly charges stop accumulating
 * Storage already accrued during the current billing cycle remains in your total and will appear on your bill
 
 **Example (30-day billing cycle):** If you store 10 GB of artifacts for 10 days, then delete everything on day 11:
+
 * Days 1-10: Accruing 240 GB-Hours per day (10 GB × 24 hours)
 * Day 11: Delete artifacts → current storage drops to 0 GB
 * Days 11-30: Accruing 0 GB-Hours (no storage)
@@ -63,11 +74,13 @@ Deleting artifacts reduces your current storage and prevents future charges, but
 ### Storage measurement units
 
 {% data variables.product.prodname_actions %} measures storage in **binary gigabytes (GB)**, where:
+
 * 1 GB = 2^30 bytes = 1,073,741,824 bytes
 * This is also known as a gibibyte (GiB)
 * 1 GB = 1,024 megabytes (MB)
 
 **Billing calculations use GB-Hours:**
+
 * 1 GB-Hour = 1 GB of storage for 1 hour
 * Example: Storing 3 GB for 10 days = 720 GB-Hours (3 GB × 10 days × 24 hours)
 
@@ -109,6 +122,7 @@ The following amounts of time for standard runners, artifact storage, and cache
 {% data reusables.billing.actions-included-quotas %}
 
 The use of standard {% data variables.product.github %}-hosted runners is free:
+
 * In public repositories
 * For {% data variables.product.prodname_pages %}
 * For {% data variables.product.prodname_dependabot %}
@@ -117,6 +131,7 @@ The use of standard {% data variables.product.github %}-hosted runners is free:
 >
 > * Larger runners are always charged for, even when used by public repositories or when you have quota available from your plan.
 > * The storage amounts shown are **shared** with {% data variables.product.prodname_registry %}. This means your total storage across Actions artifacts, Actions caches, and Packages cannot exceed the included amount for your plan.
+> * {% data variables.copilot.copilot_code-review_short %} consumes {% data variables.product.prodname_actions %} minutes on private repositories. For public repositories, {% data variables.product.prodname_actions %} minutes remain free.
 
 ## Using more than your included quota
 

content/billing/concepts/product-billing/github-code-quality.md

@@ -19,12 +19,12 @@ category:
 
 When {% data variables.product.prodname_code_quality_short %} is generally available, scanning repositories will incur two types of costs for an organization:
 
-* Premium requests
+* {% data variables.product.prodname_ai_credits_short %}
 * {% data variables.product.prodname_actions %} minutes needed to run the scans unless you use self-hosted runners
 
 ### For the {% data variables.release-phases.public_preview %}
 
-When you scan private repositories during the {% data variables.release-phases.public_preview %}, you **will not be billed** for premium request usage, but {% data variables.product.prodname_actions %} minutes **will be consumed**.
+When you scan private repositories during the {% data variables.release-phases.public_preview %}, you **will not be billed** for {% data variables.product.prodname_ai_credits_short %} usage, but {% data variables.product.prodname_actions %} minutes **will be consumed**.
 
 To view consumption of actions by the `{% data variables.code-quality.workflow_name_billing %}` workflow, download a detailed usage report from the "Billing and licensing" tab. See [AUTOTITLE](/billing/how-tos/products/view-productlicense-use).
 

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

@@ -0,0 +1,25 @@
+---
+title: GitHub Copilot billing
+intro: '{% data variables.product.prodname_copilot_short %} usage is measured and billed according to your plan.'
+versions:
+  feature: copilot
+contentType: concepts
+category:
+  - Understand product costs
+---
+
+{% data variables.product.prodname_copilot_short %} usage is measured in {% data variables.product.prodname_ai_credits_short %}—a usage-based billing unit where 1 {% data variables.product.prodname_ai_credit_singular %} = {% data variables.product.prodname_ai_credits_value %}.
+
+## Individual plans
+
+All individual plans—{% data variables.copilot.copilot_free_short %}, {% data variables.copilot.copilot_pro_short %}, {% data variables.copilot.copilot_pro_plus_short %}, and {% data variables.copilot.copilot_max_short %}—include a monthly {% data variables.product.prodname_ai_credits %} allowance that varies by plan.
+
+To understand how {% data variables.product.prodname_ai_credits_short %} work for individual plans, see [AUTOTITLE](/copilot/concepts/billing/usage-based-billing-for-individuals).
+
+## Organizations and enterprises
+
+For organizations and enterprises, each assigned {% data variables.product.prodname_copilot_short %} license comes with a monthly amount of included {% data variables.product.prodname_ai_credits_short %}, which can be pooled at the billing entity level.
+
+* To understand how {% data variables.product.prodname_ai_credits_short %} work and what happens when your pool is exhausted, see [AUTOTITLE](/copilot/concepts/billing/usage-based-billing-for-organizations-and-enterprises).
+* To understand budget controls and how to prevent unexpected charges, see [AUTOTITLE](/copilot/concepts/billing/budgets-for-usage-based-billing).
+* To compare per-token costs across models and how they translate to {% data variables.product.prodname_ai_credits_short %}, see [AUTOTITLE](/copilot/reference/copilot-billing/models-and-pricing).

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

@@ -15,21 +15,15 @@ category:
   - Understand product costs
 ---
 
-<!-- expires 2026-06-01 -->
-
-{% data reusables.copilot.ubb-announcement-cfi-cb-ce %}
-
-<!-- end expires 2026-06-01 -->
-
-Usage of {% data variables.product.prodname_copilot %} is measured through a combination of licenses and monthly usage tracking. For more information about how usage costs in {% data variables.product.prodname_copilot_short %} work, see [AUTOTITLE](/billing/concepts/product-billing/github-copilot-premium-requests).
+Usage of {% data variables.product.prodname_copilot %} is measured through a combination of licenses and {% data variables.product.prodname_ai_credits_short %}. See [AUTOTITLE](/copilot/concepts/billing/usage-based-billing-for-individuals) and [AUTOTITLE](/copilot/concepts/billing/usage-based-billing-for-organizations-and-enterprises).
 
 ## Licenses for {% data variables.product.prodname_copilot_short %}
 
 {% data variables.product.prodname_copilot_short %} licenses are required for each user who uses {% data variables.product.prodname_copilot_short %}. Licenses are available through different plans depending on your account type.
 
 | Account type      | Options                                                                 |
 |-------------------|-------------------------------------------------------------------------|
-| **Personal accounts** | <ul><li>{% data variables.copilot.copilot_pro_short %}: {% data variables.copilot.cfi_price_per_month %} per calendar month.</li><li>{% data variables.copilot.copilot_pro_plus_short %}: {% data variables.copilot.cpp_price_per_month %} per calendar month.</li><li>{% data variables.copilot.copilot_student_short %}: access to {% data variables.product.prodname_copilot_short %} premium features at no cost.</li><li>{% data variables.copilot.copilot_free_short %}: limited access to {% data variables.product.prodname_copilot_short %} features at no cost.</li></ul> |
+| **Personal accounts** | <ul><li>{% data variables.copilot.copilot_pro_short %}: {% data variables.copilot.cfi_price_per_month %} per calendar month.</li><li>{% data variables.copilot.copilot_pro_plus_short %}: {% data variables.copilot.cpp_price_per_month %} per calendar month.</li><li>{% data variables.copilot.copilot_max_short %}: {% data variables.copilot.cm_price_per_month %} per calendar month.</li><li>{% data variables.copilot.copilot_student_short %}: access to {% data variables.product.prodname_copilot_short %} premium features at no cost.</li><li>{% data variables.copilot.copilot_free_short %}: limited access to {% data variables.product.prodname_copilot_short %} features at no cost.</li></ul> |
 | **Organizations** | {% data variables.copilot.copilot_business_short %}: {% data variables.copilot.cfb_price_per_month %} per user per month (billed monthly). |
 | **Enterprises**   | Choose {% data variables.copilot.copilot_business_short %} or {% data variables.copilot.copilot_enterprise_short %}, or mix them across organizations. Both are billed monthly, pricing varies. |
 
@@ -42,7 +36,7 @@ There are several ways to use {% data variables.product.prodname_copilot_short %
 ### {% data variables.copilot.copilot_free_short %}
 
 * Provides limited access to {% data variables.product.prodname_copilot_short %} features at no cost.
-* Includes a monthly allowance of completions and premium requests.
+* Includes a monthly allowance of completions and limited chat and agent usage.
 * Intended for **individual use only** (not suitable for organizations or enterprises).
 * For usage beyond the free plan limits, upgrade to {% data variables.copilot.copilot_pro_short %}.
 
@@ -97,12 +91,10 @@ To help manage your budget for {% data variables.product.prodname_copilot_short
 * You can set budgets for your personal account to receive email alerts at 75%, 90%, and 100% of the budget.
 * Budgets help you monitor spending but do not stop license charges.
 
+{% data reusables.copilot.plans.ai-cap-recommend-upgrade %}
+
 For more information about using budgets to control spending, see [AUTOTITLE](/billing/managing-your-billing/using-budgets-control-spending).
 
 ### Organizations and enterprises
 
-* Owners and billing managers can set budgets at the organization or enterprise level, or by cost center.
-* Budgets for licenses are monitoring-only: spending can exceed the budget, but alerts notify you when thresholds are reached.
-* Use cost centers to track spending across teams or initiatives.
-
-For more information about managing company spending, see [AUTOTITLE](/copilot/how-tos/spending/manage-company-spending).
+Owners and billing managers can set budgets at the user, organization, cost center, and enterprise level to monitor and control {% data variables.product.prodname_ai_credits_short %} consumption. See [AUTOTITLE](/copilot/tutorials/budgets/getting-started-with-budget-controls).