What changed. On 1 November 2025, Microsoft eliminated the A/B/C/D volume discount tiers on online services purchased through Enterprise Agreement, MPSA, and OSPA (China). All EA customers now pay the price formerly known as Level A. Azure is unaffected. Perpetual licences and Software Assurance under EA still get volume discounts.
Who gets hit hardest. Mid-market organisations (500–5,000 seats) who previously sat in Level B or C. The structural increase on affected line items is 6–12% — compounding with the July 2026 SKU price increase and the Unified Support escalation that follows.
What to do. If your renewal is in the next 12 months, model the full impact now, identify the five negotiation levers that still exist, and reset internal pricing expectations before Microsoft anchors the conversation. The lost tier discount is partially recoverable through structured negotiation — but only with preparation that starts before Microsoft makes the first move.
The biggest single change to EA economics in fifteen years
For most of the past two decades, Microsoft Enterprise Agreement pricing was a two-axis decision. Buyers chose their product mix and their commercial terms, and a deterministic volume discount table did the rest. Levels A, B, C, and D corresponded to specific seat-count thresholds, and crossing one of those thresholds delivered an automatic step down in unit pricing. For most mid-sized and large enterprises, the volume tier was the most visible discount mechanic on the EA — sometimes the only one a procurement team understood with confidence.
On 1 November 2025, Microsoft eliminated that mechanic for online services. The change was announced months ahead of the effective date, framed in Microsoft’s communications as a “simplification of pricing structure” that would “create consistency across the channel.” In commercial terms, simplification meant that every EA customer — from a 600-seat services firm to a 60,000-seat global manufacturer — would pay the same per-unit list price for online services. The price that everyone now pays is the price that used to be the worst available: the old Level A.
The effect on actual renewal economics has been substantial and immediate. Mid-market organisations who previously enjoyed Level B or C tier discounts face an overnight cost increase of 6–12% on the affected line items. For a 5,000-seat enterprise paying $10M annually under a typical EA mix, the structural impact through mid-2026 can push total annual cost to $12.5M — a $2.5M increase — without the enterprise activating a single new capability. Compounded with the July 2026 Microsoft 365 SKU price increases and the automatic Unified Support escalation that follows base spend, the full 2025–2026 cost wave routinely exceeds 25% of the prior EA baseline.
The change is not, on its face, malicious. Microsoft has a defensible commercial rationale: the volume tier system was created in an era when EA was the only enterprise channel, and the existence of Microsoft Customer Agreement (MCA), CSP, and other newer channels with flat pricing created an inconsistency the company wanted to resolve. The point is not whether the change was reasonable from Microsoft’s perspective. The point is that for procurement teams entering an EA renewal in 2026 or 2027, the negotiation environment is materially different from anything in the past fifteen years — and a renewal strategy built on the old mechanics will produce a worse outcome than buyers expect.
This article is the structural primer. It explains exactly what changed, who is affected and to what degree, where the remaining commercial levers sit, and what a prepared enterprise procurement team should be doing in the months before their next renewal. It is written for procurement and IT leadership preparing for a renewal in the next 6–18 months — the cohort most exposed to the change and most able to do something about it before signature. If your renewal is further out, the playbook is the same; the urgency is lower.
What actually changed on 1 November 2025
The mechanics matter. Microsoft did not increase any list price on the affected products on 1 November — that is a separate event, scheduled for 1 July 2026. What Microsoft did was eliminate the tiered discount that was previously applied to that list price. The list price itself is unchanged. What changed is the price every buyer pays.
Before the change, an EA online services line item was priced by reference to a four-tier table:
| Tier | Seat threshold (online services) | Typical effective discount vs Level A |
|---|---|---|
| Level A | 250–2,399 | 0% (reference) |
| Level B | 2,400–5,999 | ~6–8% |
| Level C | 6,000–14,999 | ~10–12% |
| Level D | 15,000+ | ~13–15% |
The percentages are typical; specific product lines varied. The structure of the discount, however, was deterministic. A customer renewing with 7,500 active M365 seats received Level C pricing automatically — the buyer did not need to negotiate it. A customer renewing with 18,000 seats received Level D pricing automatically. The tier was a function of seat count, not negotiation outcome.
From 1 November 2025, that table is gone. Every EA customer renewing — or signing a new EA — pays the price that was previously Level A. A 60,000-seat enterprise and a 600-seat enterprise pay the same per-unit list price for the same product. The volume that historically earned 12–15% on the bill earns 0% from the tier mechanic.
Affected: Online services purchased through Enterprise Agreement, Microsoft Products and Services Agreement (MPSA), and OSPA (China). This includes Microsoft 365 (E1/E3/E5, Business plans, Frontline F1/F3), Office 365 components, Dynamics 365, Power Platform, GitHub Enterprise, and other cloud subscription SKUs.
Not affected: Azure consumption (already used unified pricing under EA). Perpetual software licences sold through EA (Windows Server, SQL Server, etc.) and the Software Assurance on those perpetual licences. CSP-purchased products (already flat-priced). EAS — the subscription EA — which uses the same online-services price grid as standard EA and is therefore equally affected.
The scope distinction matters because it shapes the recovery playbook. The largest single line item on most enterprise EAs — Microsoft 365 Enterprise — is fully in scope. So is Dynamics 365 for organisations that have it. Azure consumption, which on a dollar basis is often comparable to M365 spend, is largely out of scope. That changes the centre of gravity of the renewal negotiation: the leverage that previously came from total EA value now needs to come from specific commercial mechanics that survived the change.
Who is hit, and how hard
The financial impact is not uniform. It is sharply dependent on three variables: where the organisation previously sat in the tier table, the share of EA spend that comes from online services versus Azure or perpetual licences, and the seat-count direction of travel (growing organisations are hit harder than shrinking ones because the lost tier benefit applies to a larger base over time). Across our engagement portfolio since November 2025, we see three broad cohorts.
Cohort 1: Mid-market enterprises (500–2,399 seats) — minimal direct impact
Organisations that were already in Level A pricing on online services feel no direct impact from the tier collapse itself. Their list price is unchanged. They do, however, lose the future option to migrate into Level B as they grow — an option that was historically a quiet upside in EA economics. For an organisation growing from 1,800 to 2,800 seats over a three-year EA term, the historical model included roughly $250K–$400K of automatic discount realisation on the incremental seats; that future benefit is now zero.
This cohort also faces an indirect impact: at smaller scale, the EA itself becomes less commercially attractive relative to MCA-Enterprise and CSP, both of which carry flat pricing but offer monthly flexibility that EA does not. The EA-versus-MCA decision framework after tier collapse covers this cross-over in detail.
Cohort 2: Mid-large enterprises (2,400–14,999 seats) — the heaviest direct impact
This is the cohort the change targets and the cohort that feels it most immediately. Organisations renewing out of Level B or C pricing face the full 6–12% structural increase on affected line items. The increase is invisible if procurement compares renewal pricing only to the prior year’s “list” price — that number is unchanged — but visible the moment procurement compares actual paid pricing year over year.
For a 5,000-seat organisation paying $10M annually under a typical EA mix (60% online services, 25% Azure, 15% perpetual/SA), the structural increase on the online services portion is roughly $360K–$720K per year. Over a three-year EA term that is $1.1M–$2.2M before any other change. When the July 2026 SKU price increase lands on top (a separate 5–33% list-price increase on M365 SKUs), the combined effect on the online services portion compounds to 11–45% depending on SKU mix. We cover the July 2026 component separately in the M365 July 2026 price increase guide.
Cohort 3: Large enterprise (15,000+ seats) — the largest absolute dollar impact
Organisations renewing out of Level D pricing face the largest structural percentage hit (13–15% on affected items) and, because they are operating at scale, the largest absolute dollar impact. A 30,000-seat enterprise paying $50M annually under a typical mix can see a $4M–$6M annualised increase on the online services portion alone from the tier collapse. The percentage impact is similar to Cohort 2; the absolute dollars are not. These customers also have the most negotiation leverage to recover the loss, however — large-deal escalation paths, Azure consumption co-commitment, and competitive displacement threats all become more credible at scale.
The deeper strategic picture
The tier collapse is not a standalone event. It is one of three Microsoft commercial moves between mid-2025 and mid-2026 that, taken together, materially restructure the economics of being a Microsoft enterprise customer. Understanding the full picture is the starting point for any defensible renewal strategy.
The first move is the tier collapse itself: 6–12% structural increase on online services for mid-market and above. The second move is the July 2026 M365 SKU price increase: a 5–33% list-price rise on Enterprise, Business, Frontline, and Government SKUs depending on the specific product. The third move is the Unified Support escalation: because Unified Support is contractually priced as a percentage (typically 8–12%) of total Microsoft spend, every increase in EA cost flows automatically into a proportional increase in support cost. There is no negotiation event that triggers the support escalation — it happens by the contract’s own arithmetic.
Stacked together, these three moves produce a cost wave on a typical $10M EA that compounds to $12.5M annually by mid-2026. The first move is fait accompli — the tier table is gone for everyone. The second move can be partially neutralised by renewing before 1 July 2026, which locks in pre-increase pricing for the term of the new EA. The third move can be negotiated by repricing Unified Support or moving to a third-party support provider. The combined renegotiation opportunity is significant — but only if the procurement team understands the full picture before the renewal conversation starts.
The strategic context behind these moves is Microsoft’s ongoing channel restructure. The company has been signalling for several years that EA is no longer the preferred channel for organisations below the very largest tier; the future Microsoft envisions has the largest customers on EA (or its successor), the mid-market on MCA-Enterprise (a Microsoft direct channel), and the rest of the commercial customer base routed through Cloud Solution Providers. The tier collapse moves all three groups closer to that endpoint: mid-market EA customers lose the differentiator that historically kept them on EA, and become more attractive candidates for MCA migration; smaller customers find EA increasingly uncompetitive with CSP; and Microsoft’s direct sales motion is freed to focus on the largest deals.
None of this is hidden. Microsoft has talked openly about the channel evolution in analyst events and partner communications. For procurement, the practical implication is that the renewal decision is no longer just “renew the EA” — it is “renew the EA, move to MCA-Enterprise, restructure into a hybrid with CSP, or something else.” The right answer is organisation-specific. We address the framework for that decision in EA vs MCA after tier collapse: the 2026 decision framework.
Five levers that still recover discount
The tier table is gone. The commercial discount negotiated at renewal — what Microsoft calls the “line-item discount” or “negotiated discount” — is not. It is now where the entire procurement negotiation effort has to go, because there is no longer an automatic tier sitting underneath it. Across the renewals we have advised since November 2025, five levers consistently deliver measurable discount recovery. Each one is worth 1–4% on its own; combined, well-prepared buyers recover 5–9% of the lost tier benefit — reducing the net post-collapse impact from 6–12% down to 1–6%.
Multi-year term commitment with price-lock
Microsoft has always offered modest pricing concessions in exchange for term commitment beyond the standard three years. Post-tier-collapse, those concessions have become more aggressive because the account team has lost a structural discount lever and needs to find others. A four- or five-year commitment with a hard price lock on the affected SKUs is consistently negotiable, particularly for buyers signing before mid-2026 when Microsoft is pushing to lock in revenue ahead of the next pricing change.
The mechanic that matters here is the price-lock clause itself — not the term length. A four-year term without a price-lock clause is worth almost nothing because Microsoft can change list prices mid-term and the new prices apply at the next anniversary order. With a price-lock clause, the term commitment delivers real economic value.
Typical recovery: 2–4%Azure consumption co-commitment
Azure was not affected by the tier collapse, but Azure spend is the single largest source of negotiation leverage for an EA renewal in 2026. Microsoft account teams have aggressive Azure consumption targets, and a commitment to specific Azure spend over the EA term — structured as a Microsoft Azure Consumption Commitment (MACC) or equivalent — is consistently exchangeable for online services discount.
The mechanic works best when the Azure commitment is real — that is, when the buyer is genuinely going to consume the committed amount — because Microsoft account teams have learned to discount inflated commitments. We have seen buyers exchange a $5M three-year Azure commitment for an additional 2–3% discount on M365 line items. Larger Azure commitments deliver proportionally larger M365 discounts. The dollar value of the discount is independent of the dollar value of the commitment — the commitment buys a percentage point that applies to the entire M365 stack.
Typical recovery: 1–3%Copilot attach commitment
Microsoft 365 Copilot is the single most aggressive attach product in Microsoft’s 2026 sales motion. Account teams have explicit attach quotas, and the deal-desk is structurally pre-disposed to trade discount on the core EA stack for Copilot commitment. The negotiation is sensitive because the discount Microsoft offers on Copilot itself is real, but it is bundled implicitly with discount on the rest of the EA — the buyer who does not parse the components will not see the full benefit.
The cleanest version of this lever is a structured Copilot pilot with commercial expansion terms baked into the EA renewal. The buyer commits to a pilot at a specified scope (typically 100–500 users), with pre-agreed pricing for expansion if the pilot delivers measurable productivity outcomes. Microsoft gets the attach commitment for its internal scorecard. The buyer gets favourable pricing on the rest of the EA and avoids the worst-case scenario of an enterprise-scale Copilot commitment without proof of value. See our Copilot licensing advisory service for the pilot structures that protect buyers.
Typical recovery: 1–3%Credible competitive displacement
The presence of a credible alternative changes the negotiation. For Microsoft 365 specifically, the alternative is Google Workspace; for Dynamics 365 it is Salesforce; for Power Platform it is the broader low-code competitive set; for parts of Azure it is AWS or Google Cloud. None of these is a like-for-like replacement, and Microsoft account teams know that — but they also know which line items face the most credible substitution pressure and which discount concessions move those line items.
The lever requires actual competitive engagement, not just a stated threat. A buyer who has a Google Workspace pilot running, a documented executive review of the alternative, and a defensible total-cost-of-ownership comparison gets meaningfully different commercial terms than a buyer who mentions Google in passing. The discount realised is highest on the SKUs where the displacement is most credible — typically M365 for organisations whose Microsoft footprint is concentrated in Office productivity rather than deep Azure or Dynamics dependencies.
Typical recovery: 1–4%Microsoft fiscal year-end timing pressure
Microsoft’s fiscal year runs July to June. The last quarter (April to June) is the period when account teams are most willing to accept commercial terms they would resist in Q1 or Q2. The mechanic is not new — it has existed for as long as Microsoft has had quarterly sales targets — but it has become more important post-tier-collapse because it is now the timing lever that compensates for the lost structural lever.
The buyer whose renewal falls in March, April, May, or June 2026 (or 2027, 2028, etc.) has structural timing leverage that does not exist at other times of the year. The buyer whose renewal is in August or September faces an account team that is in target-setting mode rather than target-closing mode. For renewals that can be timed flexibly, moving the signature date into Microsoft’s Q4 is worth 1–3% on its own. For renewals that cannot be timed flexibly, the procurement team should at least understand whether their renewal date helps or hurts — and calibrate expectations accordingly.
Typical recovery: 1–3%The renewal-window decision tree
What a procurement team should do next depends primarily on one variable: how far away the next EA renewal is. The tier collapse changes the right strategy for each renewal window, not just the magnitude of the impact.
Renewal in 0–6 months
This cohort is in the middle of an active negotiation right now or about to be. The priorities are: confirm the full cost impact of the tier collapse on your specific SKU mix and seat count; document the pre-tier-collapse pricing as your internal baseline (so you can see the structural increase clearly); and engage the five recovery levers in parallel rather than sequentially. The mistake to avoid is treating Microsoft’s first proposal as a starting point — their proposal is already past the tier collapse and shows you only the new reality. Your reference price is what you paid last cycle, adjusted for the legitimate tier impact and nothing else.
The most valuable single move in this window is locking in pre-July-2026 SKU pricing through term commitment. The July 2026 price increase is separate from the tier collapse and entirely avoidable for renewals that sign before that date. See how to lock in M365 pricing before July 2026 for the contract mechanics.
Renewal in 6–12 months
This is the high-leverage window. The buyer has enough time to build a defensible position from scratch and not enough time for that preparation to become academic. Priorities: complete a full licence inventory (most procurement teams who skip this lose 2–5% on the renewal as a result — see the seven costly mistakes guide); benchmark current pricing against current-market pricing for comparable organisations; develop a walk-away position that includes EA renewal, MCA-Enterprise migration, and CSP hybrid as live alternatives; and structure the conversation so Microsoft is responding to your position rather than anchoring you to theirs. The lock-in window for pre-July-2026 SKU pricing is the most time-sensitive consideration.
Renewal in 12–24 months
This cohort has the most strategic flexibility. There is time to actually execute alternatives — pilot Google Workspace, evaluate MCA-Enterprise structurally, build an Azure consumption commitment plan that supports the EA discount lever. Priorities: build the strategic alternatives now so they are mature by the time the renewal conversation starts; reassess the EA-vs-MCA cross-over annually because Microsoft will continue evolving the channel mix; and begin the cross-functional team formation that our renewal preparation framework calls for at T-12.
Renewal in 24+ months
Strategic planning rather than tactical execution. The variables in the 2026 environment will continue to shift — the E7 Frontier Suite is new, Agent 365 is new, the Copilot Studio pricing model is new, and the channel architecture continues to evolve. The right action now is intelligence gathering and capability building: understand the full 2025–2026 Microsoft change set, build internal expertise on the new vocabulary, and develop the procurement framework that will let you act decisively when the renewal window arrives.
Negotiating from a structurally weaker position
The honest assessment is that buyers go into 2026 EA renewals with less structural leverage than they had in 2024 and earlier. The tier collapse removed an automatic discount mechanic that was worth 6–15% on a meaningful portion of the bill. The July 2026 SKU price increase compounds that with a separate 5–33% list-price rise. Microsoft account teams know both of these things, and they know procurement teams know them. The negotiation dynamic has shifted.
The response to that dynamic is not to negotiate harder — aggressive tactics tend to deteriorate the commercial outcome when the underlying leverage is weak. The response is to negotiate more precisely. Three principles separate procurement teams who recover meaningful discount from procurement teams who do not.
First: anchor on outcomes, not on percentages. A 5% discount from Microsoft’s opening proposal sounds like progress and may represent a worse outcome than the prior renewal in absolute dollar terms. The negotiation goalpost should be total annualised cost over the renewal term, compared explicitly to the prior cycle, with the tier-collapse and SKU-price components separated and labelled. Procurement teams who track only percentage discount lose the ability to see whether they are actually winning.
Second: separate the bundled discount. Microsoft’s deal desk routinely bundles concessions on multiple SKUs into a single “total EA discount” figure. That obscures where the discount actually sits, makes it difficult to assess whether each line item is competitive, and gives Microsoft the ability to claw back discount silently in subsequent renewals (the bundled discount goes away; the line-item discounts that constituted it are not transparent). A clean negotiation insists on line-item-level discount visibility, even if Microsoft prefers to discuss the bundle.
Third: protect the term, not just the price. A favourable renewal price means nothing if the term clauses allow Microsoft to adjust it mid-cycle. The contract clauses that matter most in 2026 are: explicit price-lock on the negotiated discount; commitment terms that survive co-term or amendment events; protection against retroactive list-price changes during the term; and clear cancellation rights for products that are subsequently restructured (the Power BI Premium to Fabric F-SKU migration is a current example of why this matters — we cover it in the Fabric migration playbook).
The compounding effects buyers underestimate
The tier collapse looks like a one-time 6–12% increase. In practice it interacts with three other commercial mechanics in ways that amplify the effective impact — and that procurement teams routinely model incorrectly.
Unified Support amplification. Microsoft Unified Support is contractually priced at 8–12% of total Microsoft spend in most enterprise contracts. The percentage is mechanical: as EA cost rises, Unified Support cost rises in lockstep without any new negotiation event. A $1M increase in EA cost produces an $80K–$120K increase in Unified Support cost automatically. The tier collapse therefore costs more than the tier collapse alone, because every dollar of incremental EA cost generates roughly $0.10 of incremental support cost on top. Procurement teams who model only the EA impact miss roughly 10% of the actual cost wave.
True-up amplification. The annual EA true-up applies the current pricing structure to incremental seat counts. In the post-tier-collapse environment, true-up growth pricing is structurally higher than it was before — growth costs more than it used to, on a per-seat basis. For organisations growing 5–15% annually, the cumulative cost of growth over a three-year EA term is now 6–12% higher than the prior term, separately from any list-price increases. We cover the negotiation positions that protect against this in the EA true-up clauses guide.
Renewal anchoring amplification. The 2026 renewal sets the baseline for the 2029 renewal. The post-tier-collapse pricing becomes the historical reference price that the next negotiation works from. A buyer who absorbs the full structural increase in 2026 has built it into their long-term cost trajectory; a buyer who recovers a meaningful portion through the five levers above has shifted their long-term trajectory commensurately. The negotiation outcome compounds over decades, not just the term of the current EA.
What to do in the next four weeks
The tier collapse is a settled fact. The recovery opportunity is open but time-bound. For any procurement or IT leadership team responsible for an EA renewal in the next 24 months, four specific actions in the next four weeks compound into a materially better commercial outcome.
- Quantify the specific exposure. Run your current EA against the post-tier-collapse pricing reality, separating online services (in scope), Azure (out of scope), and perpetual/SA (out of scope). The output is a dollar figure for the structural increase on your renewal — not a generic 6–12% range. Procurement teams who can quote the specific number negotiate differently than procurement teams who cite the range.
- Confirm the renewal date and the Microsoft fiscal-year alignment. If your renewal falls in Q4 of Microsoft’s fiscal year (April–June), the timing lever is available. If not, model whether a co-term or extension can move it into Q4 of a future fiscal year. The exercise takes a day; the payoff is 1–3% on the entire renewal.
- Audit your Microsoft 365 entitlement against actual usage. Independent of the tier collapse, the largest avoidable cost in most EA renewals is over-licensing. The renewal is the once-in-three-years opportunity to reset the entitlement to actual usage. Our M365 optimisation service covers the methodology; the M365 audit self-assessment tool is in development.
- Engage independent advisory support before Microsoft engages you. The structural shift in the negotiation environment means experience matters more in 2026 than it did in 2024. Independent advisory — not reseller, not Microsoft partner — brings current market intelligence and a commercial framework built for buyer outcomes. The cost is recovered many times over in the first year. Our advisors do an initial 30-minute scoping call free of charge to assess fit. Schedule one here.
The structural shift, in one sentence
For fifteen years, Microsoft Enterprise Agreement pricing rewarded volume automatically. From 1 November 2025, it rewards preparation. Buyers who understand the new mechanics, work the five remaining levers, and structure the renewal conversation around their own position rather than Microsoft’s proposal recover most of what the tier collapse takes away. Buyers who treat the renewal as a routine recommit absorb the full 6–12% structural increase and pay it for the next three years. The gap between the two outcomes is, for a mid-market enterprise, somewhere between $500K and $5M over the EA term. The work that closes the gap is preparation that begins twelve months before signature — and at this point in the 2026 cycle, twelve months is exactly the runway remaining for the bulk of the affected renewals.
If you want help with that preparation, that is what we do. Our EA negotiation service is built for the post-tier-collapse environment specifically; our team has worked the new mechanics on more than thirty renewals since the change took effect. Get in touch when you are ready to talk through your specific situation.