You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/library/governance/recommendations/managing-ai-credits.md
+18-18Lines changed: 18 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -138,14 +138,13 @@ User-level budgets (ULBs) are recommended as the only hard enforcement caps, whi
138
138
139
139
### 2: Distinguish governance goals for included AI credits and additional spend
140
140
141
-
Design distinct governance approaches for each spending phase. A billing cycle has two phases: the included AI credits phase (where usage draws from the pre-paid pool) and the additional spend phase (where usage incurs additional charges after the pool is exhausted).
142
-
While it is useful to think about these phases separately, current controls do not fully isolate governance between them.
141
+
Design distinct governance approaches for each spending phase. A billing cycle has two phases: the included AI credits phase (where usage draws from the pre-paid pool) and the additional spend phase (where usage incurs additional charges after the pool is exhausted). While it is useful to think about these phases separately, current controls do not fully isolate governance between them.
142
+
143
+
For the included AI credits phase, the primary goal is fair access to a shared pool. Without guardrails, a small number of heavy users can exhaust the shared pool before others benefit. User-level budgets (ULBs) help moderate this behavior and promote more balanced consumption.
143
144
144
-
For the included AI credits phase, the primary goal is fair access to a shared pool.
145
-
Without guardrails, a small number of heavy users can exhaust the shared pool before others benefit. User-level budgets (ULBs) serve as the primary mechanism to moderate this behavior and promote more balanced consumption.
146
145
For the additional spend phase (post-pool spend), the goal shifts to controlling financial exposure. Enterprise and cost center budgets help cap the additional cost your organization is willing to incur.
147
146
148
-
With UBB, the controls overlap rather than operate independently by phase. ULBs apply across both included credits and additional spend, while enterprise and cost center budgets apply only after the included credits are exhausted. As a result, ULBs serve a dual role: ensuring fair consumption of the shared pool while also acting as a guardrail on overall usage. Enterprise and cost center budgets remain the primary controls for managing additional spend exposure.
147
+
With UBB, the controls overlap rather than operate independently by phase. ULBs span both included credits and additional spend, while enterprise-level and cost center budgets take effect only after the included credits are exhausted. As a result, ULBs serve a dual role: ensuring fair consumption of the shared pool while also acting as a guardrail on overall usage. Enterprise-level and cost center budgets remain the primary controls for managing additional spend exposure.
149
148
150
149
Maintaining this distinction keeps your governance approach coherent. It clarifies the different goals at each phase — fair consumption during the included AI credits phase and cost control during the additional spend phase.
151
150
@@ -311,7 +310,7 @@ Example scenario 2:
311
310
#### Enable self-serve usage monitoring
312
311
313
312
Provide users and cost owners with a way to check their own consumption so they can
314
-
self-govern usage before hitting their ULB and cost center budgets. For example, users can [view usage in their IDE](https://docs.github.com/en/copilot/how-tos/manage-and-track-spending/monitor-premium-requests#viewing-usage-in-your-ide).
313
+
self-govern usage before hitting their ULB and cost center budgets. For example, users can [view usage in their IDE](https://docs.github.com/copilot/how-tos/manage-and-track-spending/monitor-premium-requests#viewing-usage-in-your-ide) - see [supported versions](https://docs.github.com/copilot/how-tos/manage-and-track-spending/prepare-for-your-move-to-usage-based-billing#update-your-ide-client-and-extension).
315
314
316
315
### Step 3: Set the enterprise-level additional spend budget
317
316
@@ -370,7 +369,7 @@ still apply simultaneously (ULB, cost center budget, and enterprise-level budget
370
369
{{< /callout >}}
371
370
372
371
When creating a cost center, you need to choose either
373
-
**organization** or **user-based** scope. See [Management methods](https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/billing/premium-request-management).
372
+
**organization** or **user-based** scope. See [Management methods](https://docs.github.com/enterprise-cloud@latest/copilot/concepts/billing/premium-request-management).
374
373
375
374
Recommend **user-based cost centers** when your organizational
376
375
structure does not map cleanly to budget ownership, or when users frequently
@@ -462,7 +461,7 @@ of heavy users from exhausting the shared pool before others can benefit.
462
461
463
462
GitHub provides a downloadable CSV usage report.
464
463
This data includes `aic_quantity` (AI credits consumed) and
465
-
`aic_gross_amount` (estimated USD cost). Build a reporting pipeline that maps usage to users and cost centers, and surface insights to inform budget adjustments and model guidance. See [Prepare for usage based billing](https://docs.github.com/en/copilot/how-tos/manage-and-track-spending/prepare-for-usage-based-billing).
464
+
`aic_gross_amount` (estimated USD cost). Build a reporting pipeline that maps usage to users and cost centers, and surface insights to inform budget adjustments and model guidance. See [Prepare for usage based billing](https://docs.github.com/copilot/how-tos/manage-and-track-spending/prepare-for-usage-based-billing).
466
465
467
466
#### Cost attribution approaches
468
467
@@ -482,9 +481,9 @@ consumption further. Provide users with guidance on:
482
481
-**Responsible context usage:** Minimize unnecessary context in instructions to
483
482
reduce token consumption.
484
483
-**Model selection by task complexity:** Match model tier to the task. See
-[Usage management methods in enterprise](https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/billing/premium-request-management)
606
-
-[Monitoring your GitHub Copilot usage and entitlements](https://docs.github.com/en/copilot/how-tos/manage-and-track-spending/monitor-premium-requests)
607
-
-[Prepare for usage-based billing](https://docs.github.com/en/copilot/how-tos/manage-and-track-spending/prepare-for-usage-based-billing)
608
-
-[Viewing your usage of metered products and licenses](https://docs.github.com/en/billing/how-tos/products/view-productlicense-use)
-[Usage management methods in enterprise](https://docs.github.com/enterprise-cloud@latest/copilot/concepts/billing/premium-request-management)
605
+
-[Monitoring your GitHub Copilot usage and entitlements](https://docs.github.com/copilot/how-tos/manage-and-track-spending/monitor-premium-requests)
606
+
-[Update your IDE, client, and extension](https://docs.github.com/copilot/how-tos/manage-and-track-spending/prepare-for-your-move-to-usage-based-billing#update-your-ide-client-and-extension)
607
+
-[Prepare for usage-based billing](https://docs.github.com/copilot/how-tos/manage-and-track-spending/prepare-for-usage-based-billing)
608
+
-[Viewing your usage of metered products and licenses](https://docs.github.com/billing/how-tos/products/view-productlicense-use)
0 commit comments