The Tension at the Heart of Every EA
Every Microsoft Enterprise Agreement involves a fundamental commercial tension: price lock protects you from Microsoft's price increases over the three-year term, while pricing flexibility allows you to reduce your commitment if your needs change. These two protections pull in opposite directions, and Microsoft's standard EA terms are calibrated to give you the minimum of each that still makes the contract commercially acceptable.
The reality of operating in a Microsoft environment between 2022 and 2026 underscores why both protections matter. Microsoft increased M365 pricing by 15–25% across most commercial SKUs in 2022. Organisations with strong price-lock provisions paid pre-2022 rates for their full EA term. Organisations without them absorbed mid-term increases they had no mechanism to prevent. Simultaneously, organisations that over-committed seat counts at renewal — locked into 3-year minimums they couldn't reduce — paid for thousands of unused licences while their workforce restructured. Both risks are real. Both can be mitigated through targeted contractual protections negotiated at the EA signing stage.
This article explains the specific contractual provisions that deliver these protections, what Microsoft will and won't agree to, and how to structure the negotiation to achieve both. For the broader EA negotiation context, see our complete guide to Microsoft EA negotiation.
What Price Lock in an EA Actually Means
The EA's standard "price protection" provision guarantees that the unit prices for licences committed at the time of EA signing will not increase for the duration of the agreement term. If you commit to 1,000 M365 E3 licences at €28.40 per user per month, that price is locked for 36 months. Microsoft cannot unilaterally raise the unit price during the term.
What this protection does not cover is equally important. Price lock applies only to the licences and quantities committed at signing. True-up additions — licences added during the term because your deployment exceeded the committed count — are typically priced at then-current list prices, not at the locked rate. If Microsoft has increased M365 prices since your signing date, your true-up additions pay the new price. For organisations with significant user growth between true-up cycles, this exposure can be material.
Price lock also does not apply to new products added during the EA term. If you add Copilot, a new security SKU, or a Dynamics 365 module mid-term, those additions are priced at current list. Only the original committed SKUs at original committed quantities carry the price lock. Understanding this distinction is essential when modelling your three-year cost commitment.
Microsoft's 2022 M365 price increases were applied to new agreements and renewals — existing EA customers with standard price-lock provisions were protected. But many organisations discovered their price-lock provisions contained carve-outs for "significant product enhancements" — a clause Microsoft used to justify some increases. Reviewing the precise language of your price-lock provision before renewal is essential.
True-Up Pricing Protections: The Gap Most Organisations Miss
The standard EA true-up process prices overage licences — those deployed beyond the committed count — at the then-current price list rate at the time of the true-up, not at the locked rate. In a rising price environment, this means true-up additions can be significantly more expensive than your locked base rate. The gap was negligible when Microsoft held prices steady; it became significant after the 2022 increases.
The protection to negotiate: a provision that prices true-up additions at the lower of current list price or the original locked rate from the EA signing date. Microsoft will resist this — it eliminates one of the key mechanisms by which mid-term price increases translate into incremental revenue on large accounts. But for organisations where significant true-up additions are a predictable feature of their EA (e.g., those in active headcount growth phases or multi-year technology rollout programmes), negotiating true-up price parity with the base rate is a legitimate and achievable ask with the right leverage.
Our guide to true-up clauses explains the full range of true-up commercial provisions available in EA negotiations, including true-up pricing, deployment date definitions, and step-down provisions.
Downward Flexibility: Reducing Licences During the Term
The standard EA includes no provision for reducing licence commitments during the term. Once you commit to 5,000 E3 licences, you pay for 5,000 for 36 months. If your headcount reduces through restructuring, divestiture, or adoption challenges, the licence cost remains. This asymmetry — Microsoft benefits from your growth through true-up additions but is fully protected from your contraction — is structurally embedded in the standard EA.
Flexibility provisions can be negotiated in several forms. A step-down clause allows you to reduce committed licence counts at defined intervals — typically annually — subject to a minimum step-down threshold (e.g., you can reduce by up to 10% of committed count per year, down to a defined floor). A merger and acquisition clause allows licence count reduction following a divestiture or workforce reduction event with documented evidence. A re-scope provision allows a fundamental renegotiation of the EA commitment following a material change in organisational structure.
Annual Step-Down Clause
Allows up to 10–15% reduction in committed seat count at each annual true-up, subject to a minimum floor. Limits downside exposure from workforce changes while maintaining base commitment level that justified original pricing.
True-Up Addition at List Price
Standard EA prices all overage licences at then-current list — not at your locked rate. In a rising price environment, true-up additions can be 15–25% more expensive than your base commitment. Negotiate true-up price parity at signing.
Divestiture Re-scope Right
Allows licence count reduction proportional to employee transfers following a documented divestiture or spin-off. Essential for organisations with active M&A programmes where EA commitments would otherwise balloon relative to retained headcount.
Product Enhancement Carve-Out
Some price-lock provisions contain language allowing Microsoft to increase prices on products with "significant feature enhancements." This clause was used to justify selective price increases post-2022. Ensure your price-lock provision has no such carve-out.
Term Structure and Its Impact on Price/Flexibility Balance
The EA term length — the default is 3 years — directly affects both price lock and flexibility. A 3-year term provides 36 months of price protection on committed SKUs. A 4- or 5-year term extends that protection but also extends the commitment period and reduces your ability to respond to market changes. Microsoft's account teams frequently propose extended terms as a mechanism to increase total contract value; they present the extended price lock as a benefit to the buyer.
The argument for extended terms has surface logic: if Microsoft is likely to increase prices in years 4 and 5, locking in year 1 prices for the full term saves money. The counter-argument is structural: a 4- or 5-year EA signed in 2026 means your next renewal conversation opens in 2030 or 2031. By that point, the M365 and Azure product landscape will have changed materially. Copilot, security products, and possibly entirely new delivery models will have evolved. You want the ability to renegotiate your entire Microsoft commitment — not just the SKUs added mid-term — in a reasonable timeframe.
Our standard guidance is to resist extended terms for the price-lock benefit alone. The price lock on a 4-year EA is worth less than the negotiating flexibility you surrender by being locked out of a full renewal conversation for an additional year. If Microsoft is offering material price discounts for extended term commitment, those discounts should be evaluated against the full cost — including the foregone flexibility — not just the nominal per-unit savings.
Negotiating Price Escalation Caps for the Next Renewal
A lesser-known but highly valuable provision: a price escalation cap that applies at the next renewal. Under standard EA terms, Microsoft can offer any price at your renewal — there is no contractual continuity between the current EA's locked price and the renewal opening position. Microsoft will typically open your next renewal at current list price, not at your prior locked rate plus a reasonable increment.
Some organisations successfully negotiate a renewal price cap — a provision specifying that prices at the next renewal cannot exceed the current locked price by more than a defined percentage (e.g., 5% per year over the term). This is not a standard provision and Microsoft will resist it strongly, but for high-value accounts with significant leverage, it is achievable. The provision must be explicitly included in the contract addendum at the current signing — it cannot be added later.
The argument that supports this ask: price lock at renewal is consistent with Microsoft's stated commitment to long-term customer relationships. An organisation that has been a committed Microsoft EA customer for a decade, has paid consistently and on time, and is committing to another 3-year term deserves certainty about the pricing trajectory of that relationship. That argument is more compelling when delivered by external advisors who can frame it in commercial terms that Microsoft's approval chain can evaluate, rather than as an emotional appeal.
Microsoft account teams will often agree verbally to pricing commitments that are not reflected in the contract addendum. Any price protection, flexibility provision, or escalation cap must be captured in the written agreement or it does not exist. Verbal commitments from account teams are not enforceable. Always insist on contractual language, reviewed by your legal team, before signing.
Bringing This Together: A Negotiation Approach
The provisions described here — true-up price parity, step-down clauses, divestiture re-scope, escalation caps — represent a coherent set of buyer protections that balance price certainty with commercial flexibility. None is independently available through Microsoft's standard EA template. All require active negotiation with documented justification and internal escalation through Microsoft's approval process.
The precondition for securing these provisions is leverage. Microsoft will not volunteer them. They require competitive benchmarking to establish the gap between your current position and market norms, a credible walk-away position on non-essential products, and a negotiation structure that keeps these items on the table through the entire commercial discussion rather than resolving them as afterthoughts once headline pricing is agreed.
Our EA negotiation service includes contractual provision review and negotiation as a standard component. We have seen every variation of Microsoft's EA addendum language across 500+ engagements and have a clear view of which provisions are genuinely non-negotiable and which are opening positions that can be moved with the right approach. The EA Negotiation Playbook covers the full contractual framework in detail, including draft language for buyer-protective provisions that can be proposed as specific addendum amendments.