Microsoft 365 Copilot Credits: What UK SMEs Will Actually Pay From December

On 1 December 2026, a new Microsoft 365 Copilot Business licence will arrive in a UK tenant with a spending authorisation already attached to it. Four thousand Copilot Credits per user per month, chosen by Microsoft rather than by anyone inside the business. Nothing is charged until credits are consumed. The permission to spend them exists from the first day.

Two features of that arrangement make it worth an hour of an IT manager's time this month. The first is the arithmetic, which I will come to. The second is the timetable: this change was originally scheduled for 2 November 2026 and moved to 1 December, which tells you the shape is settled while the detail is still moving. A figure quoted from a September blog post deserves checking against the Microsoft documentation before it reaches a budget.

What actually changes on 1 December

Usage-based billing becomes the default for new Microsoft 365 Copilot Business licences bought through the Cloud Solution Provider channel. Standalone offers and bundles both fall inside it: Copilot Business on its own, Business Premium with Copilot, Business Standard with Copilot, Business Basic plus Copilot Business. Microsoft's announcement sets the default spending limit at 4,000 Copilot Credits per user per month and confirms administrators can adjust it, including down to zero to switch usage-based billing off entirely.

Existing subscriptions are not converted. A tenant that bought Copilot Business in June keeps its current billing configuration until it buys more seats or upgrades something, and then the new default applies to those seats. That detail catches people out. A business adding five seats in January inherits the December rules for those five positions, and the person who approves a seat request is rarely the person who reads a credit report.

The second change shares the date and is often confused with the first. The qualifying base subscription requirement disappears, so new Microsoft 365 Copilot and Copilot Business offers can be purchased without a Microsoft 365 base plan, and the existing add-on offers reach end of sale in CSP on 1 December. Microsoft states plainly that neither change adds or removes a Copilot feature. This is a packaging change. It moves a spending decision away from whoever signs the licence order and towards whoever runs the tenant.

What 4,000 credits is worth in pounds

Copilot Credits cost about $0.01 each on the pay-as-you-go meter. For UK budgeting the more useful comparator is the capacity pack sold in the admin centre at £153.80 per 25,000 credits per month, excluding VAT, which is roughly £0.0062 per credit. Both rates matter because a client will ask why two numbers exist, and the honest answer is that they are different purchase routes for the same unit.

Read the first and last rows together. The default spending ceiling is larger than the monthly price of the licence it hangs from. A 15-seat Copilot Business estate carries a default ceiling of 60,000 credits a month, about £369 at pack rates, against seat cost of £241.50. An overhead of roughly 150% sits on top of the subscription, authorised by a vendor default rather than a budget line.

Consumption is what keeps most tenants out of trouble. In the pilots we run, a typical user working through chat, drafting and summarising burns no credits at all, because those experiences remain inside the seat. Only the heavier delegated work draws on the meter. So the ceiling is rarely reached. The exposure sits with the two or three users who do reach it, and with the ways a licence can be consumed without anyone consciously deciding to consume it.

Why the promotional price matters to your budget

That £13.80 figure expires on 31 December 2026. A twelve-month Copilot budget built on the promotional rate understates the second year by £27.60 per seat, and in a 15-seat estate that is £414 a year of unbudgeted subscription. Use the list price for planning and treat the discount as a first-year credit.

Which Copilot work now draws on credits

Everyday Copilot is still included. Chat, a draft in Word, a meeting summary in Teams, a formula in Excel: that is what the seat buys. The metered experiences are the ones where Copilot or an agent runs for minutes rather than seconds, or works across a collection of documents rather than one file.

Cowork is where a UK SME meets this first. Microsoft's guidance estimates a light Cowork task at 100 to 300 credits, a medium task at 300 to 700 and a heavy one above 700. At the default cap that is somewhere between six and forty tasks a month for one person. Enough for a finance director assembling a board pack. Not enough for someone who delegates their inbox every morning and checks the output at lunchtime.

Teams Phone Agent is the other line worth watching, because it meters by the call. A simple enquiry handled in under a minute is estimated at 5 to 15 credits, a call with a transfer or a booking at 15 to 40, and anything longer above 40. A reception agent taking sixty straightforward calls a week would consume somewhere near 3,000 credits a month on its own. That is one number to test before a voice agent goes live.

Microsoft publishes per-task estimates in its Copilot Credits guide, and Cowork exposes a /cost command that shows approximate credit use for the task on screen. Teaching that command to three people is cheaper than teaching it to everyone, and it belongs in week one of a rollout rather than month three.

Three ways to fund the meter

Pay-as-you-go bills in arrears against an Azure subscription with no upfront commitment, which suits a tenant testing one agent or a handful of Cowork users. Capacity packs are the administrative middle ground at £153.80 per 25,000 credits a month. The pre-purchase plan is an annual commitment bought in tiers, with discounts running from 5% at 300,000 credits to 20% at 300 million, and unused credits expiring at the end of the term.

A tenant consuming 4,000 credits a month is better off on the meter than holding a pack, because the pack is a subscription and the credits do not wait indefinitely. Anyone above 25,000 credits a month should be doing the pack arithmetic, and anyone above 300,000 should be pricing the annual plan before renewing. The pre-purchase plan also decrements against an Azure consumption commitment, which is worth knowing if the business already has one.

The two settings that decide your exposure

The first is the per-user monthly limit. Microsoft makes it optional and recommends setting it anyway, and the reasoning becomes obvious once you have watched a single task run. Without a per-user cap, one enthusiastic user can consume a group policy's entire allowance before lunch. A task already running when the per-user limit is crossed is allowed to finish, so the cap stops the next task rather than cutting a report in half.

The second setting is quieter and I would change it on every tenant. Auto-apply new services is on by default, which means any future metered experience Microsoft ships is added to existing spending policies without review. The convenience is real. The side effect is that a policy written in November 2026 governs a product set nobody has seen, and the first signal is an invoice. Turn it off on the main policy and add services deliberately.

My position on ownership is blunt. The Copilot spending policy should not sit with whoever administers licences. It is a budget, and it belongs to the person who signs off the management accounts. Technical administration is fine, but the limit, the alert thresholds and the request routing need a name from finance against them, because those three settings decide what the company has agreed to spend.

One structural point that most tenants miss. Credits are pooled at tenant level rather than assigned per person, so a spending policy defines access and limits but reserves nothing. A department cannot be handed its own pot of capacity, and a user who reaches a limit stays on their policy rather than moving to another one. If finance wants departmental reporting, it has to read consumption by group and allocate the charge internally, because the platform will not do that allocation for them.

A checklist to run before the December cycle

• List every Copilot Business subscription with its purchase date and channel. New purchases from 1 December carry the default; existing ones do not until seats are added or upgraded.
• Open Copilot, then Cost Management, in the Microsoft 365 admin centre and confirm whether usage-based billing is active at all. Tenants on the larger Microsoft 365 Copilot licence are not switched automatically and still need a deliberate decision.
• Set the default policy's monthly limit at a number you can defend to a board, not at whatever the tenant inherited.
• Set a per-user limit below the policy limit. Microsoft's documentation suggests at least 2,000 credits per user per month as a sensible floor for a custom policy.
• Add alert recipients, including someone in finance, and set a user-level threshold so people are warned before they lose access at month end.
• Turn off auto-apply new services, then review additions monthly.
• Assign a read-only role such as AI Reader or Global Reader to whoever reviews consumption. They can see the dashboard without the ability to change a policy.
• Decide between the meter, packs and the annual plan, and test the pack arithmetic against expected use before buying credits.

What this looks like in a 45-person business

A professional services firm we worked with this autumn runs 45 staff on Business Premium and had planned to add Copilot Business for 15 people: the leadership team, two bid writers, a finance manager and an operations lead. Seat cost came to £241.50 a month on the annual price, which was easy to approve. The default credit ceiling would have authorised up to £369 a month on top, and nobody in the business had discussed that figure.

We kept the ceiling and changed its shape. Eleven users went to 2,000 credits a month, the four heavy roles stayed at 4,000, and total authorised exposure fell from 60,000 credits to 38,000, about £234 a month. That is roughly a third off the pre-approved spend while keeping headroom where the work actually exists. The conversation took forty minutes, most of it spent working out which roles would genuinely use Cowork rather than chat.

That pattern repeats across the tenants we see. Three or four roles generate almost all metered consumption: bid and tender work, financial analysis, recruitment screening, and anything involving a document set large enough that nobody wants to read it manually. Everyone else uses the seat and nothing more. Budget by role instead of by headcount and the numbers stop being frightening.

What I would not do is switch usage-based billing off across the estate to make the problem disappear. Turning the limit to zero removes access to the delegated work that justifies the licence in the first place, and a business that buys Copilot for chat alone is paying £16.10 a month for something Copilot Chat already does. Better to cap it, watch two months of real consumption, and set the number from evidence.

Review the controls while the decision is still yours

The practical deadline is not 1 December. It is whenever your next seat purchase lands, and for most UK SMEs that is a renewal inside the next ninety days. Review the Copilot cost controls now, while the limit is still a choice, rather than after an invoice arrives that nobody approved. If your tenant holds Copilot Business seats, or is about to buy them, we can review the spending policies and the roles that will actually consume credits as part of our Copilot readiness work.