Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 12 additions & 16 deletions content/library/governance/recommendations/managing-ai-credits.md
Original file line number Diff line number Diff line change
Expand Up @@ -136,22 +136,18 @@ and user-level budgets prevent individual overconsumption of shared resources.

User-level budgets (ULBs) are recommended as the only hard enforcement caps, while enterprise and cost center budgets act as monitoring guardrails unless explicitly configured to stop usage.

### 2: Separate included AI credits governance from additional spend governance

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). For the included AI credits phase, use ULBs to
prevent any single user from exhausting the shared pool before others benefit.
For the additional spend phase (post-pool spend), use enterprise and cost
center budgets to cap the additional cost your organization is willing to incur.

All budget layers apply at all times; this separation keeps your governance model coherent. ULBs are your tool for
fair consumption of the shared pool. Enterprise and cost center budgets are
your tool for controlling incremental cost exposure. Mixing their purposes —
for example, relying only on the enterprise-level budget while ignoring ULBs — leaves
the pooled AI credits ungoverned and vulnerable to a few heavy users
draining it before month-end.
### 2: Distinguish governance goals for included AI credits and additional spend

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.

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) serve as the primary mechanism to moderate this behavior and promote more balanced consumption.
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.

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.

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.

### 3: Establish cost attribution before you optimize

Expand Down
4 changes: 3 additions & 1 deletion content/library/overview/release-notes/2026-q2.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,4 +3,6 @@
## 2026 Q2

- **New Content: [Governing agents in GitHub Enterprise](/library/governance/recommendations/governing-agents/)** - Published governance and policy guidance for managing GitHub Copilot agents across the enterprise, covering policy configuration, security boundaries, MCP server governance, and audit pipelines
- **New Content: [Essentials of governance and administration with GitHub Enterprise](/library/governance/recommendations/governance-administration-essentials/)** - Published a comprehensive guide for enterprise governance and administration fundamentals, covering structural components, user access models, organization architecture strategies, policy baselines, and operational topics such as billing, repository governance, and audit logging
- **New Content: [Essentials of governance and administration with GitHub Enterprise](/library/governance/recommendations/governance-administration-essentials/)** - Published a comprehensive guide for enterprise governance and administration fundamentals, covering GitHub structural components, user access models, org architecture strategies, policy baselines, and operational topics such as integrations, roles, and audit logging
- **New Content: [Managing AI credits](/library/governance/recommendations/managing-ai-credits/)** - Published a FinOps-oriented guide for governing AI credit consumption across GitHub Enterprise, covering layered budgets design, cost attribution, usage guidance, and an operating cadence
- **Deprecated: Managing GitHub Copilot Premium Request Units (PRUs)** - Retired the PRU enterprise admin playbook, replaced by the managing AI credits guidance