Copilot Business Pricing: The $21 Seat, a 4,000-Credit Default, the Real Date

Nothing switched on yesterday. The 2 November date that most partner checklists still carry was moved by Microsoft on 1 October. Copilot Business usage-based billing now turns on by default for new CSP licences from 1 December 2026. The default ceiling is 4,000 Copilot Credits per user per month. For a 50-seat firm, that is up to $2,000 a month on top of a $1,050 seat bill.

The short answer. From 1 December 2026, new Microsoft 365 Copilot Business licences bought through a Cloud Solution Provider come with pay-as-you-go billing on for Cowork, the Work IQ APIs and GitHub Copilot Harness. The default limit is 4,000 Copilot Credits per user per month. Existing licences are not described as changing. Admins can lower the limit.

What changes for new Copilot Business licences on 1 December

Microsoft 365 Copilot Business is the Copilot add-on for smaller organisations, priced below the $30 enterprise seat. Until now, the metered features attached to it behaved like the enterprise version. Microsoft's setup documentation says an admin selects Get Started and activates a default spending policy before users reach usage-billed experiences. No policy meant no metered bill.

The October Partner Center item reverses that for one channel. Under the heading Usage-based billing is default on for new Microsoft 365 Copilot Business licenses starting December 1, 2026, Microsoft says new CSP purchases will have usage-based billing enabled by default. The billing method is pay-as-you-go, and it applies to standalone offers and bundles.

Three experiences are named as eligible: Copilot Cowork, the Work IQ APIs and GitHub Copilot Harness. Cowork is the long-running agent that takes a task and works through it across your files. The Work IQ APIs let third-party apps and agents query your Microsoft 365 work data. Both consume Copilot Credits, Microsoft's common billing unit for agentic work.

Who is affected and who is not

The item covers new purchases. Every partner write-up we read says existing Copilot Business licences are not converted, and the Microsoft text we could read describes no change to them. If you renewed or bought before 1 December, your tenant keeps whatever billing setup you already chose.

The rollout also has a geographic carve-out. Microsoft says it will initially not be available in Australia, Belgium, Brazil, France, Germany, India, Italy, Korea, the Netherlands, Poland and Spain. If your tenant bills in one of those countries, the default does not reach you yet, and you should expect it later.

Two other 1 December changes land at the same moment. New Copilot Business offers no longer require a qualifying Microsoft 365 base subscription, and Microsoft says new licences include the Azure subscription setup needed for usage-based billing.

The Copilot Business date conflict: 2 November or 1 December

Search for this change today and you will find two dates. The 2 November date comes from Microsoft's own first communication. The 1 December date comes from Microsoft's correction. Both are real, and only one is current.

Microsoft's October item is dated 1 October 2026 and carries an update note dated 14 October. It states that the effective date was updated, that it was previously communicated as 2 November 2026, and that the default now begins on 1 December 2026 for new CSP subscriptions.

The confusion has a simple cause. Partners wrote their checklists in mid-September from the first notice, and several ranked well before the correction. Geltec updated its post on 3 October. Schneider IT Management and Universal Cloud updated theirs on 16 October. Stoneridge Software has carried 1 December since 21 September, but quotes a $10 cap that no Microsoft text we read supports.

The direct-purchase date we could not confirm

One partner, EPC Group, says direct purchases switched on 19 October 2026 and cites a Microsoft 365 message center post. We could not open that post. It would explain why Microsoft's pricing card now carries usage-billing language, but a single partner citing an unreadable notice is not enough to state it as fact.

My read is that the date is settled for CSP and unsettled for everything else. Plan on 1 December if you buy through a partner. If you buy direct, ask your account team in writing whether the default already applies to you.

What the $21 Copilot Business seat covers and what meters

The Copilot Business seat price does not change. Microsoft's pricing page lists $21 per user per month paid yearly, a promotional $18, and $25.20 on monthly billing. What changes is what else can be billed alongside it, and whether that billing starts without a decision from you.

Microsoft's own FAQ on that page draws the line in one sentence. Everyday AI experiences, like chat and Copilot in your Microsoft 365 apps, are included with your license. More advanced AI experiences are billed on usage, and today those include Copilot Cowork, Code, Autopilot and the Work IQ APIs.

The seat covers Copilot in Word, Excel, PowerPoint, Outlook and Teams, plus chat grounded in your work data. It includes a choice of large language model, the pre-built Researcher and Analyst agents, adoption analytics and Enterprise Data Protection. For most staff at a 50-person firm, this is the whole product they will use.

Cowork, Autopilot and Code sit on usage-based billing in every Copilot Business SKU column on Microsoft's comparison table. So do advanced AI experiences in SharePoint and the Work IQ APIs. Of these, the 1 December default switches on Cowork, Work IQ APIs and GitHub Copilot Harness. The others still need you to opt in.

Seat contents from Microsoft's Copilot Business pricing page. Default scope from Microsoft's October 2026 Partner Center item. Our earlier map of which Copilot features meter on the enterprise seat covers the $30 plan.

The 4,000 Copilot Credits default limit, in dollars

Microsoft states the default limit in credits, not dollars. Its own example makes the scale clear: a customer with 100 Copilot Business users could consume up to 400,000 Copilot Credits a month under the default, with charges based on actual usage. To turn that into money you need a price per credit.

Microsoft publishes one firm unit price. Copilot Studio capacity packs cost $200 a month for 25,000 credits, or $0.008 each if you use them all. A pre-purchase plan saves up to 20% against pay-as-you-go. The pay-as-you-go rate itself is the softer figure.

Microsoft's pay-as-you-go meters page, updated 30 October, still lists the Copilot Studio meter at $0.01 per message, the older name for the unit. Partners converting the default into dollars all use $0.01 per credit. I use $0.01 as a planning rate and flag it as one, because I could not find a Microsoft page stating it as a Copilot Credit price.

Why 4,000 credits is a high default

At $0.01, 4,000 credits is $40 per user per month. The Copilot Business seat is $21. So the default meter ceiling is 1.9 times the seat, and 2.2 times the $18 promotional seat. Microsoft has set a default that lets every user spend nearly double their licence on agents before anything stops them.

Microsoft's own admin guidance points lower. The cost management page tells admins to set at least 2,000 credits per user per month as a monthly budget limit. That is a recommended floor for users who actually need agents, not a ceiling. The default is twice it, applied to every new user whether they need agents or not.

I think a default this generous is a reasonable product choice and a poor budgeting choice. It avoids the worst first impression, an agent that stops mid-task. It also means the owner of a small firm can find a metered charge larger than their seat bill without ever having opened a settings page.

What a 50-seat Copilot Business tenant could pay

A worked example makes the default concrete. Take a firm buying 50 new Copilot Business seats through a partner in December, at the $21 annual price. The seat bill is $1,050 a month. Everything below that line is new.

The ceiling is straightforward arithmetic. Fifty users at 4,000 credits each is 200,000 credits. At $0.01 that is $2,000 a month, or $24,000 a year. On a fully used pack rate of $0.008 it would be $1,600. Either way, the metered ceiling is larger than the seat bill it sits beside.

Usage levels are illustrative assumptions, not measured consumption. Microsoft publishes no per-task credit rate for Cowork or the Work IQ APIs. Totals use the $21 annual seat; on monthly billing at $25.20 the seat line is $1,260.

The bottom row is a ceiling, and few firms will reach it. The point of the table is the spread. The same 50 seats can cost $1,050 or $3,050 a month, and the default puts you nearer the top of that range than the bottom.

The break-even cap: 2,100 credits per user

One number is worth carrying into the admin center. Divide the seat bill by the user count and the credit price: $1,050 divided by 50 users divided by $0.01 is 2,100 credits. At any per-user cap above 2,100, your 50-seat metered ceiling exceeds your entire Copilot Business seat bill.

That threshold scales with seat price, not seat count. At the $18 promotional rate it falls to 1,800 credits. At the $25.20 monthly rate it rises to 2,520. In every case, Microsoft's 4,000 default is well above it.

Copilot Business spending limits admins can set

The default is adjustable, and the controls are the same ones enterprise tenants use. They live under Copilot, then Cost Management, in the Microsoft 365 admin center. Microsoft's setup guide for Copilot Credits describes two choices for a policy: do not limit monthly spending, or limit monthly spending to a set number of credits.

Three settings to check on day one

First, the policy limit. When you activate the default spending policy, Microsoft says you set the tenant-level limit for all users. Each additional policy has its own independent limit and does not inherit the tenant one. A small firm usually needs one policy for everyone and a second, larger one for the few people running agents.

Second, the per-user limit. Microsoft calls it optional, then tells admins to set it anyway to prevent runaway spending by one individual user. That instruction is the most useful sentence in the documentation. Set it below 2,100 credits unless you have a reason not to.

Third, Auto-apply new services. It is on by default, so any future metered service Microsoft adds joins your existing policy automatically. Microsoft says it will add more agents and services over time. Turn it off if you want each new meter to be a decision rather than a surprise.

What happens at the limit

Microsoft's page on managing usage-billed experiences says users who hit the limit lose access to agents and services for the rest of the month. Credits reset on the first. They can request more, but they do not fall back to other policies. Alert emails start at a threshold you set and repeat daily.

The limit behaves like a hard stop for access, which suits a small firm. It does not protect you from a cap set too high. That is why the number matters more than the mechanism, and why the way HubSpot handles AI spend caps is a useful comparison if you run both stacks.

None of the Microsoft pages we read describes a single switch that turns Copilot Business usage billing off. The documented route is to edit the spending policy and lower its limit. We have not confirmed whether a limit of zero is accepted. If you want no metered spend at all, ask your CSP partner to confirm the setting on your tenant before 1 December.

Where this argument is weakest

This post treats the default as a budgeting risk. There is a fair case that it is mostly harmless, and you should weigh it before you act.

Most firms will spend little

Metered credits are only consumed when someone uses Cowork, the Work IQ APIs or Harness. In a 50-person firm, most staff will use Copilot in Outlook and Word and never open an agent. The $2,000 ceiling assumes every user maxes out every month, which is about as likely as every employee using every app in the suite.

The default also solves a real problem. A small firm without an IT team might never activate a spending policy, and Cowork would sit unused behind a gate nobody opened. A default with a cap is a reasonable answer to that, and a cap that ends access at the limit is safer than an uncapped meter.

The evidence base has gaps

Our fetch of Microsoft's October Partner Center page truncated before the full text of the Copilot Business item. Some details here come from the readable part of that page and from four partner posts that reproduce it. The $0.01 rate rests on a page that still uses the word message. Microsoft's Learn cost management pages, updated 30 October, do not yet mention the Business default at all.

The direct-purchase date of 19 October rests on one partner. We also could not verify when Microsoft added usage-billing wording to its Copilot Business pricing card, because archived copies of the page could not be retrieved. Treat any claim of an exact edit date as unconfirmed, including the one that prompted this post.

Frequently asked questions

Where to start before 1 December

If you are buying new Copilot Business seats through a partner, write your per-user cap into the order. A cap of 1,000 credits holds a 50-seat tenant's metered ceiling to $500 a month, and you can raise it for named users later. Ask the partner to confirm in writing that the cap is applied on day one, not after the first invoice.

If you already hold Copilot Business, open Cost Management this week anyway and switch off Auto-apply new services. The 1 December default does not touch your licences, but the next metered service Microsoft adds will join your policy unless you say otherwise. For renewal planning, our breakdown of Microsoft 365 renewal tier math and the analysis of concessions buyers can win on usage-based pricing are the next two reads.

Related reading