Cost · 05
Put the limit in three places
Microsoft describes spending controls at tenant, group and user level, with alerts. Learn's setup notes add a detail that is easy to miss: the default policy sets a tenant-level limit for all users, and each further policy has its own limit. It does not inherit the tenant figure. A new programme that sets one number and stops has not finished the job.
Tenant, then the exception
The tenant limit is the backstop. A group policy is how you let one team try Cowork without opening the meter for the whole company. A user limit is how you stop a single heavy session, or a single curious person, from using the group's allowance before anyone else has started.
Deleting a policy is not a refund
Learn is explicit that deleting a spending policy does not remove or reset credits already consumed. It only stops that policy governing the limit. Usage already incurred stays in the history. Do not treat 'delete the policy' as a way to undo a month.
Keep the fictional ledger boring
FrontierOrg, fiction, separates a board number from a departmental control so a green status cannot hide a red one. Your version is simpler: write the three limits down, even if two of them are 'not set, on purpose'.
Monday
Draft three lines: tenant limit, the one group allowed to spend, and the per-user ceiling inside that group. If a line is unset, say so.
Which group is allowed to find the limit first, and what are they supposed to do when they hit it?
Sources: Microsoft Learn, Set up usage-based billing for Copilot Credits (opens in a new tab). Microsoft Learn, Govern Copilot Credit consumption (opens in a new tab). Microsoft Learn, Managing AI experiences enabled by usage-based billing (opens in a new tab).
Where this note mentions FrontierOrg, that is a fictional method for rehearsing a decision. It is not a company, not a client, and not a case study.