Consumption-based controls
Proposed framework for Copilot Cowork and Copilot Credits, Perplexity Computer and API Portal consumption. These remain separately governed capabilities; the framework below is the common control set applied to each.
Scroll horizontally to view all columns.
| Control | Requirement |
|---|---|
| Approved scope | Each consumption-based capability has a defined set of approved use cases and audiences. Access outside that scope requires a new approval. |
| Budget ownership | Every allocation of credits or quota has a named budget owner, cost centre and authorised approver before it is enabled. |
| Approval thresholds | Consumption above a defined level requires explicit approval from the budget owner, and above a higher level from the central governance owner. |
| Alerts and limits | Alert thresholds and hard or soft limits are configured before access is enabled, so that unexpected consumption is detected early. |
| Reporting | Regular consumption reporting is provided to the budget owner and to central governance, with a common definition of the units being reported. |
| Periodic review | High-consumption use cases and pooled allocations are reviewed periodically for value, alternative lower-cost workflows and continued need. |
| User guidance | Users receive practical guidance distinguishing lighter search and chat workflows from compute-heavy or agentic workflows, so that consumption choices are informed. |
| Separation of capabilities | Copilot Cowork and Copilot Credits, Perplexity Computer and API Portal tokens are approved, funded, reported and reviewed separately. Credits or quota approved for one capability are not transferable to another. |
| No access promise before the gate | No consumption-based capability is offered, announced or promised to users before its commercial, billing, control, reporting and support arrangements are approved. |