The November 2025 EA volume tier collapse applies only to online services purchased through Enterprise Agreement, MPSA, and OSPA. Perpetual software licences (Windows Server, SQL Server, etc.) and the Software Assurance attached to them continue to operate under the prior tier mechanics. Azure consumption was never subject to tier mechanics and is unaffected. For a typical large enterprise EA with a 60/25/15 split (online services / Azure / perpetual+SA), the tier collapse affects roughly 60% of the contract value — not 100%. Procurement teams who model the impact across the wrong portion of the bill produce inflated cost waves and weak negotiation positions.
Why scope matters more than the headline percentage
The headline number from the November 2025 change is 6–12% structural cost increase. That number is correct as a percentage of affected line items. It is not correct as a percentage of total EA value, and the difference matters significantly to renewal economics, internal stakeholder communication, and negotiation positioning.
A 6–12% impact on 60% of the bill is a 3.6–7.2% impact on the total. The latter is the number a CFO wants to see in the impact analysis, and the number that should anchor the procurement team’s internal communication. The former is the number that anchors the negotiation conversation, because the recovery levers all work on the affected portion specifically. Confusing the two produces misaligned expectations on both sides.
What is in scope
The tier collapse applies to online services purchased through Enterprise Agreement, Microsoft Products and Services Agreement (MPSA), and OSPA (China). “Online services” in Microsoft’s commercial taxonomy includes all SaaS offerings and cloud subscription services. Specifically:
- Microsoft 365 family: E1, E3, E5, the Business plans (Basic, Standard, Premium), Frontline (F1, F3), Education (A1, A3, A5), Government (G1, G3, G5), and all add-on SKUs (Teams Phone, Power BI Pro, Project, Visio, etc.) sold as online services.
- Office 365 components where still purchased separately from M365.
- Dynamics 365: all online subscription SKUs across Sales, Customer Service, Field Service, Finance, Operations, Business Central, and the rest.
- Power Platform: Power Apps, Power Automate, Power BI Premium, Power Pages, and Power Virtual Agents (now Copilot Studio).
- GitHub Enterprise on EA/MPSA.
- Microsoft 365 Copilot and related Copilot SKUs sold as online subscriptions.
- Security and compliance add-ons sold as online services: Defender suite components, Purview add-ons, Entra add-ons, Intune.
What is out of scope
Three categories of EA spend are unaffected and continue to operate under prior pricing mechanics.
Azure consumption
Azure has always used a unified pricing model under EA, with discount mechanics tied to consumption volume and commitment (via MACC) rather than seat-count-based tiers. The tier collapse changes nothing about Azure economics. This matters because Azure remains the largest single source of negotiation leverage on a 2026 renewal, and the post-tier-collapse playbook leans heavily on Azure co-commitment as a recovery lever. See the recovery playbook for the operational mechanics.
Perpetual software licences
Windows Server, SQL Server, BizTalk, Visual Studio (perpetual SKUs), and other perpetual licences purchased through EA continue to benefit from volume tier discounts on the licence purchase itself. The original A/B/C/D tier structure still applies to these products. A 5,000-seat enterprise renewing SQL Server licences still receives the volume discount on those specific line items.
Software Assurance
SA pricing on perpetual licences continues to use the prior volume mechanics. This includes SA on Windows Server, SQL Server, Visual Studio, and the rest of the perpetual stack. SA is roughly 25% of perpetual licence cost annually and is itself a meaningful EA line item for organisations with significant on-premises Microsoft footprint.
Office LTSC. Office LTSC is a perpetual product but is purchased through specific commercial vehicles. Its volume discount treatment under the November 2025 change is consistent with perpetual licence handling — that is, the tier mechanics survive for LTSC.
Visual Studio subscriptions. Visual Studio subscriptions are technically online services and are affected by the tier collapse. Visual Studio perpetual licences are not. Most enterprise Visual Studio spend is on the subscription side.
Modelling impact correctly
A correct impact model separates EA spend into the three categories and applies the right discount mechanic to each. The structure looks like this for a typical $10M EA:
| Category | Typical share | Tier collapse impact | Recovery levers |
|---|---|---|---|
| Online services | ~60% ($6M) | 6–12% structural increase | 5 levers from recovery playbook |
| Azure consumption | ~25% ($2.5M) | None directly | MACC negotiation, RI/SP optimisation, BAFO process |
| Perpetual + SA | ~15% ($1.5M) | None — tier mechanics survive | Standard SA renewal negotiation, drop-SA decision per product |
The category split varies significantly by organisation. Heavy Azure consumers have larger Azure share. Organisations that have completed cloud migration may have minimal perpetual licence exposure. Manufacturing and other industries with on-premises requirements may have larger perpetual+SA share. The correct model uses the actual split for the specific organisation, not the typical split.
Strategic implications of the scope distinction
The scope distinction has two practical implications for renewal strategy beyond simply getting the math right.
First, the relative attractiveness of Azure as a negotiation lever has increased. Azure was always a leverage source on EA renewals; post-tier-collapse, it is disproportionately important because it is the largest category of EA spend that retained its prior commercial flexibility. Procurement teams who deprioritised Azure-side preparation in past renewals need to reweight their attention. Azure consumption commitments (MACC), Azure Hybrid Benefit optimisation, and Reserved Instance / Savings Plan strategy each became more valuable as Azure-side leverage now compensates for online-services-side loss.
Second, organisations with significant perpetual licence footprint have a comparative advantage they may not have noticed. The 15% of an EA that sits in perpetual+SA still operates under prior mechanics; that portion of the renewal is essentially unchanged from a 2024 negotiation. Organisations whose EA tilts heavier than typical toward perpetual+SA — common in manufacturing, life sciences, and other on-premises-heavy industries — absorb the tier collapse on a smaller percentage of their total bill than the typical organisation. This should be reflected in internal expectations.
Scope correctness checklist for your model
Before finalising your tier-collapse impact analysis, verify five things:
- Is your EA line-itemised by online service, Azure consumption, and perpetual+SA? If not, the categorisation needs to come from the EA itself before the model can be trusted.
- Is Azure being modelled with a different methodology from online services? It should be — Azure does not get a tier-collapse adjustment.
- Are perpetual licences and SA on those licences being modelled with their pre-November-2025 tier mechanics intact? They should be.
- Is Office LTSC sitting in the correct category? It is perpetual, not online.
- Are Copilot, Dynamics, and Power Platform additions captured in the online services portion at their full value, not their incremental value? Common modelling error: treating new SKU additions as incremental rather than including them in the affected base.