We Buy One More Copilot Business Seat After October 19. Does Usage Billing Turn On Across Our Whole Tenant, and What Does the 4,000-Credit Default Cost?

The short answer

Yes. For existing Microsoft 365 Copilot customers, buying one new Copilot Business seat turns on usage-based billing across every Microsoft 365 Copilot subscription in the tenant [Verified MC1476200].

Microsoft Message Center MC1476200 (updated October 1, 2026) and Partner Center October 2026 announcements set the dates and the default:

• October 19, 2026: eligible new Copilot Business purchases made directly from Microsoft (Microsoft web and the Microsoft 365 admin center) [Verified MC1476200].
• December 1, 2026: eligible new purchases through Cloud Solution Provider (CSP) resellers. Microsoft moved this from November 2 [Verified Partner Center] [Verified MC1476200].
• Default spending limit: 4,000 Copilot Credits per user per month, adjustable by admins [Verified MC1476200] [Verified Partner Center].
• List credit price: $0.01 per Copilot Credit [Reported CRN]. That puts the default ceiling at about $40 per user per month on top of the seat (4,000 × $0.01) [Derived].
• Microsoft's own example: 100 Copilot Business users can consume up to 400,000 credits a month under the default [Verified Partner Center]. At $0.01, that is up to $4,000 a month [Derived].

Charges follow actual use. Admins can change the limit. Set your own spending policy before the next seat purchase, or Microsoft's default becomes the policy [Verified MC1476200].

Copilot Business is sold for tenants with up to 300 seats [Reported CRN]. Confirm seat count and list seat price on your own quote. Seat list price is omitted here until a Microsoft pricing page or Message Center line confirms it.

Sources: MC1476200 as republished by Modern Workspace Pro; Partner Center October 2026 announcements.

What changed on October 1

September coverage (CRN; MSSP Alert repeating Nov 2 as late as Oct 6) said nothing bills until an admin creates a spending policy, and kept the CSP date at November 2.

The October 1 update to MC1476200 reads differently. On an eligible new purchase, Microsoft "will automatically create the required Azure resources and apply a spending policy that enables usage-based billing including default spending limits and future eligible services" [Verified MC1476200]. Partner Center moved the CSP effective date to December 1 and named the 4,000-credit default [Verified Partner Center].

So the policy arrives with the purchase. If your team read the September coverage and parked this, reopen it.

What stays the same, per the notice [Verified MC1476200]:

• Existing Copilot Business subscription benefits and payment terms.
• Capabilities already in your license.
• Any spending policy you already configured. It stays in place.

What the meter covers

Microsoft Learn lists the services managed by usage-based billing for Microsoft 365 Copilot [Verified Learn] (overview):

• Cowork (Copilot license required)
• Advanced work in SharePoint and in OneDrive (Copilot license required)
• Work IQ API for custom apps and agents
• Copilot Managed Runtime
• Teams Phone Agent

The Partner Center notice also names GitHub Copilot Harness as an eligible usage-based experience [Verified Partner Center].

Two settings matter for your budget:

1. Auto-apply new services is on by default. Future supported services and agents join the policy without a new approval unless an admin turns it off [Verified Learn].
2. A limited budget stops access. When users hit a limited monthly budget, "they lose access to agents and services for the rest of the month until credits reset on the first of the month." Prepaid credits (P3 or capacity packs) are used first, then pay-as-you-go [Verified Learn] (manage page).

The math your CFO will ask for

Illustrative, using only published numbers:

• Default limit per user per month: 4,000 credits. Basis: [Verified MC1476200] [Verified Partner Center]
• Price per credit: $0.01. Basis: [Reported CRN]
• Default ceiling per user per month: $40. Basis: [Derived] 4,000 × $0.01
• 100 users, default ceiling per month: 400,000 credits, $4,000. Basis: [Verified Partner Center] example + [Derived] $
• CRN "medium" task (briefing doc, spreadsheet, deck from email and files): up to 700 credits. Basis: [Reported CRN]
• Medium tasks per user before the default cap: about 5. Basis: [Derived] 4,000 / 700

Copilot Business is for tenants with up to 300 seats [Reported CRN]. Confirm the seat price and credit rate on your own quote. Resellers set their own prices. Seat list price is not stated here.

Read the list this way: at the default, light use costs far less than the ceiling. About five medium tasks per user in a month reaches the default cap [Derived from Reported CRN band].

The Proof Gap: policy on purchase, outcome still blank

The meter shows credits burned under a spending policy. It cannot show whether Cowork, Work IQ, or Harness work was worth the credits.

MC1476200 and Partner Center prove the trigger (one new Copilot Business seat on an existing Copilot tenant), the dates (Oct 19 direct / Dec 1 CSP), and the default ceiling (4,000 credits per user per month). They do not prove your team's burn rate, your reseller's credit price, or an accepted outcome for any agentic task.

September partner coverage that said "nothing bills until you create a policy" is outdated for the default-on path. The Oct 1 update creates the policy with the purchase. That is a governance gap if Finance assumed the old CRN line still held.

Blank seats on chargeback (tenant to BU to workload to accepted outcome) mean the invoice has no owner. Fill those blanks before the next seat add.

Where it does not apply yet

The change starts in supported markets. Microsoft says it will not initially roll out in Australia, Belgium, Brazil, France, Germany, India, Italy, Korea, the Netherlands, Poland, or Spain [Verified MC1476200] [Verified Partner Center]. If your tenant bills in one of those countries, ask Microsoft or your reseller for the date in writing.

Order Form and admin lines to name before October 19

Paste these into the Order Form schedule, Cost Management runbook, or seat-add approval. Fill the blanks. [RAR analysis]

1. Who can buy a seat. One new Copilot Business seat flips the meter on across every Microsoft 365 Copilot subscription in the tenant [Verified MC1476200]. Name the one person who approves new seat purchases between now and December 1.
2. Your spending policy, created first. Microsoft keeps an existing policy in place [Verified MC1476200]. Create yours with your limit before the next seat purchase so Microsoft's 4,000-credit default does not become the policy.
3. Per-user limit. Pick a number at or below 4,000 credits if your use case does not need Cowork or Work IQ volume. Write it down.
4. Auto-apply new services. Decide on or off. On means future agents bill without review [Verified Learn].
5. What happens at the cap. A limited budget cuts access for the rest of the month [Verified Learn]. Name who gets the alert and who can raise the limit mid-month.
6. Billing method. Pay-as-you-go, P3 pre-purchase, or capacity packs. Prepaid draws first [Verified Learn].
7. Chargeback owner. Usage reports break out by policy, user, group, agent, and service [Verified Learn]. Assign sales, CS, and enablement their share. Map tenant to BU to workload to accepted outcome.
8. Reseller date. If you buy through CSP, confirm December 1 and your reseller's credit price on the quote [Verified Partner Center].

Eight-Seat Read: one decision each

Director to C-suite revenue leaders.

• CRO / VP Sales: Do not approve a casual Copilot Business seat add after Oct 19 (direct) or Dec 1 (CSP) without a named spending policy owner.
• VP RevOps: Own the seat-add approval path and the Cost Management policy before the next license lands.
• Finance / Procurement: Put 4,000 credits / ~$40 per-user ceiling and the credit rate on the quote. Confirm CSP Dec 1 if you buy through a reseller.
• IT / M365 admin: Create or confirm the spending policy, Auto-apply setting, and Azure billing linkage before purchase.
• Sales Ops / CS Ops: Name chargeback for Cowork and Work IQ burn by team.
• Enablement: Train teams that a limited budget cuts access mid-month; do not treat the default as unlimited headroom.
• Security / compliance (if in scope): Confirm which metered services (Cowork, Work IQ API, Managed Runtime, Harness) are allowed before Auto-apply expands the list.
• CEO / strategy: Ask one question on every Copilot Business seat add after the date: did we set our limit, or did Microsoft's 4,000-credit default just become our policy?

Why we might be wrong

1. Your tenant may already have a spending policy. MC1476200 says that policy stays. The one-seat trigger still matters for Auto-apply and for tenants with no policy yet.
2. Your CSP reseller may quote a credit rate or packaging that differs from the $0.01 list CRN reports. Your paper wins.
3. Supported-market exclusions may clear before your next seat add. Get the country date in writing if you bill in an excluded market.
4. Actual burn may stay far under 4,000 credits if your teams do not use Cowork, Work IQ, or Harness. Treat the 4,000-credit figure as a spending ceiling only.
5. CRN's medium-task band (up to 700 credits) is a vendor illustration. Measure your own burn before you budget from the "about five tasks" line.
6. Partner Center sandbox readiness (Nov 2) and partner packs may change how resellers stage the Dec 1 flip. Confirm with your CSP in addition to the announcement page.
7. Primary MC1476200 text sits behind the admin center. This piece cites the Modern Workspace Pro republication. If Microsoft revises the notice again, re-check the Message Center copy.

Sources

1. Microsoft Message Center MC1476200, updated October 1, 2026, as republished by Modern Workspace Pro. https://mwpro.co.uk/blog/2026/10/01/mc1476200-microsoft-365-copilot-business-adds-default-usage-based-billing-for-easier-ai-access/. The primary text sits in the Microsoft 365 admin center.
2. Microsoft Learn, Partner Center announcements, October 2026. https://learn.microsoft.com/en-us/partner-center/announcements/2026-october.
3. Microsoft Learn, usage-based billing overview for Copilot Credits. https://learn.microsoft.com/en-us/microsoft-365/copilot/usage-based-billing-overview-copilot-credits.
4. Microsoft Learn, manage Copilot Credits. https://learn.microsoft.com/en-us/microsoft-365/copilot/usage-based-billing-manage-copilot-credits.
5. CRN, Microsoft enables consumption billing by default for Copilot Business, 5 things to know. https://www.crn.com/news/ai/2026/microsoft-enables-consumption-billing-by-default-for-copilot-business-5-things-to-know. Source for the $0.01 per credit list rate and the 300-seat figure.
6. MSSP Alert, Microsoft shifts Copilot Business licenses to usage-based billing. https://www.msspalert.com/news/microsoft-shifts-copilot-business-licenses-to-usage-based-billing. Still repeats the older November 2 date.

Related reading: Which Order Form line is USL vs Copilot Credits covers the general Copilot Credits fork. GitHub Copilot Default to Balanced covers the code-review dual meter. Who Audits the Meter on Our AI Agents? covers chargeback. OpenAI usage tiers and the spend limit covers the same cap question on the API.

If you want the next Order Form decoder before your next AI renewal, subscribe.