How do spending policies stop runaway Copilot Credits?

You’re right to treat metered Copilot Credits as a Cost & Value problem, not a “flip the switch and see.” Open discovery without a spending fence is how programmes get an Azure surprise before the pilot even has a name.

Here’s what’s going on. In the Microsoft 365 admin center, Copilot → Cost Management lets admins create spending policies that control who may use AI experiences enabled by usage-based billing, which agents/services are in scope, and what monthly credit budgets apply at policy and (optionally) per-user level. You pick a billing method (capacity packs, Copilot Credit Pre-Purchase Plan / P3 on an Azure subscription, and/or pay-as-you-go), set alerts when usage hits a threshold, and can turn Auto-apply new services on or off so tomorrow’s metered agent doesn’t land in an unlimited policy by accident. When users hit a limited monthly budget, they lose access to those agents and services until the month resets. Users can sit in more than one policy; Microsoft picks one by highest per-user limit (then overall limit, then newest) — limits don’t stack. Moving a user between Entra groups mid-month carries their consumption history forward, so they can’t reset the meter by changing teams. Reader roles can watch the Consumption tab without editing policies; Global/Billing admins own billing methods; AI and License admins can shape policies and alerts. This Cost Management surface currently gates experiences such as Cowork and Work IQ API — it is not a substitute for Copilot Studio environment capacity packs or per-agent hard stops in the Power Platform admin center.

Steady before scale puts Pane 06 (Cost & Value) in front of shiny discovery. Schofield’s First Law (historically attributed) still applies: don’t put the organisation on a meter you can’t read back out of — use Overview/Consumption and the Copilot Credits report before you widen the circle.

Options that actually work:

1. Activate a default spending policy with a hard monthly limit and a per-user cap, leave Auto-apply on only if you want new services governed immediately, and route credit requests through Finance or ServiceNow via a custom request policy. Best Steady default.
2. Pilot with a security-group-scoped policy (makers or a named wave), unlimited tenant default off or tightly capped elsewhere. Good for Wave 0.
3. Unlimited monthly budget “to unblock innovation.” Predictable surprise for Finance; one power user can burn the month.
4. Assume Cost Management covers every Copilot Studio meter and SharePoint agent PAYG path. It doesn’t — keep PPAC capacity allocation and agent monthly limits in the same FinOps register.

12 Panes action / comms: Tell Finance: Spending policies are limit fences, not credit allocations — prepaid still depletes first. Tell AI admins: Cost Management for tenant metered experiences; PPAC for Studio capacity and per-agent hard stops. Users: If you hit a limit, request more credits through the approved path — don’t chase shadow tools.

Benefits / risks: Caps and alerts buy calm adoption; billing method can’t be changed after create (delete and recreate); CSP/partner and MACC tenants must wire the right Azure billing account or committed funds won’t apply. Product names and which services sit under this dashboard will keep expanding — verify against Learn for your tenant.

I’d suggest this week: stand up a limited default policy, add one pilot-group policy, turn Auto-apply off on anything that shouldn’t auto-inherit new meters, and put Overview + Consumption on the FinOps weekly. You’ll have Steady Cost under metered AI without waiting for an invoice to teach the lesson.

DIGITAL SKILL WORKS LTD / 12 PANES · You ask, we answer