Repo sync

content/billing/managing-your-billing/gathering-insights-on-your-spending.md

@@ -82,9 +82,9 @@ You can view the usage of your {% data variables.enterprise.enterprise_or_org %}
 1. To request a CSV usage report, select **Get usage report** in the upper-right corner of the page.
 
    * For a breakdown of all metered usage, click **Metered billing usage report**.
-   * For a per user breakdown of additional premium requests, click **{% data variables.product.prodname_copilot_short %} premium requests usage report**.
+   * For a per user breakdown of premium requests for the last 45 days, click **{% data variables.product.prodname_copilot_short %} premium requests usage report**.
 
-   You can choose a pre-selected option or use the "Custom range" option to specify a date range of up to 31 days.
+   >[!TIP] The premium request usage report includes all premium requests, both within and beyond the allowance. By contrast, the metered billing usage report only reflects costs for requests beyond the allowance.
 
 ## Viewing license usage
 

content/billing/managing-your-billing/using-budgets-control-spending.md

@@ -132,7 +132,6 @@ As the owner of an enterprise or organization account, or as a billing manager,
 
 You can edit or delete a budget at any time, but you cannot change the scope of a budget after creating it.
 
-1. In the "Budgets and alerts" view, click **New budget**.
-1. Click **Budgets and alerts**.
-1. To edit a budget, in the list of budgets, click {% octicon "kebab-horizontal" aria-label="View actions" %} next to the budget you want to edit, and click **{% octicon "pencil" aria-hidden="true" aria-label="pencil" %} Edit** or **{% octicon "trash" aria-hidden="true" aria-label="trash" %} Delete**.
+1. Navigate to the "Budgets and alerts" view. See [Viewing budgets](#viewing-budgets).
+1. In the list of budgets, click {% octicon "kebab-horizontal" aria-label="View actions" %} next to the budget you want to edit, and click **{% octicon "pencil" aria-hidden="true" aria-label="pencil" %} Edit** or **{% octicon "trash" aria-hidden="true" aria-label="trash" %} Delete**.
 1. Follow the prompts.

content/copilot/concepts/copilot-billing/understanding-and-managing-requests-in-copilot.md

@@ -67,9 +67,10 @@ If you're on a **paid plan** and use all of your premium requests, you can still
 If you need more premium requests beyond your monthly allowance, you can:
 
 * Set a spending limit for additional premium requests. See [AUTOTITLE](/billing/managing-your-billing/using-budgets-control-spending).
-* Upgrade to a higher plan.
+* Upgrade your individual subscription to a higher plan.
+* If you're an enterprise owner, edit the default $0 budget or upgrade members to {% data variables.copilot.copilot_enterprise_short %}. See [AUTOTITLE](/copilot/how-tos/premium-requests/manage-for-enterprise).
 
-These actions can be taken by organization owners, billing managers, and personal account users.
+These actions can be taken by enterprise owners, organization owners, billing managers, and personal account users.
 
 > [!IMPORTANT] By default, all budgets are set to zero and premium requests over the allowance are rejected unless a budget has been created. Additional premium requests beyond your plan’s included amount are billed at {% data variables.copilot.additional_premium_requests %} per request.
 

content/copilot/get-started/choosing-your-enterprises-plan-for-github-copilot.md

@@ -61,9 +61,12 @@ With {% data variables.copilot.copilot_code-review_short %}, {% data variables.p
 
 ## How much will we benefit from premium requests?
 
-{% data reusables.copilot.premium-requests-for-enterprises %}
+Each {% data variables.product.prodname_copilot_short %} plan includes a per-user allowance for premium requests:
 
-To decide if you will benefit from a higher allowance for premium requests, compare the goals of your rollout to **development tasks** that each model is specialized in. For example, the {% data variables.copilot.copilot_claude_sonnet_40 %} is designed for advanced reasoning and coding tasks. Teams who work in specialized areas may require more requests to premium models. To learn about the benefits of different models, see [AUTOTITLE](/copilot/using-github-copilot/ai-models/choosing-the-right-ai-model-for-your-task).
+* 300 requests per user per month for {% data variables.copilot.copilot_business_short %}
+* 1000 requests per user per month for {% data variables.copilot.copilot_enterprise_short %}
+
+By ensuring members have access to enough premium requests, you can drive real business outcomes, such as reducing your backlog with {% data variables.copilot.copilot_coding_agent %}, accelerating pull requests with {% data variables.copilot.copilot_code-review_short %}, or increasing code quality with suggestions from more specialized models.
 
 Regardless of your plan, you can set a spending limit for premium requests over your plan's allowance. Premium requests over the allowance will be charged at a rate of {% data variables.copilot.additional_premium_requests %} per request, with an additional multiplier applied to certain models.
 

content/copilot/how-tos/administer/organizations/reviewing-activity-related-to-github-copilot-in-your-organization/reviewing-user-activity-data-for-copilot-in-your-organization.md

@@ -41,31 +41,11 @@ redirect_from:
 
 You can use {% data variables.product.prodname_dotcom %}'s REST API to get details about the assignment of {% data variables.product.prodname_copilot %} seats in your organization. See [Get Copilot seat information and settings for an organization](/rest/copilot/copilot-user-management?apiVersion=2022-11-28#get-copilot-seat-information-and-settings-for-an-organization), [List all Copilot seat assignments for an organization](/rest/copilot/copilot-user-management?apiVersion=2022-11-28#list-all-copilot-seat-assignments-for-an-organization), and [Get Copilot seat assignment details for a user](/rest/copilot/copilot-user-management?apiVersion=2022-11-28#get-copilot-seat-assignment-details-for-a-user).
 
-## Understanding the `last_activity_at` calculation
+## Troubleshooting `last_activity_at` data
 
-> [!NOTE] This data is in {% data variables.release-phases.public_preview %} and subject to change.
+If you believe a user's `last_activity_at` date should be more recent than shown in the CSV or API report, wait 24 hours and check again. If their recent Copilot usage is still not reflected in their `last_activity_at` date, have the user check that telemetry is enabled in their IDE settings.
 
-To align the `last_activity_at` data point with _actual usage_, the system returns the timestamp of a user's most recent interaction with Copilot functionality. These interactions are:
-
-* Receiving a code suggestion in an IDE
-* Chatting with Copilot Chat in an IDE
-{%- ifversion ghec %}
-* Creating or updating a knowledge base
-* Creating a pull request summary
-* Interacting with Copilot Chat in GitHub
-{%- endif %}
-* Interacting with Copilot on a mobile device
-* Interacting with Copilot Chat for CLI
-
-The `last_activity_at` date is consistent across the CSV generated via `Get Report` in Copilot Access settings as well as through {% data variables.product.prodname_dotcom %}'s REST API. The events which are tracked come from both client, and server-side telemetry. This allows the timestamp to be durable in the event that network conditions would impact client-telemetry.
-
-The retention period for `last_activity_at` data is 90 days. After 90 days of no new activity, a user's `last_activity_at` value is set to `nil`. The data retention period cannot be modified. For more information, see [Updating retention period for `last_activity_at` values on the Copilot user management API to 90 days](https://github.blog/changelog/2025-01-17-updating-retention-period-for-last_activity_at-values-on-the-user-management-api-public-preview-to-90-days/) on {% data variables.product.prodname_blog %}.
-
-### Troubleshooting `last_activity_at` data
-
-Processing new telemetry events and updating a user's `last_activity_at` date can take up to 24 hours. Users must have telemetry enabled in their IDE for their usage to be reflected in `last_activity_at`.
-
-If you believe a user's `last_activity_at` date should be more recent than shown in the CSV or API report, please wait 24 hours and check again. If their recent Copilot usage is still not reflected in their `last_activity_at` date, have the user check that telemetry is enabled in their IDE settings.
+For more information about this property, see [AUTOTITLE](/copilot/reference/metrics-data#last_activity_at).
 
 ## Further reading
 

content/copilot/how-tos/index.md

@@ -16,7 +16,7 @@ children:
   - /custom-instructions
   - /content-exclusion
   - /github-flow
-  - /monitoring-your-copilot-usage-and-entitlements
+  - /premium-requests
   - /personal-settings
   - /manage-your-account
   - /administer

content/copilot/how-tos/premium-requests/index.md

@@ -0,0 +1,13 @@
+---
+title: Premium requests for Copilot
+shortTitle: Premium requests
+intro: 'Manage and track premium requests for yourself or for your users.'
+versions:
+  feature: copilot
+topics:
+  - Copilot
+children:
+  - /monitoring-your-copilot-usage-and-entitlements
+  - /manage-for-enterprise
+---
+

content/copilot/how-tos/premium-requests/manage-for-enterprise.md

@@ -0,0 +1,64 @@
+---
+title: Managing the premium request allowance for users in your enterprise
+shortTitle: Manage allowance for members
+intro: 'Change the default spending limit or upgrade users to {% data variables.copilot.copilot_enterprise_short %}.'
+permissions: 'Enterprise owners'
+versions:
+  feature: copilot
+topics:
+  - Copilot
+allowTitleToDifferFromFilename: true
+product: '{% data variables.copilot.copilot_for_business %} or {% data variables.copilot.copilot_enterprise %}'
+---
+
+Each {% data variables.product.prodname_copilot_short %} plan includes a per-user allowance for premium requests. To learn more about premium requests, see [AUTOTITLE](/copilot/concepts/copilot-billing/understanding-and-managing-requests-in-copilot). For allowances per plan, see [AUTOTITLE](/copilot/get-started/plans-for-github-copilot#comparing-copilot-plans).
+
+By default, every enterprise has a $0 budget for the Premium Request SKU. Unless this budget is edited or deleted, your enterprise will have **no extra costs** for premium requests: when one of your licensed users exhausts the allowance in their plan, the user's premium requests will be rejected for the rest of the month.
+
+![Screenshot of the enterprise budgets page, with the default budget: a $0 budget for the Premium Request SKU.](/assets/images/help/copilot/enterprise-premium-request-budget.png)
+
+You can edit or delete this budget to grant extra requests to all your licensed members. If you want to grant extra requests to certain users only, you can upgrade those users to {% data variables.copilot.copilot_enterprise_short %}.
+
+## Prerequisites
+
+* Before making changes, download a usage report to see which developers are frequently hitting the limit or using a significant number of requests over the allowance. You may want to contact these users to understand their use cases and requirements. See [Downloading a monthly usage report](/copilot/how-tos/monitoring-your-copilot-usage-and-entitlements#downloading-a-monthly-usage-report).
+* If a user receives licenses from multiple enterprises or standalone organizations, the user must select a billing entity to use premium requests. See [Managing premium request billing with multiple {% data variables.product.prodname_copilot_short %} licenses](/copilot/managing-copilot/monitoring-usage-and-entitlements/monitoring-your-copilot-usage-and-entitlements#managing-premium-request-billing-with-multiple-copilot-licenses).
+
+## Changing the budget for all members
+
+To enable premium requests over the allowance for everyone, you can:
+
+* Delete the default $0 budget to allow **unlimited spending on premium requests** for all users.
+* Edit the "Budget amount" of the default $0 budget to set **a non-zero total spending limit** for premium requests in your enterprise.
+
+For instructions, see [AUTOTITLE](/billing/managing-your-billing/using-budgets-control-spending#editing-or-deleting-a-budget).
+
+>[!NOTE] Creating new budgets without deleting the $0 budget does not override the $0 budget. If **any** applicable budget with "Stop usage when budget limit is reached" enabled is exhausted, additional premium requests are blocked.
+
+## Upgrading users to {% data variables.copilot.copilot_enterprise_short %}
+
+You can upgrade certain users to increase their base allowance of premium requests.
+
+>[!TIP] {% data variables.copilot.copilot_business_short %} users who make make more than 800 premium requests per month would save money with a {% data variables.copilot.copilot_enterprise_short %} license.
+
+1. Create a new organization in your enterprise. See [AUTOTITLE](/enterprise-cloud@latest/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#creating-a-new-organization).
+1. Add the users who need more premium requests to the new organization.
+1. Grant {% data variables.copilot.copilot_enterprise_short %} licenses to all users in the organization.
+
+   1. If needed, upgrade the enterprise to {% data variables.copilot.copilot_enterprise_short %}. See [AUTOTITLE](/enterprise-cloud@latest/copilot/how-tos/administer/enterprises/managing-the-copilot-plan-for-your-enterprise/upgrading-copilot-for-your-enterprise).
+
+   1. Enable {% data variables.copilot.copilot_enterprise_short %} for the new organization. See [AUTOTITLE](/enterprise-cloud@latest/copilot/how-tos/administer/enterprises/managing-access-to-copilot-in-your-enterprise/enabling-copilot-for-organizations-in-your-enterprise).
+
+   1. Grant licenses to all users in the organization. See [AUTOTITLE](/copilot/how-tos/administer/organizations/managing-access-to-github-copilot-in-your-organization/granting-access-to-copilot-for-members-of-your-organization#granting-access-to-github-copilot-for-all-current-and-future-users-in-your-organization).
+
+1. Check the usage report regularly to ensure that {% data variables.copilot.copilot_enterprise_short %} remains the most cost-effective option for these users.
+
+## Setting a budget for specific members
+
+You can set a higher budget for premium requests over the allowance for specific users in your enterprise. However, you must ensure that every user in your enterprise is covered by a budget. Users who are not covered by a budget will have access to unlimited spending on premium requests.
+
+At a high level, the required steps are:
+
+1. Delete the default $0 budget.
+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/monitoring-your-copilot-usage-and-entitlements.md → content/copilot/how-tos/premium-requests/monitoring-your-copilot-usage-and-entitlements.md

@@ -11,6 +11,7 @@ redirect_from:
   - /copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/monitoring-usage-and-entitlements/monitoring-your-copilot-usage-and-entitlements
   - /copilot/managing-copilot/monitoring-usage-and-entitlements/monitoring-your-copilot-usage-and-entitlements
   - /copilot/managing-copilot/understanding-and-managing-copilot-usage/monitoring-your-copilot-usage-and-entitlements
+  - /copilot/how-tos/monitoring-your-copilot-usage-and-entitlements
 ---
 
 You can track your monthly usage of premium requests to help you get the most value from your {% data variables.product.prodname_copilot_short %} plan.
@@ -52,6 +53,8 @@ You can view your premium request usage at any time from your {% data variables.
 
 ### Downloading a {% data variables.product.prodname_copilot_short %} premium request usage report
 
+The premium request usage report includes all premium request usage, both within and beyond the allowance. By contrast, other metered billing reports only reflect costs for premium requests beyond the allowance.
+
 >[!NOTE]
 > For organizations and enterprises, only admins can download a usage report to understand {% data variables.product.prodname_copilot_short %} usage across their business. Individual members of the organization or enterprise cannot download the report for themselves.
 

content/copilot/reference/index.md

@@ -11,5 +11,6 @@ children:
   - /ai-models
   - /proxy-server-and-firewall-settings-for-copilot
   - /copilot-extensions
+  - /metrics-data
 ---
 

content/copilot/reference/metrics-data.md

@@ -0,0 +1,46 @@
+---
+title: Metrics data properties for GitHub Copilot
+shortTitle: Metrics data
+intro: 'See how GitHub calculates properties from APIs and reports.'
+versions:
+  feature: copilot
+topics:
+  - Copilot
+allowTitleToDifferFromFilename: true
+---
+
+## `last_activity_at`
+
+> [!NOTE] This data is in {% data variables.release-phases.public_preview %} and subject to change.
+
+The timestamp of a user's most recent interaction with {% data variables.product.prodname_copilot_short %} functionality.
+
+### Surfaces
+
+This property is consistent across the following surfaces:
+
+* The CSV report downloaded from the "Access management" page (see [AUTOTITLE](/copilot/how-tos/administer/organizations/reviewing-activity-related-to-github-copilot-in-your-organization/reviewing-user-activity-data-for-copilot-in-your-organization))
+* The [AUTOTITLE](/rest/copilot/copilot-user-management)
+
+### Calculation
+
+The following interactions count as activity:
+
+* Receiving a code suggestion in an IDE
+* Chatting with Copilot Chat in an IDE
+* Creating or updating a knowledge base
+* Creating a pull request summary
+* Interacting with Copilot Chat in GitHub
+* Interacting with Copilot on a mobile device
+* Interacting with Copilot Chat for CLI
+
+The tracked events come from both client- and server-side telemetry, ensuring the timestamp is durable if network conditions affect client-side telemetry.
+
+Processing new telemetry events and updating a user's `last_activity_at` date can take up to 24 hours. Users must have telemetry enabled in their IDE for their usage to be reflected in `last_activity_at`.
+
+### Retention period
+
+* The retention period for `last_activity_at` data is 90 days. This cannot be modified.
+* After 90 days of no new activity, a user's `last_activity_at` value is set to `nil`.
+
+For more information, see [Updating retention period for `last_activity_at` values on the Copilot user management API to 90 days](https://github.blog/changelog/2025-01-17-updating-retention-period-for-last_activity_at-values-on-the-user-management-api-public-preview-to-90-days/) on {% data variables.product.prodname_blog %}.