Microsoft is changing the way usage-based services are enabled for new Microsoft 365 Copilot Business purchases through CSP.
From 2 November 2026, new Microsoft 365 Copilot Business purchases through CSP will have pay-as-you-go (PAYG) billing enabled by default, alongside the Azure subscription setup required to support consumption-based Copilot experiences.
For IT leaders considering Copilot, this is an important change to understand.
It makes it easier for organisations to access a growing range of AI capabilities, but it also makes cost visibility, governance and control increasingly important as Copilot adoption expands.
What is changing?
The change applies to new purchases of Microsoft 365 Copilot Business through CSP, including standalone licences and bundles.
Rather than requiring additional billing configuration before organisations can access usage-based Copilot services, PAYG will become the default configuration.
This supports consumption-based experiences including:
Copilot Credits used through PAYG are charged based on consumption. Where usage becomes more predictable, organisations can also consider Microsoft's Copilot Credit Pre-Purchase Plan (P3), with additional usage falling back to PAYG.
The important distinction is that this doesn't simply change the price of a Microsoft 365 Copilot Business licence.
It introduces a model where some AI services can generate additional consumption-based costs depending on how they're used.
What about existing Copilot customers?
Based on the current guidance shared with TIEVA, existing licences remain unchanged for now.
However, there isn't yet clarity on what will happen when those licences reach renewal.
That means organisations approaching a Copilot purchase or renewal should understand their current licensing position and keep an eye on Microsoft's evolving commercial model.
Why does this matter?
The change reflects something much bigger happening with enterprise AI.
Copilot is evolving beyond a relatively straightforward per-user licence.
As organisations start using agents, APIs and other consumption-based AI capabilities, the conversation increasingly becomes:
Who can use AI? What can they access? How much are we consuming? What is it costing? And how do we maintain control?
That's why organisations need to think about governance and cost management before usage starts scaling.
Three things IT leaders should consider
1. Put cost controls and visibility in place
Microsoft provides mechanisms including Azure budgets and cost alerts, while Copilot spend limits can be managed through the Microsoft 365 admin centre.
However, there is an important distinction: budgets and alerts aren't necessarily hard spending caps.
IT and finance teams therefore need visibility of consumption and a clear process for monitoring it.
2. Establish AI governance before adoption accelerates
As more employees experiment with Copilot, agents and AI-enabled workflows, organisations need to understand who has access to what.
That means thinking about areas such as identity, permissions, data access, security, governance and ongoing management alongside the technology itself.
AI adoption without appropriate governance can quickly create unnecessary risk, complexity and cost.
3. Understand your likely consumption model
PAYG can make sense while organisations are experimenting or usage is variable.
But once consumption becomes predictable – particularly for organisations making more substantial use of agents – Microsoft's Copilot Credit Pre-Purchase Plan (P3) may provide another commercial route to consider.
Understanding actual usage will therefore become increasingly important when deciding how Copilot should be funded and managed.
Not ready for a full Copilot deployment?
Organisations don't necessarily need to move straight from experimentation to a large-scale deployment.
Microsoft's Copilot in 30 trial currently provides 25 seats for 30 days and is available even to organisations that already have Copilot licences (speak to your TIEVA account Manager).
Used properly, a trial can help organisations identify practical use cases, introduce Copilot to additional departments, understand adoption and start building the business case for wider deployment.
The key is to treat the trial as more than simply activating licences.
Identify the users and use cases first, support adoption, measure the value being created and decide what a successful wider deployment should look like.
The bigger picture: AI needs managing
The 2 November change is another sign that enterprise AI is moving from experimentation into operational IT.
As capabilities expand, organisations will need to manage AI in much the same way they manage other areas of their technology environment: with visibility, governance, security and financial control.
For IT leaders, the question is increasingly moving beyond:
“Should we deploy Copilot?”
towards:
“How do we make Copilot and AI work for our organisation without losing control of cost, security or governance?”
That's where having the right foundations matters.
Get ready for the next phase of Copilot
Whether you're considering Copilot for the first time, expanding an existing deployment or exploring agents and more advanced AI capabilities, now is a good time to review your approach.
TIEVA can help you understand your Microsoft environment, licensing, Copilot readiness, governance and adoption strategy – and put the controls in place to help you get value from AI while maintaining visibility over cost and risk.
Talk to TIEVA about Copilot readiness, governance and cost management.