MC1476200: Copilot usage-based billing turns on by default December 1. Set the spending policy before your tenant does it for you

Most admins file MC1476200 Copilot usage-based billing under "a CSP thing, December, someone else's invoice." It's closer than that. If you bought a Copilot Business seat directly from Microsoft after October 19, your tenant may already have an Azure subscription and a spending policy nobody on your team set up.

This is the decision we make with a tenant before the seat order goes through: which date applies to you, what the purchase builds, and the three ways to set the policy on purpose.

Which date applies: October 19 direct, December 1 CSP

MC1476200 has two start dates, and the one you remember is probably the wrong one. Eligible new Copilot Business purchases made directly from Microsoft, including the Microsoft 365 admin center, picked up the default on October 19, 2026. Purchases through a Cloud Solution Provider follow on December 1, 2026, which Partner Center moved from an earlier November 2 date.

Partner Center scopes it to Copilot Business (B-SKUs), standalone or bundled with Business Basic, Standard, or Premium. Microsoft 365 Copilot (Enterprise), education, nonprofit, and GCC aren't in this default. Microsoft also says the change won't initially be available in Australia, Belgium, Brazil, France, Germany, India, Italy, Korea, the Netherlands, Poland, and Spain.

What breaks it:

• Check how your last Copilot seats were bought — admin center purchase, or a CSP order. That tells you whether you're past the date or ahead of it.
• Ask your CSP what goes out after December 1 — a seat increase entered in the Partner Center portal triggers the same setup as a new subscription.
• Confirm your billing country — if it's on the excluded list, write down that you checked, and check again when Microsoft expands availability.

What one seat builds in your tenant

The purchase doesn't just license a user. If the tenant has no pay-as-you-go setup, Microsoft creates an Azure Plan, an Azure subscription, and a resource group for consumption, then applies a default spending policy: 4,000 Copilot Credits per user per month, with a tenant limit Partner Center lists at 1,200,000 credits. Charges only accrue when someone uses an eligible experience such as Copilot Cowork, Work IQ APIs, or GitHub Copilot Harness, and more services are expected over time.

Two details make this a tenant-wide change rather than a per-seat one. MC1476200 says buying a new Copilot Business seat "will deploy usage-based billing across all Microsoft 365 Copilot subscriptions in your tenant." And when more than one policy applies to a user, the least-restrictive policy wins. If any applicable policy is unlimited, that one always applies.

What breaks it:

• Look for an existing policy first. If one already exists from any channel or partner, Microsoft leaves it in place and doesn't create a duplicate, so whatever that policy allows is your real limit.
• Hunt for the unlimited policy — one leftover pilot policy with no cap overrides every careful 500-credit policy you add later.
• Name an owner for the new Azure subscription — it's billed through your Azure invoice, not the seat invoice, and that usually means a different reviewer.

Decide on purpose: cap it, scope it, or delete it

You can't opt out at checkout. There are three deliberate positions, and each one should be written down with a name next to it.

Keep it with lower caps. Bring the per-user and tenant limits down to what the pilot actually needs. Whichever cap is hit first is enforced, so a sensible tenant limit backs up a generous per-user limit. You can't go below the platform minimum.

Scope it. The default policy covers all users. In the Microsoft 365 admin center under Copilot > Cost management you can build policies for specific users, groups, or workloads, so Cowork is available to the five people piloting it, not to every licensed seat.

Delete it. Partner Center is explicit: deleting the policy is the only way to stop spend entirely. Billing for future usage stops immediately. Usage already accrued is still owed, and experiences that need usage-based billing stop working.

What "good" looks like: the five-move baseline

If you do nothing else before December 1, these five moves turn MC1476200 from a default into a decision:

1. Find every spending policy in Copilot > Cost management, including any unlimited one, before the next seat order.
2. Pick a position per policy — lower caps, scoped users, or deleted — and record who decided.
3. Set the tenant limit to a number someone would sign off on, not the default.
4. Tag the auto-created Azure subscription with an owner and a budget alert in Azure Cost Management.
5. Brief whoever places seat orders, internal or CSP, that one new seat changes billing for the whole tenant.

None of this needs a new license. It's a policy screen, an Azure subscription, and a calendar reminder. A billing default that creates Azure resources and a per-user credit allowance in your tenant is exactly the kind of spend nobody reviews until the invoice shows up, which is why our Cloud Cost Optimization audit now checks Copilot credit policies alongside unused licenses and right-sizing.

The uncomfortable question

Whether usage-based billing is on matters less than who in this tenant can spend Copilot Credits today, and how much, before anyone looks at a bill. Because the least-restrictive policy wins, the answer is your loosest policy, not your newest.

Open Cost Management in the Microsoft 365 admin center and read the spending policy view: scope, policy limit, user limit, and current-month usage. Copilot Studio cost controls are moving to the same place under MC1530368, expected generally available by November 20, so it's about to become the one screen for Copilot spend. If what's there doesn't match what you approved, the default has already made the decision for you.