The standard Enterprise Agreement permits step up. It does not, by default, permit step down. The buyer who needs to move a population from E5 back to E3, from E3 back to F3, or from Business Premium to a Defender attached E3, has to negotiate the right into the contract at renewal. Microsoft does not extend it freely. For an estate with twenty percent E5 attach, the step down right on a five thousand seat population can return $2M to $4M across a three year term. The right needs to exist before the analysis becomes actionable.
The default Enterprise Agreement is a commit. The buyer commits a quantity of each SKU for the term. Increases are accepted through the annual true up. Decreases at SKU tier are not contemplated unless explicit step down language is in the agreement.
Without negotiated language, every E5 seat purchased at the start of the term remains E5 for thirty six months. A population that no longer requires the security and compliance stack continues to be paid for at the E5 price.
The default rule above applies to the EA. The Enterprise Agreement Subscription, the M365 EA variant, permits reductions at anniversary. The MCA E permits month to month subscription changes with monthly billing. Buyers on the right instrument inherit different flexibility.
Four common step down paths cover the majority of mid term tier movements. Each has different mechanics and different negotiation difficulty.
The most common request. Users overprovisioned on E5 when the security and compliance attach was aspirational, not consumed. Step down to E3 saves roughly $25 to $30 per user per month depending on discount band.
Frontline population on E3 that meets the F3 use case definition. F3 carries the Microsoft frontline restrictions but covers the workload pattern of most desk less workers. Roughly $20 to $26 per user per month savings.
The two adjacent paths. Defender Plan 2 step down to Plan 1, or removal entirely. Power BI Pro removal from users who do not authenticate. Teams Phone removal from users in the wrong country license footprint.
The negotiated step down right has three components. The trigger, the scope, and the cap. Each component is leverage at the renewal table.
The standard trigger is the annual anniversary of the EA enrollment. Step down adjustments are submitted thirty to sixty days before anniversary, take effect at anniversary, and reset the billing for the year that follows.
Buyers who do not contract a specific trigger end up depending on Microsoft account team discretion, which is unreliable across reorganization cycles. The contracted trigger removes the variability.
The scope clause defines which SKUs are eligible. Buyers should negotiate the full M365 base SKU set, the major add on families, and Defender plans. Excluded SKUs become friction at the moment of move.
The cap clause defines how much of the population can move at each anniversary, commonly fifteen to twenty five percent of the total committed seats for that SKU. The cap protects Microsoft from a wholesale exit but should be set high enough to absorb any realistic step down volume.
The step down concession is one of the most asymmetric value items in an EA negotiation. Low cost for Microsoft to grant at the table, high value to the buyer across the term.
We start with the consumption telemetry. Which users on E5 actually authenticate against Defender Plan 2, Purview eDiscovery Premium, Entra ID P2, and the other E5 exclusive workloads. The population that does not is the step down candidate set.
The case is presented as a documented business need, not a financial request. Microsoft account teams are more responsive to a tiering exercise than to a pure cost ask. The two are functionally identical but the framing matters at the table.
The step down clause sits in the EA amendments. We benchmark the cap percentage and scope language against signed concession data from comparable enterprises, present the language alongside the renewal financial commit, and use it as part of the broader concession package.
The clause typically lands at the same negotiation moment as future product use rights and price protection. All three are buyer side defensive items that Microsoft accepts in exchange for the renewal close. The package is more efficient than each clause negotiated individually.
Benchmarked language for anniversary step down rights across E5, E3, F3, and the major add ons. Sent with our M365 tiering analysis template.
The clause needs to be drafted, benchmarked, and tabled before the renewal close. After signature the right cannot be added mid term without a commercial concession Microsoft rarely offers.