MICROSOFT 365 LICENSING IS CHANGING
- Jonathan Stuckey
- 20 hours ago
- 8 min read
author: Jonathan Stuckey
audience: IT Operations, Procurement, Project managers, Business management.
I mostly comment on the practicalities of Microsoft 365 ECM stack for business use, but July 1st is a sea-change, and a lot of organisations do not understand what is about happen.
Most organisations treat Microsoft 365 as a licensing exercise. Pick the right plan, allocate licences, manage renewals. Repeat annually. It is a clean model, and for a long time it worked reasonably well.
That model no longer applies.
Why It Actually Matters
Over the past 18 to 24 months, Microsoft has systematically changed how the platform is priced and consumed. What looks at first glance, like a series of isolated updates is actually something more deliberate. It is a coordinated shift in commercial philosophy. One that moves cost responsibility from Microsoft's bundled assumptions to your organisation's actual behaviour.
And as of July the 1st this lot comes together and will impact every organisation using M365.
This is not just a pricing update. It is an operating model change.
A Shift: From Licences to Usage-Driven Cost
Historically, Microsoft 365 spend has been relatively predictable in a way that made it easy to ignore. You paid per user, received bundled capabilities, consumed services within defined limits, and stayed within broadly stable boundaries. The complexity existed in the product - not in the bill.
That is changing for three structural reasons:
Artificial intelligence is now embedded across core workloads and priced as a premium layer:
Copilot is not just a feature add-on, it is a separate commercial commitment
This new cost sits on top of existing subscriptions, and
additional consumption-based billing is added for agents and processing.
Data growth is accelerating in SharePoint and OneDrive, and the billing model has finally followed. Storage capacity overages were once absorbed into licence headroom, they are now exposed directly to the customer as variable, pay-as-you-go charges.
Microsoft is consolidating services into broader suites while removing the standalone options that allowed workload-level optimisation. The flexibility that previously let organisations tune spend at a granular level is being de-scoped.
The result of the changes is a hybrid model encompassing a higher baseline licence cost, layered with additional usage-based charges for storage, AI, governance, and backup.
The more you use the platform, and the less actively you govern that use, the more directly your behaviour determines your bill.
If you are not actively governing usage, your costs will drift. Not eventually - Right Now.
What Has Actually Changed
The easiest way to understand the shift is to look at the changes collectively, rather than individually. Viewed in isolation, each update feels incremental. Viewed together, they describe a platform that is being deliberately restructured.
Area | What Changed | What It Means in Practice |
SharePoint and OneDrive | Standalone plans are being retired | These workloads can no longer be optimised independently - they must be aligned to Microsoft 365 suites |
SharePoint storage | Pay-as-you-go billing introduced for overages | Storage becomes a variable operational cost, not fixed capacity Included allocation remains 1 TB plus 10 GB per user. Growth beyond this has direct financial impact |
OneDrive storage | Consumption-based extension model (preview) | Another PAYG plan for overages. User behaviour will directly affect cost exposure |
Purview pricing | Usage-based billing introduced for some services | Compliance capabilities being consolidated. Governance costs scale with data volume and AI use |
| Rationalise options | Business plans have reduced access to Purview services. |
M365 Copilot pricing | Per-user add-on license | AI is a premium capability, not a baseline one |
Copilot agents | Usage-based billing | Azure-linked consumption pricing for resource utilisation. Automation costs scale with usage and complexity |
Microsoft 365 pricing | Global price increases from 1st July | Higher minimum cost of entry across the platform skus: Business plans, Enterprise E3/E5 and Govt plans |
| Commercial terms | Reduced flexibility under New Commerce Experience. Impact: Poor forecasting now creates locked-in overspend |
Frontier (E7) | New high-end bundle for Enterprise plans | Microsoft formalises an AI-first licensing tier. License add-on and monitoring. Excludes agent and resource consumption. |
Microsoft 365 Archive | Pay-as-you-go billing per GB above quote. | Quota based on SharePoint baseline. Archive becomes a cost optimisation tool with planned usage. |
| Rehydration charge removed | Removes “double-dipping” costs for data access. |
Microsoft 365 Backup | Pay-as-you-go pricing based on protected data | Backup introduces a new consumption workload across active, deleted, and versioned content |
Why It Matters More Than You Think
On their own, these changes feel manageable. Each one, reviewed in isolation, looks like a standard commercial adjustment. A price increase here. A new billing model there. The kind of thing you note in the opex section of managerial briefing paper and revisit at the next procurement cycle.
That reading of the situation is wrong, and it is dangerous.
Together, the changes shift responsibility. Microsoft is moving away from absorbing platform variability into licensing and instead exposing it directly to the customer. That means three things are now true simultaneously, and they compound each other:
Storage Is Now a Financial Risk, Not Just a Technical Problem
Consider a typical SharePoint environment with a mixed usage profiles: Large files. Heavy collaboration. Version history enabled. Retention policies in place...
Each version of every file consumes storage. Each retained version cannot be deleted while a policy is active. Once the tenant exceeds its included allocation (the basic 1 TB plus 10 GB per licensed user) all of that becomes billable. The same content also contributes to backup consumption, because deleted items and versioned copies are included in backup billing calculations.
Without governance, a single workload compounds cost across multiple services simultaneously.
What was previously a capacity planning problem is now a financial exposure problem.
The distinction matters, because the people who own the technical problem and the people who own the financial problem are rarely the same people... and they rarely talk to each other with the urgency this requires.
AI Introduces a Second, Less Predictable Cost Layer
Copilot is not just a licence. It is a combination of:
per-user entitlements,
role-specific extensions, and
consumption-based execution (particularly for agents).
A common pattern emerging in organisations is this:
Copilot is licensed broadly across knowledge workers,
internal agents are built for things like: HR enquiries, IT support, Health & Safety assistance, Resources content navigation...
The base licences unlock the capability. The usage drives the cost. AND every agent interaction consumes compute resources, billed through Azure-linked consumption, independent of how many users hold Copilot licences.
This creates a dynamic that is genuinely new to Microsoft 365 commercial management: adoption success increases spend.
i.e. The better your agents work, the more they are used, and the more they cost.
This is not a criticism. It is simply a reality that requires a completely different approach to financial management. One that most organisations have not built yet, because they have never needed it for a general user productivity platform.
Governance Decisions Now Carry Direct Financial Consequences
Retention policies, sensitivity labels, and content classification used to be about just Information compliance (and nobody really cared ...except IM, Security and Privacy advisors).
Ironically they still are about compliance, but now they also determine:
how much data you store,
how much backup you pay for,
as well as what Copilot can and cannot access.
Well here's where the gotchas became real for everyone:
a strict retention policy may reduce regulatory risk, but it increases long-term storage footprint and therefore storage cost.
a restrictive sensitivity label may protect data appropriately, but it can also prevent AI from using it effectively.
...
These are no longer purely technical or compliance decisions. They are commercial ones, and they need to be treated accordingly.
The tension this creates is new territory for most governance teams. You are now simultaneously trying to minimise cost, maintain compliance, and enable AI-driven productivity - and the levers for each pull in different directions depending on who got there first.
The Bigger Picture From Microsoft
If you step back from the individual changes and look at the direction of travel, a consistent strategy appears.
Microsoft is raising the baseline licence cost.
It is removing standalone options that allowed workload-level flexibility.
It is introducing consumption-based billing wherever usage varies significantly between organisations.
It is monetising AI as a premium capability layered on top of everything else.
...the result is a platform that behaves much more like Azure than traditional SaaS. You do not just pay for access. You pay for what you use, how you use it, and how well you govern it.
Microsoft is being explicit about where it sees the market heading, with its Frontier (E7) SKU a bundled AI-first tier, combining:
a base user license Microsoft 365 E5,
a Copilot client uplift, and
advanced AI capabilities
This is not a niche enterprise offering. Microsoft is formalising an expectation that AI-first organisations will pay accordingly, and that the baseline for enterprise licensing will continue to rise as more AI capability is embedded into core workloads.
The organisations that understand this will be in a position to control cost and extract genuine value from the AI investment. The ones that do not will find their licensing model becoming progressively more expensive, with a progressively less clear link between what they pay and what they get.
What Organisations Should Be Doing Now
Organisations responding well to this shift are not focusing on licence optimisation alone. They are treating Microsoft 365 as an operating model. One that requires active management of usage, governance, and commercial design simultaneously.
That means three deliberate shifts in how the platform is managed.
Segment your workforce properly. Understand that not every user needs Copilot, or even an E5 license.
The introduction of role-based and consumption-based pricing makes workforce segmentation essential. The cost difference between assigning Copilot broadly versus assigning it to users who will genuinely benefit is significant, and it compounds over time. Organisations that have not done this work are paying for capability that is not being used.
Put controls around consumption. Storage lifecycle management, version history policies, and archive strategy are now financial levers, not just operational hygiene.
The same is true for how agents are designed and deployed. Every retention decision, every versioning default, every sharing configuration has a cost implication. These decisions need to involve people who understand the financial exposure and operational impact, and not just the technical requirements.
Introduce basic FinOps discipline for the platform. If you are not monitoring storage growth, backup footprint, and AI usage, you are accepting uncontrolled cost. Microsoft provides tooling.
The gap in most organisations is not tooling - it is accountability. Someone needs to own the cost model for the platform, and that person needs to be in a conversation with the people who make architectural and governance decisions.
None of this is especially complex, but it does require treating Microsoft 365 differently from how most organisations currently treat it. Don't think of it as a fixed-cost utility, but as a governed platform where usage patterns matter as much as the licence model.
A Final Thought
Microsoft 365 used to be defined by what you bought. It is now defined by how you use it.
That change is subtle on the surface, but structural underneath. The shift to consumption-based billing, AI-layered licensing, and reduced standalone flexibility is not a set of inconveniences to be managed at the next renewal. It is a fundamental change in how the platform creates and compounds cost, and it is already underway.
The organisations that continue to treat licensing as a static procurement exercise will find spend becoming progressively harder to justify and control. The organisations that treat Microsoft 365 as a governed platform, where usage patterns, data lifecycle, and AI adoption are actively managed, will be in a substantially better position to extract real value without incurring uncontrolled cost.
The question is not whether your organisation needs to adapt to this model. You already have to - from 1st July. The question is whether it is doing so deliberately, or by accident.
About the author: Jonathan Stuckey
Comments