Copilot Business Usage Billing Turns On by Default in CSP. Set the Limits Before It Does.

Microsoft is turning on usage-based billing by default for new Microsoft 365 Copilot Business purchases in CSP. If you resell Copilot Business, your clients' Copilot invoices are about to stop being a flat seat price.

Microsoft's November 2026 Partner Center announcements moved the rollout to Microsoft's fiscal Q3 of 2027, which is January through March 2027. The earlier date was December 1, 2026, and plenty of posts still quote it. You have a little more runway than you think. Not a lot.

Quick answer: When usage-based billing turns on for a Copilot Business tenant, metered Copilot features bill separately from the seat at a default limit of 4,000 Copilot Credits per user per month. It can't be fully turned off once configured, so MSPs should decide per client whether the limit is zero or a real allowance, set it before the client buys, name an approver for increases, and add a capped pass-through usage line to the quote.

What actually changes

Here is the short version from Microsoft's usage-based billing page for Copilot in Partner Center. Microsoft labels that page preliminary, so check it again before you build process on it.

Microsoft also says partners get at least 30 days in a sandbox before general availability. Use them.

Put the Copilot usage line on the quote

Scopable builds the quote from the client's Microsoft 365 data, so the seats, the credit cap, the approver, and your rollout labor land on one document the client signs. Start for free and quote your first Copilot client this week.

Start for free

Why the default limit matters

Microsoft's Copilot Credits guide prices pay-as-you-go credits at $0.01 each, billed in arrears.

Scenario math, not a forecast: 4,000 credits at $0.01 is $40 per user per month. A 25-seat client where everyone hit the default cap would add $1,000 a month to a bill they think is fixed. Most users won't get near that. The point is that the default ceiling is several times what a lot of MSPs charge per seat for support, and nobody at the client agreed to it.

Microsoft's list of metered features is short for now: Cowork, Work IQ APIs, and GitHub Copilot Harness. The Copilot apps people open every day aren't on it. The meter runs on the agent and API features, which are exactly the things a curious power user turns on during a pilot, and Microsoft says the list will grow.

What to set per client before rollout

Do this once per tenant, and write the decision down where the next tech can find it.

1. Pick the limit on purpose. For clients who aren't piloting agents, set the spending limit to zero. For pilots, set a user limit well under 4,000 and a tenant limit that matches the budget the client actually approved.
2. Name the approver. One person at the client approves any limit increase in writing. One person at the MSP raises it. Nobody else touches it.
3. Set the alert owner. Advanced spending policies live in the Microsoft 365 admin center under Copilot, then Cost management. Someone on your team should get the alert, not a shared mailbox nobody reads.
4. Watch how seats get added. Seats added through the Partner Center portal trigger usage billing. Seats added through the API do not, according to Microsoft's page. If your PSA or distributor provisions through the API, know which path each client is on.
5. Reconcile the meter monthly. Pull the billed usage reconciliation file, filter to the Copilot meter IDs, and match it to the client's invoice line. A usage charge you can't explain is a margin leak or a dispute, usually both.

If a client is already testing agents, pair this with the Work IQ API spend cap checklist. The Work IQ meter is one of the three that bills under this model today.

How to put it on the quote

The seat price you quoted last year is no longer the whole number. Fix that on paper before the first usage invoice does it for you.

Add a separate line for Copilot usage: pass-through, capped at the credit limit you set, billed monthly in arrears, with the client approver named for increases. Keep your rollout, governance, and support labor on their own lines so the client can see what's Microsoft's meter and what's your work. The AI billing guide for MSPs has the full threshold and approval model if you want to copy it.

If your quotes come out of a spreadsheet, this is where the stale-number problem bites. Scopable's MSP quoting software builds the quote from the client's live data, so the usage line, the cap, and the seats sit on the same document the client signs.

Put it on the next QBR

Every Copilot Business client should hear about this from you before they see it on an invoice. Bring the current limit, last month's metered usage, and the one decision you need from them: keep it at zero, or fund an allowance. That's a five-minute agenda item that makes you look like the adult in the room. If you're building QBR decks by hand, Scopable's vCIO software pulls the tenant data into the review so you're not screenshotting the admin center at midnight.