The Price Increase Reality Every EA Customer Faces
Between 2021 and 2023, Microsoft executed the largest set of commercial price increases in its enterprise history. M365 E3 rose 9–15% depending on channel. M365 E5 increased 12–25%. Azure pricing for certain reserved instance categories shifted materially. Customers mid-term in three-year EAs discovered that their contracts — which they assumed were fixed — contained exposure they had never understood at signing.
The problem is not that Microsoft raises prices. All enterprise software vendors do. The problem is that the standard EA contains price protection language that is far narrower than most buyers assume. Customers believe their EA locks pricing for the term. In practice, the standard agreement only locks the prices of products on the initial order form for the current product set. True-up additions, new products, and license count increases are almost always priced at current rates — which may be materially higher than the rates in place when the EA was signed.
Price protection in a Microsoft EA is not automatic. It must be negotiated — and it must be negotiated precisely, because the standard language Microsoft's legal team will accept is carefully circumscribed. This article explains what is achievable, how to negotiate it, and the contractual failure modes that leave enterprises exposed.
What the Standard EA Actually Protects — and What It Doesn't
The standard Microsoft Enterprise Enrollment (the core EA document) contains a pricing clause that fixes the per-unit price for products on the initial order for the duration of the three-year term. This sounds comprehensive. It is not.
Four categories of spend are explicitly outside standard price protection:
True-up additions above the initial baseline. When you add licences above your original enrolled quantity at true-up, Microsoft prices those additions at the rates in effect at the time of the true-up — not the rates locked at signing. If M365 E3 has increased 15% since your EA start date, your incremental licences at the first annual true-up are priced at the higher rate.
New products added by amendment. Any product not on the initial order form and added via EA amendment is priced at current rates. This is the mechanism through which Copilot, Defender add-ons, and Power Platform licences have been priced at current (higher) rates for customers who signed EAs before those products were available or before they decided to deploy them.
Subscription renewals at the end of term. The price lock applies for the three-year term. At renewal, Microsoft resets to current pricing — unless you negotiate a price cap for the renewal at the time of the original EA. This is achievable but rarely offered proactively.
Azure consumption above MACC commitment thresholds. Azure Monetary Commitment (MACC) arrangements within an EA have their own pricing mechanisms. Overage consumption above committed spend is generally priced at current pay-as-you-go rates unless specific Azure reservation or savings plan pricing has been locked. See our Azure MACC negotiation guide for specifics on Azure commitment pricing.
Standard EA price protection covers existing products at existing quantities. It does not protect against increases on incremental purchases, new products, or renewal pricing. Each of these requires a separate, explicitly negotiated contractual provision.
The Four Price Protection Mechanisms Available in EA Negotiations
There are four distinct mechanisms enterprises can negotiate into an EA to achieve price certainty beyond what the standard document provides. They vary in what Microsoft's legal team will accept, how much commercial value they require to unlock, and how robustly they protect against different exposure types.
1. True-Up Pricing Lock
A true-up pricing lock is a contractual provision that fixes the per-unit price for true-up additions at the rates in effect at EA signing, for the full three-year term. This means that even if you add 500 licences at your second annual true-up, you pay the rate negotiated at signing rather than the rate Microsoft is charging at that point.
Microsoft will generally agree to true-up pricing locks for M365 and EMS products in engagements of sufficient scale (typically £500K+ annual commitment) when the buyer can demonstrate good-faith intent to maintain the product set. The language to request: "Per-unit pricing for all true-up additions shall be fixed at the pricing set forth in the initial Order Form for the duration of the Enrollment term."
The negotiating lever is growth commitment. If you can demonstrate that your user base is likely to grow by 10–20% over the term, you are offering Microsoft revenue visibility in exchange for pricing certainty. Framed correctly, this is a straightforward commercial exchange — not a confrontational demand.
2. New Product Price Cap
A new product price cap provisions a maximum uplift percentage for products added to the EA by amendment during the term. Typical language achieves a 0–5% cap on per-unit pricing for new additions, relative to a baseline price list. This is harder to obtain than a true-up lock because Microsoft's product pricing strategy relies on the ability to price new products (particularly cloud products) at current market rates.
Realistic outcomes vary by product category. M365 add-ons (Defender, Purview, Power Platform per-user) are more likely to attract a new product price cap than Azure services or Copilot. The strongest argument for obtaining a new product cap is a multi-year deployment roadmap — if you can show Microsoft you intend to deploy specific products on a defined schedule, you are providing the revenue visibility needed to justify price commitment.
3. Renewal Price Cap
A renewal price cap commits Microsoft to a maximum percentage increase on the per-unit pricing for renewal — typically expressed as CPI-linked (2–4%) or a fixed cap (5–8%). This is the least commonly secured provision because it has the longest time horizon and the largest commercial risk for Microsoft. However, in multi-year strategic engagements — particularly those involving MACC commitments above £5M — renewal price caps are achievable with the right escalation path and commercial framing.
The language to anchor on: "Renewal pricing for products on the initial Order Form shall not exceed [X]% above the pricing in effect at the end of the current Enrollment term." Note that this language ties the cap to end-of-term pricing, not signing-date pricing — ensuring the cap compounds rather than resets.
4. Structural Price Lock via Evergreen EA
An evergreen EA (an EA with automatic renewal provisions) can be structured to carry forward current pricing to the next term. This is a different mechanism from a cap — it is a contractual continuation of pricing rather than a ceiling on increases. Evergreen structures work best for stable M365 deployments with consistent licence counts. They are less appropriate for organisations with significant Azure growth or evolving product strategies because they can constrain commercial flexibility at renewal.
What Microsoft's Legal Team Will and Won't Accept
Microsoft's enterprise licensing contracts are ultimately negotiated through a defined approval chain — field rep, account team lead, regional licensing manager, Enterprise Licensing Desk (ELD), and in complex cases, Microsoft's commercial legal team. Each level has standardised language and non-standard language that requires escalation to approve.
| Protection Type | Likelihood of Approval | Minimum Deal Size | Key Negotiating Lever |
|---|---|---|---|
| True-up pricing lock (M365/EMS) | High — standard escalation | £250K+ annual | User growth commitment |
| True-up pricing lock (Server products) | Moderate-High | £150K+ annual | SA continuation |
| New product price cap (M365 add-ons) | Moderate — ELD required | £500K+ annual | Deployment roadmap |
| New product price cap (Azure) | Low-Moderate | £2M+ MACC | Multi-year consumption commitment |
| Renewal price cap (CPI-linked) | Moderate — commercial legal required | £2M+ annual | Long-term relationship commitment |
| Renewal price cap (fixed %) | Low — requires VP approval | £5M+ annual | Strategic account designation |
| Evergreen pricing continuation | Moderate | £1M+ annual | Stable user base, no Azure growth |
The table above reflects typical approval pathways in 2025–2026. Deal-specific factors — particularly competitive alternatives on the table and the customer's strategic value to Microsoft — will shift these thresholds materially. Customers who arrive with a documented competitive evaluation and independent pricing benchmarks consistently achieve outcomes one tier better than what is shown above. The leverage points that shift Microsoft's approval thresholds are the difference between what Microsoft will approve in principle and what your field rep thinks is achievable.
How to Negotiate Price Protection Language: Practical Guidance
Most negotiations over price protection fail because the buyer asks for the wrong thing in the wrong way. A request to "freeze pricing" or "lock costs for the term" is too broad and will be declined by field reps who lack authority over non-standard language. The path forward requires precise contractual language submitted through the right channel.
Step 1: Identify Your Exposure Points First
Before any discussion with Microsoft, conduct a line-by-line audit of your current or proposed EA. Map every SKU to one of four categories: (a) protected under standard pricing clause, (b) exposed at true-up, (c) exposed on new product add, or (d) exposed at renewal. This maps your financial exposure to specific contract provisions — which lets you prioritise which protections are worth the commercial concessions required to obtain them.
Enterprises with stable user bases and few anticipated additions may find that renewal price cap protection provides the highest return on negotiating effort. Organisations planning significant M365 expansion — deploying Copilot, adding Defender, or growing into E5 — should prioritise true-up and new product protections first.
Step 2: Submit Specific Language Requests, Not General Asks
Price protection provisions need to move through Microsoft's approval chain as specific contract language, not as a general commercial request. Submit the exact language you want inserted — specifying the provision number in the standard EA it modifies, the products it covers, the pricing period it applies to, and the baseline price list it references. Vague requests stall; precise language requests can be escalated and approved.
Step 3: Connect Price Protection to a Deployment or Growth Commitment
Microsoft's legal team is more likely to approve price protection language when it is linked to a commercial quid pro quo. The most effective framing: a growth or deployment commitment in exchange for pricing certainty. "We commit to maintaining our current licence count plus 15% growth over the term, in exchange for true-up pricing locked at initial Order Form rates." This converts a one-sided protection ask into a mutual commercial commitment that Microsoft's approvers can justify internally.
Step 4: Escalate to ELD Before Microsoft's Field Team Reaches the Table
Field reps can approve standard true-up locks in larger engagements. Anything more complex — new product caps, renewal caps, hybrid protection structures — requires the Enterprise Licensing Desk. Do not wait for your rep to escalate on your behalf. Include a specific request for ELD involvement in your written summary of commercial requirements, framed as a standard process step rather than an escalation of conflict. Advisors who have ELD relationships can accelerate this by days to weeks. See our EA renewal timeline guide for the right moment to introduce ELD into negotiations.
If Microsoft Announces a Price Increase Mid-Term: Your Response Framework
In 2022 and 2023, Microsoft notified enterprise customers of price increases mid-term for M365 products. The standard EA language gave Microsoft the right to adjust prices with 30–60 days' notice for changes affecting the underlying product or service definition. Some customers were better protected than others based on their specific contract language.
If you receive a mid-term price increase notification, take these four steps before accepting or engaging:
Review your specific agreement language. Pull your EA, enrollment, and all amendments. Look for the exact pricing clause, any non-standard language added at signing, and any definition of "product" or "service" that Microsoft may be relying on to justify the increase. The standard pricing clause in most EAs signed before 2022 contains stronger protection than Microsoft's notifications implied — some customers successfully challenged the increases on contractual grounds.
Document your entitlement position. Before engaging Microsoft, confirm exactly which products are on your initial Order Form versus added by amendment. Only initial Order Form products carry the standard price lock — and even that protection can be argued more forcefully if you have precise entitlement documentation to reference.
Request a formal written explanation of the contractual basis for the increase. Do not accept verbal explanations from your account team. A written request for the specific contractual provision authorising the mid-term adjustment triggers a formal review process and slows the implementation timeline — creating a window for negotiation or challenge.
Use the increase as renewal leverage. Even if the mid-term increase ultimately applies, document the commercial impact precisely and use it as an anchor in your next renewal negotiation. Enterprises that quantify the impact of a mid-term increase ("this cost us £340K beyond the contracted amount") have a powerful argument for higher discounts at renewal — not as a punishment, but as a genuine correction of the relationship's commercial terms.
The 2022 M365 price increase applied to new and renewing customers, not to customers mid-term in active EAs with standard price lock language. Many enterprises paid the increase unnecessarily because their procurement teams did not review their contract language carefully. Always review before accepting a Microsoft price change notification.
Securing Price Protection for Your Next Renewal
The optimal moment to negotiate price protection for renewal is at the current EA signing — not at the next renewal date. When you are renewing, Microsoft holds the leverage of timing pressure: your current agreement expires in 60–90 days, and the cost of switching or delaying is real. At current signing, you are Microsoft's committed customer for three years, and they are competing for that commitment. That asymmetry favours you.
Three provisions to target in your current negotiation for the next renewal: (1) A price cap on renewal, expressed as maximum percentage uplift on initial Order Form rates; (2) A right to renew at existing terms ("evergreen option") for a defined period, which creates optionality even if you don't ultimately use it; and (3) A most-favoured-nation (MFN) clause for enterprise customers of comparable size and spend profile. MFN language is difficult to obtain but worth attempting for engagements above £5M annually — it creates a floor on commercial terms that provides genuine protection against being priced above peers.
For a full view of the contractual provisions worth negotiating in each EA cycle, see our complete enterprise agreement negotiation guide. For the specific renewal process that creates the right context to introduce price protection asks, our EA renewal preparation guide covers the 18-month timeline in detail.
How an Independent Adviser Changes the Outcome
In our 500+ enterprise agreement engagements, price protection provisions are among the highest-value outcomes we consistently deliver for clients. The reason is not that we have unique relationships with Microsoft — it is that we know the precise language that moves through Microsoft's approval chain, the commercial quid pro quos that justify non-standard provisions, and the escalation paths that bypass field-level constraints.
Enterprises negotiating EAs directly with their Microsoft account teams are limited to what their rep has authority to offer. Field reps are trained to minimise the scope of non-standard provisions, not to maximise buyer protection. An independent adviser visible in the negotiation signals to Microsoft's commercial team that the buyer knows what they are asking for and why — which triggers a materially different internal response.
Contact our firm to review your current EA for price protection gaps and structure your next renewal to close them. Our EA negotiation advisory service is structured around measurable outcomes — our fee is typically recovered multiples over on the first renewal alone.