Microsoft is changing Copilot billing. Here’s how to stay in control of AI costs 

From 1 December 2026, new Microsoft 365 Copilot Business purchases through CSP will come with usage-based billing already configured. 

At first glance, that might sound like another variable cost for IT and finance teams to manage. But it also gives businesses a practical way to access the next generation of Copilot experiences while retaining control over who can use them, how much they can spend and where that money goes. 

This matters because Copilot is changing. 

New experiences such as Copilot Cowork are designed to carry out larger, multi-step pieces of work. That creates more value, but also a different cost model. Businesses therefore need to understand what they are paying for, what controls are available and how to connect AI consumption with measurable results. 

Traditional Copilot experiences are useful when you need to ask a question, summarise information or create something. 

First, what is Copilot Cowork? 

Cowork is designed for work involving multiple steps, applications or outputs. You define the outcome and Cowork plans the work, uses relevant business context and produces something for you to review. 

Copilot helps you with the work. Cowork lets you delegate more of the work. 

As a rule of thumb, use regular Copilot when a task can be completed in a single sitting. Consider Cowork when the work spans several applications, outputs or hours. 

Cowork can bring together information from emails, meetings, files and business data. It can plan the steps, carry out the work and pause for approval at important points. 

The value is not in generating another paragraph more quickly. It is in looking at time-consuming processes and asking: 

Does a person need to complete every step of this? 

• preparing information before a customer meeting 

• coordinating a project 

• researching a topic 

• working through an overloaded inbox 

• bringing information together from several sources 

• producing a report or briefing for review 

Why usage-based billing can be positive 

Cowork is designed for larger pieces of work, so its usage is measured differently. 

Microsoft uses Copilot Credits to measure eligible usage-based AI activity. Different experiences and tasks can consume different numbers of credits, so the cost depends on the work completed, not simply the number of people with licences or the number of prompts entered. 

That creates three important considerations: 

1. Credits measure consumption, not user numbers. Spend follows the eligible AI work that is completed. 

2. Tasks can consume credits differently. A straightforward action and a more involved multi-step task may not cost the same. 

3. Billing and control work together. Organisations can combine supported payment options with access policies, spending limits and usage reporting. 

Microsoft publishes the applicable services, consumption measures and prerequisites in its Copilot Credits Guide. This should remain the reference point because services and rates can change. 

Administrators can review consumption in the Microsoft 365 admin centre under Copilot > Cost management. From there, they can manage access, apply spending controls, review credit requests and monitor supported services. 

The Microsoft overview of Copilot Credits and usage-based billing explains how these controls fit together. 

A simple way to plan Cowork costs 

Microsoft’s published pay-as-you-go planning rate is $0.01 per Copilot Credit. 

The following examples turn that rate into an indicative monthly budget. They are planning scenarios, not fixed prices for specific tasks. Actual Cowork consumption depends on the work completed, including the steps, tools, models and data involved. 

Illustrative monthly Cowork costs at $0.01 per credit 

Usage profile	Credits per user	Cost per user	10 users	50 users
Light exploration	500	$5	$50	$250
Regular targeted use	1,500	$15	$150	$750
Frequent multi-step work	3,000	$30	$300	$1,500
Default monthly ceiling	4,000	$40	$400	$2,000

These figures use Microsoft’s illustrative US dollar pay-as-you-go rate before taxes, partner pricing, currency conversion or any applicable pre-purchase discount. Actual invoices will follow the relevant commercial agreement and metered consumption. 

For a quick estimate, use: 

Number of users × expected credits per user × $0.01 

A 25-user pilot budgeted at 1,500 credits per user would therefore have an indicative monthly ceiling of $375. 

The better forecast comes after the pilot. Users can type /cost in Cowork to see an approximate task total and remaining allowance. Those patterns can then be compared with the authoritative reporting in Cost management before limits are changed. 

The in-product figure is useful for learning. It is not the billing ledger. 

What changes on 1 December 2026? 

From 1 December 2026, a new eligible Copilot Business purchase through CSP can automatically create the Azure billing foundations and a default spending policy. 

The change also covers: 

• additional seats added to an eligible subscription 

• upgrades to an eligible SKU 

• eligible subscriptions created through a partner transfer 

The scoped offers include: 

• Microsoft 365 Copilot Business 

• Microsoft 365 Business Premium with Copilot 

• Microsoft 365 Business Standard with Copilot 

• Microsoft 365 Business Basic plus Microsoft 365 Copilot Business 

Microsoft’s starting policy allows up to 4,000 Copilot Credits per licensed user each month. 

This is a spending ceiling, not a bundle of free credits. Eligible usage is billed as it occurs. Partners and administrators can lower the limit, increase it where appropriate or set it to zero when usage-based experiences should not be available. 

Charges flow through the CSP invoice, making clear onboarding, reporting and customer billing processes essential. 

Existing user-group and tenant cost-management policies remain in place. The change is intended to simplify activation, not remove the governance already established. 

When users approach their limit, they can see their available allowance and request more. An administrator can review that request against the organisation’s cost and compliance policies before approving it. 

That approval point allows people to experiment without turning experimentation into unmanaged spending. 

Where Cowork is likely to earn its keep 

Cowork is most useful when a task crosses applications, sources and outputs. 

The economic comparison is not simply the cost of a prompt. It is the cost of a governed AI run compared with the time, delay and rework in the existing process. 

Examples of outcome-led Cowork scenarios 

Business area	Example workflow	Value to measure
Leadership	Build a daily command centre or board pre-read from meetings, emails, files and results	Preparation time, decisions ready for review and actions completed
Sales	Prepare for a customer meeting, then draft the follow-up actions and account-team update	Seller preparation time, follow-up completion and sales-cycle movement
Marketing	Create a launch kit across blog, social, web and seller materials, with review points	Asset turnaround, approval time and consistency
Customer service	Assemble case context, investigate likely causes and prepare a cited response	Handling time, resolution speed and escalation reduction
Finance and operations	Produce a weekly business review, reconciliation pack or audit evidence package	Reporting time, exceptions resolved and review cycles reduced

Use Copilot Chat or an in-app Copilot for focused assistance. Use Cowork when you need a multi-step process carried through to review. 

Start with a measurable workflow. Do not enable consumption first and look for a purpose afterwards. 

Imagine that Cowork completes a task that would normally require someone to work across several applications, find information, analyse it and create the final output. 

The useful question is not simply: 

How many Copilot Credits did that use? 

It is: 

What did we get back for that consumption? 

That is the basis of good AI cost management: connecting the cost of AI with the value of the work being delegated. 

How do you stop costs getting away from you? 

Variable consumption creates an understandable concern for IT and finance teams. 

Microsoft Cost management allows administrators to control access, create spending policies, apply limits, configure alerts and review consumption across supported services and funding sources. 

This means businesses can start with a controlled group, observe how Cowork is being used and adjust their policies based on evidence. 

It is more than billing administration. It creates a way to govern and improve AI use over time. 

The Microsoft guidance on Cowork administration and governance also states that a Cowork spending policy acts as an access control, not simply a budget. A user outside the relevant policy does not gain access just because Cowork is available elsewhere in the organisation. 

That gives businesses a better starting point than enabling AI everywhere and hoping for the best. 

Start small, learn quickly, then scale what works 

A sensible first step is a controlled 30-day pilot with: 

• named users 

• two or three priority workflows 

• a clear monthly ceiling 

• agreed measures of time, quality and business value 

Record how the process works before the pilot. Then compare it with Cowork’s consumption and results. 

This produces a useful cost-per-workflow view rather than a vague AI bill. 

As adoption matures, businesses can consider three funding approaches: 

Central pilot budget 

The organisation funds the initial pilot while people learn what works. 

Showback 

Departments can see their consumption and costs, but are not charged internally. 

Chargeback 

Business units take responsibility for their own AI consumption and budgets. 

The right model will depend on the organisation’s culture and finance processes. But visibility should come before complexity. 

Cost optimisation is not about using less AI 

Good cost optimisation is not necessarily about spending less. It is about wasting less. 

If AI consumption produces measurable value, reducing it simply to lower the Azure bill could be a false economy. 

Instead, businesses should ask: 

• Which teams are getting the most value? 

• Which tasks are worth delegating? 

• Where is a more expensive AI experience being used for work that could be handled more simply? 

• Which use cases should be expanded? 

• Which should be stopped? 

• Are our limits still right as adoption grows? 

Consumption reporting can help administrators identify cost drivers and compare usage across policies, users, groups and supported services. That evidence can inform future limits, access decisions and budget allocation. 

Govern the spend. Measure the outcome. Then optimise both. 

That is how AI becomes sustainable. 

Making it practical with Espria 

Switching on the technology is only one part of successful AI adoption. 

The Espria approach connects three things: 

• readiness 

• cost control 

• adoption 

We help customers check that licensing, billing and policies are ready, establish suitable limits and alerts, and identify work that is genuinely worth delegating. 

The goal is not to introduce more technology for its own sake. It is to give people access to the right tools, with clear boundaries and a measurable purpose. 

30-minute Copilot cost-control workshops 

Espria will support customers with focused 30-minute workshops covering the new billing model. 

We will explain the change in plain English and help customers consider how access, policies, limits and cost controls should work together. 

The workshop is designed to answer three questions: 

• Who should have access? 

• What are we comfortable spending? 

• How will we monitor it? 

Building the skills to use AI well 

Controls are only half of the picture. People also need to know how to define the work they want AI to complete. 

Through Espria Promptathon sessions, users learn how to turn business challenges into clearer prompts and more useful outcomes. 

That becomes more important with Cowork. When delegating multi-step work, users need to define: 

• the outcome 

• the relevant context 

• the boundaries 

• what a good result looks like 

Clearer instructions support purposeful use, better results and more informed cost decisions. 

The bigger opportunity 

The billing change on 1 December should not create fear around Copilot. It should prompt a more mature conversation about AI. 

Not simply: 

How many Copilot licences should we buy? 

But: 

Which pieces of work should we delegate to AI, what are they worth to us and how do we keep the economics under control? 

Cowork opens the door to more substantial, multi-step AI work. Usage-based billing makes the cost of that work visible. Cost-management policies provide the boundaries. 

Put those together properly and businesses can move from experimenting with AI to managing it as an investment. 

Ready to explore Cowork without losing control of the cost? 

Speak to Espria about a 30-minute Copilot cost-control workshop or a Promptathon session. 

We will help you understand the new billing model, put appropriate access and cost controls in place, and identify the work where Copilot and Cowork can deliver measurable value. 

The goal is not to consume more AI. It is to get more value from what you consume.