The standard Enterprise Agreement permits the buyer to add licenses across the term and forbids the buyer to remove them. The only structural true down event is renewal. That asymmetry costs more than any other single clause in the EA. This page is the practice view on what true down options actually exist, what to negotiate at signature, and how to execute a renewal reset when you did not get the clause the first time.
The Enterprise Agreement is a forward looking commitment. The price discount is calibrated against the assumption that the buyer is committing to a baseline count for the full term. True down would unwind the commitment and the discount with it. Microsoft has no commercial reason to offer it as a default term, and structurally does not.
Mid term, the buyer cannot reduce license counts on perpetual or subscription enrollments without renegotiating the entire enrollment. Departing employees do not reduce the obligation. Headcount reductions do not reduce the obligation. The contracted baseline is the floor for the full term.
The Enterprise Agreement Subscription, the subscription variant of the EA, carries a structural true down right at each anniversary subject to a maximum percentage reduction. EAS gives up perpetual license rights in exchange for that flexibility. For organizations with volatile headcount, EAS is sometimes the right structural answer to the true down problem.
Server and cloud enrollments inherit the same no true down posture as the master EA. Azure consumption commits behave differently because they are dollar denominated rather than seat denominated, but the dollar commit floor is also structurally fixed across the term.
Divestitures, major restructuring, and contract default give rise to negotiated exits in narrow circumstances. None of them are written into the standard EA. All of them require a credible buyer side posture and a willingness to push.
True down rights do not appear in the standard EA. They are negotiated in. The practice argues for five specific clauses at signature, calibrated against the buyer's projected headcount trajectory, M&A pipeline, and product rationalization plan.
An explicit acknowledgement that at renewal the buyer may reduce counts to the consumption baseline regardless of the contracted baseline. This converts the renewal from a defensive negotiation into a clean reset. Microsoft will resist. Buyers who land it preserve material optionality.
The right to remove headcount associated with a divested business unit from the agreement at the time of the divestiture, without penalty and without renegotiating the price level. Standard for buyers in active portfolio management. Almost never present without negotiation.
The right to migrate users from E5 to E3 mid term, capped at a percentage of the population, without forfeiting the E5 discount on the remaining E5 seats. Buyers who deployed E5 broadly often discover only half the users need it. This clause makes that discovery actionable.
A defined material adverse change clause that permits renegotiation of headcount in the event of a defined external trigger. Sized appropriately, this is the clause that protects buyers across genuine business disruption.
For buyers with persistent headcount volatility, the right answer is often not a negotiated true down clause inside an EA. It is electing the EAS variant from the outset. EAS carries the structural flexibility natively. The economics differ by a few percentage points. The decision should be made on the volatility profile of the buyer, not on the headline per seat number. We model both paths against a five year horizon and let the comparison speak.
The renewal is the structural opportunity to right size. Buyers who arrive at the renewal without a posture rarely execute a clean reset. Buyers who arrive with a posture often do. The mechanics are governable.
The renewal converts the prior contract baseline into a negotiable starting point rather than a binding floor. The buyer can elect to renew at the prior count, increase it, or decrease it. Microsoft will price each option differently. The decrease option is the one Microsoft prices most aggressively against, because the renewal discount is calibrated against the assumed renewed baseline.
The mechanics work in the buyer's favor only if the consumption case is built and credible. A renewal that asks for a count reduction without consumption evidence becomes a negotiation against the prior signed instrument. A renewal that arrives with a consumption rebuild becomes a negotiation against the buyer's documented use. The difference is the discount band Microsoft will defend.
Timing matters. The renewal window is roughly eighteen to twenty four months before the anniversary. The buyer who begins the rebuild in month eighteen has time to clean the estate, rationalize add ons, and stage the count reduction in a way that survives Microsoft's pushback. The buyer who begins at month six negotiates from where the count happens to sit at that moment.
Add ons unwind first. The Defender, Purview, and Teams add on stack is rationalized against the base entitlement. The base SKU population is then tested against authentication and feature usage. The result is a defensible new baseline that becomes the renewal posture.
The practice runs a defined sequence whether the buyer has a true down clause or not. The presence of the clause changes the leverage. It does not change the discipline.
We start with a consumption rebuild eighteen months before renewal. The output is the consumption baseline, calibrated against authentication, feature use, and identity hygiene. The baseline is what the buyer can defend, not what the buyer is currently paying for. The gap between the contract count and the consumption baseline is the right sizing opportunity.
We then test the SKU mix. Users on E5 who use no E5 feature get categorized for step down candidacy. Users on Defender for Endpoint who never authenticated against a Defender protected workload get categorized for unwind. The output is a SKU rationalization plan that converts the consumption baseline into a defensible renewal posture.
We then sequence the negotiation. If the original EA carried a true down clause, the renewal becomes a straightforward reset. If it did not, the renewal is staged across the renewal window. We do not negotiate one number. We negotiate the sequence of reductions that survive Microsoft's defense of the renewal discount band.
The deliverable is a renewed EA that matches the consumption baseline rather than the prior contract baseline, plus the clauses that prevent the next cycle from repeating the problem.
Anonymized. Verifiable on reference call. Within the trailing twelve months.
The prior EA had been signed on a peak headcount estimate that never materialized. The original instrument carried no true down language. The practice rebuilt the consumption baseline, staged the SKU rationalization across the renewal window, and negotiated the reduction as a single renewal event.
We arrived at the renewal with a count we could defend with evidence. They priced against that count rather than the old one.Chief Operating Officer · North American insurer
Two analyst calls. No pitch. We tell you what we would do, what the leverage actually is, and whether we are the right firm for this engagement.