diff --git a/CHANGELOG.md b/CHANGELOG.md index 4f1fd0187a32..c4cca58a4635 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,11 @@ # Docs changelog +**4 February 2026** + +We've published a new tutorial on [using GitHub Copilot coding agent to improve a project](https://docs.github.com/copilot/tutorials/coding-agent/improve-a-project). + +
+ **20 January 2026** We published the first iteration of the [GitHub Copilot feature matrix](https://docs.github.com/en/copilot/reference/copilot-feature-matrix) to provide customers with the latest information about which Copilot features are available by which IDE/version. diff --git a/content/copilot/concepts/billing/index.md b/content/copilot/concepts/billing/index.md index 71da8663b21f..4cbec6b93e59 100644 --- a/content/copilot/concepts/billing/index.md +++ b/content/copilot/concepts/billing/index.md @@ -11,10 +11,10 @@ children: - /individual-plans - /billing-for-individuals - /organizations-and-enterprises + - /premium-request-management redirect_from: - /managing-copilot/managing-copilot-as-an-individual-subscriber/billing-and-payments - /copilot/managing-copilot/understanding-and-managing-copilot-usage - /copilot/concepts/copilot-billing contentType: concepts --- - diff --git a/content/copilot/concepts/billing/premium-request-management.md b/content/copilot/concepts/billing/premium-request-management.md new file mode 100644 index 000000000000..3de83e8002ad --- /dev/null +++ b/content/copilot/concepts/billing/premium-request-management.md @@ -0,0 +1,69 @@ +--- +title: Management methods for premium request usage in an enterprise +shortTitle: Premium request management +intro: 'Learn about organization and user-based control of premium requests for enterprises.' +permissions: Enterprise owners and organization owners +product: '{% data variables.copilot.copilot_enterprise_short %} or {% data variables.copilot.copilot_business_short %}' +versions: + feature: copilot +topics: + - Copilot +contentType: concepts +category: + - Manage Copilot for a team +--- + +## Management methods + +The best way to control budgets for premium requests in an enterprise is to create cost centers and scope one or more budgets to each center. + +When you want to set different limits on additional premium requests for different subsets of users, there are two possible budget management approaches. + +* **Organization-based:** Each cost center is assigned one or more organizations. +* **User-based:** Each cost center is assigned one or more users. + +These options provide flexibility for managing the cost of premium requests, but involve tradeoffs and careful decision making. + +{% rowheaders %} + +| Considerations | Organization-based | User-based | +|----|----|----| +| Identity provider integration | SCIM supported | No support | +| {% data variables.product.prodname_copilot_short %} license assignment | Single organization only | Not relevant | +| REST API automation | Supported | Supported | + +{% endrowheaders %} + +See [AUTOTITLE](/billing/tutorials/use-cost-centers#creating-a-cost-center) and [AUTOTITLE](/rest/enterprise-admin/billing) or [open source utilities for automating cost center administration](https://github.com/github/cost-center-automation) in the `/github/cost-center-automation` repository on {% data variables.product.prodname_dotcom_the_website %}.. +With organization-based management, the costs of {% data variables.product.prodname_copilot_short %} and {% data variables.product.prodname_enterprise %} licenses are allocated to the cost center. With user-based management, the costs of all paid licenses are allocated to the cost center. See [AUTOTITLE](/billing/reference/cost-center-allocation). + +## Organization-based management example + +An enterprise with the following properties would be a good candidate for organization-based management: + +* Uses System for Cross-domain Identity Management (SCIM) to provision organization and team membership from the identity provider, which facilitates centralized management of {% data variables.product.prodname_copilot_short %} licenses. +* Users are already grouped into organizations that match the differential budgets planned. +* Most users are assigned a {% data variables.product.prodname_copilot_short %} license through a single organization. +* Any users who are currently assigned licenses through multiple organizations will be identified and their license assignment revised. + +For example, there are a total of 25 {% data variables.product.prodname_copilot_short %} users, and you want to permit additional premium requests for only 10 users. All 10 of those users must be assigned {% data variables.product.prodname_copilot_short %} licenses through a single organization, separate from the organization that assigns licenses to the remaining 15 users. + +For information about preparing your enterprise for organization-based management, see: + +* [AUTOTITLE](/copilot/reference/copilot-billing/seat-assignment) +* [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-access/disable-for-organizations) +* [AUTOTITLE](/billing/tutorials/use-cost-centers) + +## User-based management example + +An enterprise with the following properties would be a good candidate for user-based management: + +* Organization membership does not align with the differential budgets planned. +* Many users are assigned a {% data variables.product.prodname_copilot_short %} license through multiple organizations. +* You want to allocate costs for {% data variables.product.prodname_enterprise %}, {% data variables.product.prodname_GH_cs_and_sp %} licenses using the same grouping of users. + +For example, organizations in your company represent workstreams and not users in different roles. You want to make additional premium requests available to a small subset of users across different organizations. There are a total of 25 {% data variables.product.prodname_copilot_short %} users, and you want to permit additional premium requests for only 10 users. You assign the 10 users directly to one cost center and the remaining 15 to a second cost center. You set a budget of $0 for premium requests to the second cost center, and a higher budget for the first cost center. + +## Next steps + +* [AUTOTITLE](/copilot/how-tos/manage-and-track-spending/manage-request-allowances) diff --git a/content/copilot/how-tos/manage-and-track-spending/manage-request-allowances.md b/content/copilot/how-tos/manage-and-track-spending/manage-request-allowances.md index 032cf7f6c21d..1109a2228f0b 100644 --- a/content/copilot/how-tos/manage-and-track-spending/manage-request-allowances.md +++ b/content/copilot/how-tos/manage-and-track-spending/manage-request-allowances.md @@ -21,10 +21,13 @@ category: Each {% data variables.product.prodname_copilot_short %} plan includes a per-user allowance for premium requests. If enabled, requests over the allowance are billed to your organization or enterprise. To learn more about premium requests, see [AUTOTITLE](/copilot/concepts/copilot-billing/requests-in-github-copilot). For allowances per plan, see [AUTOTITLE](/copilot/get-started/plans-for-github-copilot#comparing-copilot-plans). -Your organization or enterprise's policies and budgets determine whether users can use premium requests over their included allowance: +Premium request usage beyond the allowance is governed by two complementary control layers: -* The **Premium request paid usage** policy determines whether users can surpass their included premium request allowance for each AI tool. This policy is enabled by default. -* If your enterprise or organization has a **Bundled premium requests budget** that caps usage, all premium request-powered tools are blocked once the budget amount is reached for the billing period. +* **Policy setting:** The **Premium request paid usage** policy determines whether users can surpass their included premium request allowance for each AI tool. This policy is enabled by default. +* **Budget constraints:** If your enterprise or organization has a premium request SKU-level budget or a bundled premium requests budget, premium request usage will be blocked once the budget is fully consumed for the billing period. + + +The **Premium request paid usage policy** must be enabled for any additional billing to occur. Budgets then control whether and when usage is stopped. You can increase the allowance for users by ensuring the policy is enabled, editing your budgets, or upgrading users to {% data variables.copilot.copilot_enterprise_short %}. @@ -34,6 +37,8 @@ You can increase the allowance for users by ensuring the policy is enabled, edit * 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 [AUTOTITLE](/billing/how-tos/products/view-productlicense-use). * 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). +* For enterprises only, review which organizations are able to assign and are actively assigning {% data variables.product.prodname_copilot_short %} access to users. See [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-access/grant-access#enabling-copilot-for-organizations). + ## Setting a policy for paid usage @@ -55,6 +60,9 @@ You can set the policy for an enterprise or a standalone organization. Creating new budgets without deleting an existing budget does not override the existing budget. If **any** applicable budget with "Stop usage when budget limit is reached" enabled is exhausted, additional premium requests are blocked. + Enterprise-level budgets act as a failsafe for the entire enterprise, including any spending originating from within cost centers. If the enterprise budget is exhausted before the cost center budget, usage will be blocked. See [AUTOTITLE](/billing/concepts/budgets-and-alerts) for details on different scopes of budgets and stopping usage. + + ## Upgrading users to {% data variables.copilot.copilot_enterprise_short %} An enterprise owner can upgrade certain users to increase their base allowance of premium requests. @@ -73,14 +81,35 @@ An enterprise owner can upgrade certain users to increase their base allowance o 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 +## Organization-based premium request management -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. +With this budget management method, budgets are scoped to cost centers with organizations as the managed resource. -At a high level, the required steps are: +Users must be assigned a {% data variables.product.prodname_copilot_short %} license through only a single organization in the enterprise. If users are currently assigned licenses through multiple organizations within your enterprise, you must either update your assignment practices or use user-based management. For a comparison of methods, see [AUTOTITLE](/copilot/concepts/billing/premium-request-management). -1. Ensure the "Premium request paid usage" policy is enabled. See [Setting a policy for paid usage](#setting-a-policy-for-paid-usage). -1. If there is a $0 budget for premium requests set at your enterprise or organization account level, delete it. +### Setting up organization-based cost centers + +1. Create a cost center and assign all organizations that contain users where no additional premium requests are required. These organizations should be the organizations that assign each user their {% data variables.product.prodname_copilot_short %} license. Assign a $0 budget to this cost center. +1. Create a second cost center and assign organizations with users who need access to additional premium requests. These organizations should be the organizations that assign each user their {% data variables.product.prodname_copilot_short %} license. Assign a budget to this cost center. +1. If you need more than one tier of budgets for additional premium requests, create further cost centers. + +You should define a SKU-level budget for "`FEATURE` Premium Request", not a product-level budget for "{% data variables.product.prodname_copilot_short %}". Alternatively, use "Bundled premium requests budget" to define a budget for all types of premium requests. + +>[!NOTE] +> Creating a budget scoped directly to the organization is an option, but it is not recommended due to how organization-scoped budgets interact with cost center-scoped budgets for cost centers that contain users as resources. + +## User-based premium request management + +With this budget management method, budgets are scoped to cost centers with users as the managed resource. When a user is added directly as a managed resource to a cost center, this takes precedence over the user being a member of any organizations that are managed resources in any cost centers. + +User-based management applies to all metered, licensed products. See [AUTOTITLE](/billing/reference/cost-center-allocation#details-for-license-based-products). + +> [!NOTE] +> If your business needs to allocate license costs for {% data variables.product.prodname_copilot %} and {% data variables.product.prodname_enterprise %} separately from costs for {% data variables.product.prodname_GHAS_cs_or_sp %}, you must use organization-based management. + +### Setting up user-based cost centers + +1. Create a cost center to contain each subset of users that needs a distinct limit on premium requests. +1. Assign the appropriate budget for premium requests to each cost center. -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 **Bundled premium requests 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. +You should define a SKU-level budget for "`FEATURE` Premium Request", not a product-level budget for "{% data variables.product.prodname_copilot_short %}". Alternatively, use "Bundled premium requests budget" to define a budget for all types of premium requests.