Renewals signing before 1 July 2026 can preserve pre-increase Microsoft 365 pricing for the term of the new agreement — typically three years. For a typical mid-market customer, this single action saves 5–9% of the M365 portion of the EA over the new term, or roughly $200K–$700K depending on size. The mechanism is real and Microsoft-confirmed, but it requires three specific contract clauses to hold and the lock can be defeated by two other clauses that appear in Microsoft-drafted EAs. For renewals naturally falling July–December 2026, acceleration almost always produces net-positive savings even after accounting for compressed preparation cost. The window is approximately six weeks at the time of writing.
The lock-in mechanism in plain language
Microsoft has confirmed that customers signing Enterprise Agreements (or equivalent multi-year commitments through MCA-Enterprise or CSP) before 1 July 2026 will pay pre-increase prices for the duration of their new term. The new pricing applies at the renewal after the locked term ends — typically three years later. The mechanism is an explicit transition policy designed to give existing customers predictability and to incentivise pre-deadline renewals.
The mechanism is not a quirk or a loophole. It is documented in Microsoft’s commercial communications and applied as standard practice across the account team population. Procurement teams should not feel they are exploiting a gap; they are using the published transition rules as intended.
What is not automatic is that the lock-in actually holds. Microsoft account teams will sometimes draft contract documents that nominally implement the lock-in but actually allow the new pricing to apply through anniversary order adjustments, true-up pricing, or currency provisions. The procurement work is ensuring the contract clauses match the policy intent.
Three clauses that make the lock real
An EA signed in late June 2026 with the wrong clauses can still see the July 2026 list-price increase applied at the first anniversary order. Three clauses determine whether the lock-in holds:
Clause 1: Explicit unit price lock
The negotiated per-unit price for each affected SKU must be documented in the agreement, with a clear statement that the documented price applies for the term. Look for language like “Unit prices for the Online Services listed in Schedule X shall remain at the levels specified for the Initial Term, regardless of subsequent list-price adjustments by Microsoft.” Avoid language like “Unit prices subject to list-price adjustment at anniversary” — that single clause defeats the entire lock-in.
Clause 2: Anniversary order price-lock language
The price-lock must explicitly apply to anniversary orders, not just to the initial enrollment. EAs include annual anniversary orders that adjust seat counts and add new products; without specific lock-in language, anniversary orders can reprice at prevailing list rather than at the locked rate. The protective language: “Anniversary Orders during the Initial Term shall be priced at the locked unit prices specified in Schedule X, regardless of prevailing list prices at the time of the Anniversary Order.”
Clause 3: True-up pricing protection
True-up orders during the term must price at the locked rate, not at the prevailing list rate. Without this protection, growth during the term — new seats added through the annual true-up process — is priced at post-July 2026 levels even if the original base is locked at pre-July 2026 levels. For organisations expecting growth, this can erode 30–50% of the lock-in value over the term.
Two clauses that quietly defeat the lock
Two additional clauses appear in many Microsoft-drafted EAs and effectively nullify the price lock even when the explicit lock language is present.
The currency adjustment clause
EAs signed in non-USD currencies frequently include a currency adjustment provision that allows Microsoft to adjust unit prices to reflect exchange rate movements. In practice, the clause is exercised one-directionally — Microsoft adjusts upward when the customer’s currency weakens but does not reduce when it strengthens. For organisations outside the USD zone, the currency clause can absorb 5–10% of locked-in discount over the term of the EA. The clean version of the lock-in either eliminates the currency clause entirely or makes it explicitly bidirectional and symmetric.
The product-change clause
Microsoft retains the right under standard EA terms to modify product offerings during the term — renaming SKUs, splitting bundled products, or replacing one SKU with a successor product. Each modification creates an opportunity to apply prevailing pricing rather than locked pricing for the successor product. The Power BI Premium to Microsoft Fabric F-SKU migration is a current example. The protective language requires that any successor or replacement SKU be priced at the locked rate for the original SKU, not at the prevailing rate for the successor.
The acceleration decision math
For procurement teams whose renewal naturally falls July 2026 to December 2026, acceleration is the structural question. The cost-benefit math is:
- Benefit (locked-in savings): 5–9% of the M365 portion of the EA over the new term. For a $5M EA with 60% M365 share, this is $150K–$270K per year, or $450K–$810K over three years.
- Cost (compressed preparation): Typically 1–2% of total EA value in weaker negotiated discount on the non-locked levers (Azure, term commitment, line-item discount). For a $5M EA, this is $50K–$100K per year or $150K–$300K over three years.
- Net benefit: $150K–$510K over three years for the typical mid-market case.
The math favours acceleration in approximately 85% of cases we have advised since the increase was announced. The 15% where it does not are typically organisations with major pending business changes that would benefit from delayed commitment (M&A activity, large workforce changes, technology stack pivots) or organisations that have unusually weak baseline preparation and would benefit more from additional preparation time than from the lock-in savings.
Practical mechanics of accelerating a renewal
Three mechanisms allow renewals to be accelerated into the pre-July window.
Mechanism 1: Early renewal of an existing EA. Most EAs allow renewal up to 90 days before anniversary. For renewals naturally in July, August, or September 2026, this is sufficient to pull signing into June. Microsoft account teams will typically support this when asked because the deal closes earlier in their fiscal year.
Mechanism 2: Co-term extension or amendment. For renewals naturally later than September 2026, the existing EA can be extended through a short amendment to align with a new EA signed in June. This is more complex procedurally but commercially viable for the right size of deal.
Mechanism 3: New EA enrolment. For organisations currently on MCA-E or CSP considering EA migration, signing a new EA before 1 July 2026 locks in pre-increase pricing for the EA term. This is the most aggressive option and only appropriate when the EA migration was already in serious consideration.
Action this week if your renewal is in the affected window
- Confirm your renewal date. Check the EA anniversary date on your current agreement. If it falls July–December 2026, you are in the acceleration window.
- Run the acceleration math for your specific situation. Apply the M365 share of your EA, the percentage savings, and the compressed-preparation cost. Calculate the net benefit.
- Notify Microsoft of intent to renew early. Your account team will support this when asked. The conversation does not commit you to anything — it preserves the option.
- Engage independent advisory immediately. The compressed preparation timeline makes external capacity more valuable, not less. Our advisors are running accelerated renewals weekly through June 2026. Schedule a scoping call.