EA Renewal · Price Protection

Price protection that survives the term. Named unit pricing, not percent off list.

A working brief on price protection language inside Microsoft EA agreements. The default trap, the five questions to ask before signature, and the clause structure that holds. Net present value of properly drafted protection sits in the seven figures on agreements over fifty million.

Contact Us EA renewal practice →
The situation

The headline price is not the price.

Most enterprises negotiate the unit price on the Microsoft EA renewal and treat the work as done. The deal desk concedes a few percentage points on M365 E3, a few more on E5, a small discount on Azure commit, and the agreement gets signed. Eighteen months later, true ups arrive at a different unit price. Expansion SKUs are priced at list. Future product additions reset the discount entirely. The headline price negotiated at signature was a one time concession on the base purchase, not a durable commitment. Price protection is the contract language that turns the negotiated unit price into a binding term over the life of the agreement.

What price protection actually means

The clause has to name the price.

The default Microsoft EA paper contains no meaningful price protection. The agreement states that pricing is fixed at the level set forth in the program signature form, which itself references the enrollment schedule, which references the product terms accessible at a URL. The actual unit price the buyer believes was negotiated is not in the body of the agreement. It is inferred from a chain of references that Microsoft can update.

  • Named unit pricing. SKU by SKU, currency by currency, with the negotiated unit price stated verbatim in the body of the agreement or in a signed amendment.
  • True up unit pricing. True up purchases priced at the same unit price as the original order, not at list with discount reapplied.
  • Expansion pricing. New users added inside the term priced at the same unit price as the original order.
  • Future SKU pricing. A pricing methodology stated for SKUs that did not exist at signature but become available during the term.
  • Currency stability. Where multi country enrollment exists, the exchange rate basis is fixed for the term or capped to a defined band.
The default trap

What Microsoft writes if you do not insist.

The default amendment language Microsoft will offer references a percentage discount off list. A percentage discount off list looks like price protection but is not. Microsoft retains the ability to change list price during the term. The negotiated discount applies to a moving target. By year three of the agreement, the actual unit price the buyer pays may exceed the original quote despite the discount remaining intact on paper.

The buyer side remedy is to insist on absolute unit pricing in the negotiated currency. Not a percentage off list. The discrete number, stated in the contract.

The five questions

What to ask before signature.

  • Where in the document is the unit price stated for each SKU we negotiated?
  • What unit price applies to true up purchases during the term?
  • What unit price applies to user expansion during the term?
  • What methodology applies to SKUs that come available during the term and that we may want to add?
  • What is the unit price on the same SKUs at the next renewal, assuming continuity?
The single most common drafting failure on enterprise EA agreements is to negotiate a percent discount and to call that price protection. It is not. Microsoft retains the ability to revalue list during the term. The negotiated discount stays intact while the unit price the buyer actually pays drifts upward.
Practice principle · EA contract language reviews
The renewal protection

The clause that survives this term.

The most underused piece of price protection language in Microsoft contracting is the next renewal ceiling. A clause that caps the unit price increase at the next renewal to a defined percentage of the current price gives the buyer a durable position into the following cycle. Microsoft will resist the clause. The deal desk will argue it cannot commit to future pricing. The clause is signed regularly in renewals that run with a buyer side anchor letter and a credible walk away scenario.

  • Renewal ceiling. Defined percentage cap on unit price increase at the next renewal for the same SKU mix.
  • Trigger conditions. The cap applies if the buyer renews on EA or migrates to MCA E.
  • Currency stability. Exchange rate basis carries through to the next renewal.
Mid term true up

The other place price drifts.

Mid term true up is the moment Microsoft revisits the deal. Anniversaries are the contractually mandated purchase windows for users added during the year. Without explicit true up pricing language, the unit price applied is whatever Microsoft chooses, almost always at the higher end of the band.

The buyer side remedy is to name the true up unit price in the contract. Same SKU, same price, for the duration of the term.

What the language looks like

A working clause structure.

Drafting varies by jurisdiction and by the specific Microsoft paper template in play. The following is a working clause structure that has cleared deal desk review in active engagements during 2025 and 2026. Counsel should adapt the language to the specific enrollment.

  • Stated unit price. The negotiated unit price for each listed SKU is set forth in Exhibit A and shall apply to all purchases under this enrollment for the duration of the initial term.
  • True up parity. True up purchases at each anniversary shall be priced at the unit price set forth in Exhibit A.
  • Expansion parity. New users added during the term for any SKU listed in Exhibit A shall be priced at the unit price set forth in Exhibit A.
  • Future SKU methodology. SKUs that become generally available during the term and that are functionally equivalent to SKUs listed in Exhibit A shall be priced using the methodology set forth in Exhibit B.
  • Renewal ceiling. The unit price applicable at the next renewal shall not exceed the unit price set forth in Exhibit A by more than the agreed cap, provided the renewal is signed before the end of the current term.
Our advisory angle

The clause is the savings.

A signed price protection clause that names unit pricing, applies to true ups and expansion, and caps the next renewal is worth more in cumulative savings than the discount negotiated on the base order. Across our active portfolio, the net present value of properly drafted price protection language sits in the seven figure range on agreements of fifty million dollars and above. The work to get the language right is mechanical. The savings are durable. Most enterprises that lose price protection at signature do so by accepting the default Microsoft paper and treating the negotiated discount percentage as sufficient.

Field notes

What we have learned about price protection.

Price protection language is the area of EA contracting where buyer side advisory adds the most durable value. The work is unglamorous. It happens in the last six weeks before signature. It does not move the headline discount that the procurement team reports to the steering committee. It does, over the life of the agreement, protect more value than the headline discount itself. Three field observations recur across every enterprise EA we have reviewed.

Field note 01

The amendment language is the agreement.

The body of a standard Microsoft EA agreement contains very little of the negotiated commercial terms. The negotiated terms live in the amendment, which is appended to the agreement and which references specific exhibits. The buyer who reads only the body and signs based on the headline pricing in the program signature form is signing a document that does not contain the protections discussed in negotiation. Read the amendment. Read the exhibits. Verify each negotiated term against its written form.

Field note 02

True up pricing is the most commonly lost protection.

Across the reviews we have run on agreements signed without buyer side legal review, the most common protection failure is true up pricing. The amendment language specifies a discount off list at signature, but the true up pricing methodology is left to the standard product terms accessed at a URL. Eighteen months later, true up purchases are priced significantly above the original order. The buyer believes the negotiated discount applies. The legal reality is that it does not.

The remedy in a renewal under preparation is to name the true up unit price in the body of the amendment, SKU by SKU. The remedy in an agreement already signed is to negotiate a side letter at the next anniversary that establishes the missing protection going forward.

Field note 03

Currency volatility erodes the deal.

Multi country enterprises that signed multi currency EAs in 2023 and 2024 have seen material erosion of the negotiated unit price through currency movement. Without a stated exchange rate basis or a currency stability clause, the buyer absorbs the full impact of foreign exchange volatility through the term. The protection is mechanical and Microsoft is generally willing to concede it inside a negotiation. The protection is rarely raised because most buyer side teams are not focused on currency exposure during the commercial negotiation.

A review checklist

Read the amendment against this list.

Before the final signature, the buyer side legal team should be able to answer yes to each of the items below. A no on any item is a flag to reopen the negotiation, even at cost of additional days to close.

  • Is each negotiated unit price stated in the body of the amendment or in a signed exhibit?
  • Is true up unit pricing named for every SKU subject to anniversary purchase?
  • Is user expansion pricing named for every SKU subject to mid term additions?
  • Is the methodology for future SKU pricing stated?
  • Is the renewal ceiling clause present and does it cover the SKU mix actually purchased?
  • Is the currency basis stated for multi country enrollment?
  • Are all references to standard Microsoft product terms accessed by URL explicitly subordinated to the negotiated language?
  • Are all side letters signed at the same time as the agreement and referenced in the body?
Related reading

Other renewal levers.

Each note here is a tactical brief drawn from active EA negotiations. Read alongside this one to build a complete posture before the quote arrives.

Initiate engagement

Write before the renewal quote becomes a position.

Two analyst calls. No pitch. We tell you what we would do, what the leverage actually is on your renewal, and whether we are the right firm for this engagement. Buyer side only. Never affiliated with Microsoft.

Contact the practice
EA engagements112
Cumulative savings$420M+
Audit exposure cut79%