Playbooks · Teams
Set a spending policy before Copilot billing does
Written November 15, 2026
New Copilot Business licences arrive with usage-based billing on and a preset credit budget. How a spending policy is set, and when CSP changes it.
The default nobody picked
For new Microsoft 365 Copilot Business purchases, usage-based billing arrives switched on. Microsoft's November 2026 Partner Center announcements put it plainly: Microsoft automatically creates the required Azure resources and "applies a default spending limit for all eligible services of 4,000 Copilot Credits per user per month for all users in the customer's organization." Pay-as-you-go is the default billing configuration, new purchases also enable usage-based billing for existing Copilot Business licences already in the tenant, and the announcement warns that disabling usage-based billing might limit access to AI experiences. A 100-user tenant therefore starts with headroom of 400,000 credits a month under the default limit — Microsoft's own example — with charges based on actual usage. None of that required an admin to choose a number.
The CSP date moved — plan on the new one
If you buy through a partner, the date in older briefings is stale. The same Partner Center announcements record a November 3, 2026 update: usage-based billing will be enabled by default for new Copilot Business subscriptions purchased in CSP "during Microsoft's FY27 Q3 (January-March 2027), instead of December 1, 2026, as previously announced." The Partner Center sandbox date moved with it, and Microsoft says it will announce a specific date in advance and provide readiness guidance. The updated timelines apply across all markets, including Australia, Belgium, Brazil, France, Germany, India, Italy, Korea, the Netherlands, Poland, and Spain, where these capabilities were previously not expected to be available initially. The readiness window is longer than it looked a month ago — which makes now the cheap time to set policy, not a reason to skip it.
How a spending policy is actually set
The mechanics live in the Microsoft 365 admin center, under Copilot, then Cost Management. Microsoft's setup guide for usage-based billing walks the first run: sign in as a Global administrator or Billing administrator, open the Cost Management node, select Get Started, and a panel titled "Activate the default spending policy for your organization" opens. In it you choose the billing method and the default subscription other policies will inherit, set the monthly spending limit for the policy — including a "Don't limit monthly spending" option — and, optionally, set a monthly limit per user so one person cannot spend the whole pool. You then define alerts: email notifications at a credit amount or percentage threshold you choose, continuing daily until the monthly period resets or the policy changes. The default setup targets the entire organization; you can customize its scope to specific groups or services before selecting Activate. Roles are split on purpose: Global and Billing administrators handle billing methods, while AI administrators and License administrators can edit spending policies, limits, and alerts but cannot create policies.
Identity policies, resource policies, and the auto-apply switch
Microsoft's usage-based billing overview describes two policy shapes. Identity-based policies govern people: which users and groups can access supported services, and how much they can spend. Resource-based policies govern environments and agents. Copilot Studio sits on the resource side and is opt-in — the overview notes that existing Power Platform admin center controls continue to apply until a Microsoft 365 spending policy covers that scope, and the setup guide suggests starting with one environment before applying a policy to all environments. One setting deserves a deliberate decision either way: spending policies can automatically apply to future supported services and agents, and the overview states the Auto-apply new services setting "is enabled by default for spending policies." Leave it on and new services inherit your limits without a review; turn it off and each new service waits for an admin to add it. Microsoft's guidance for CSP and partner-managed customers covers the billing-account side of the same setup for partner-billed tenants.
What to do before the first bill
Set the tenant limit yourself instead of inheriting 4,000 credits per user per month by default, add the per-user limit the setup guide calls optional, and turn on threshold alerts so the first surprise arrives as an email, not an invoice. Decide the auto-apply question explicitly, and if Copilot Studio matters to you, plan its separate resource-based policy rather than assuming the identity policy covers it. CSP customers now have until the January–March 2027 rollout window to get this done; the work is the same whenever your channel's date lands.
Related playbooks
- Copilot's model-policy API is GA at four levels
- Set team plugin defaults for Copilot
- Copilot Agent Merge: watch a PR and fix its blockers
- The Copilot app now takes GHES accounts
Sources
- November 2026 announcements — Partner Center, Microsoft Learn
- Set up usage-based billing for Copilot Credits — Microsoft Learn
- Usage-Based Billing and Cost Management for Copilot Credits — Microsoft Learn
- Usage-based billing guidance for CSPs, partner-managed customers, and MACC — Microsoft Learn
Back to: Teams playbooks hub · Also: Stop an agent running up a bill · Check Copilot cloud sandbox billing first · Also: Audit agent blueprint creation in Entra