The Enterprise Agreement Subscription, known as EAS, is the subscription variant of the EA. It carries the structural true down right that the perpetual EA does not. It carries a slightly different economic profile, a different audit posture, and a different fit pattern. This page is the practice view on what EAS actually is, when it wins against the perpetual EA, and what to negotiate at signature.
EAS is the subscription variant of the Enterprise Agreement. Same master agreement architecture. Same anniversary anchored term. Different rights at the underlying license layer, and a different reconciliation profile that creates the structural true down opportunity the perpetual EA does not provide.
All entitlements are subscription based. No perpetual license rights accrue across the term. The end of the agreement is also the end of the entitlement unless renewed. The economic trade off is structural flexibility in exchange for the loss of the perpetual right.
Qualifying SKUs accrue perpetual rights across the term. Subscription only SKUs behave as subscription. The mixed model is the historical default for organizations with large on premise server and SQL estates. No true down during the term. The renewal is the only reset event.
EAS permits the buyer to reduce the count at each anniversary, subject to a defined percentage cap. The cap is negotiable at signature. The default cap is conservative. Buyers with volatile headcount should negotiate the cap up.
EAS entitlements end at non renewal. The buyer migrating off EAS does not retain perpetual rights to the subscription products. Buyers should plan exit pathways before signing rather than after.
EAS is not a default answer for any cohort. It is the structural answer for a defined set of buyer profiles where the true down right outweighs the loss of perpetual entitlements.
Buyers with persistent year over year headcount swings extract more value from EAS than from the perpetual EA. Each year of true down accumulates against the cost of carrying a stranded baseline.
Buyers actively divesting business units benefit from the EAS true down at each divestiture event. The reduction is structural rather than negotiated, which compresses the cycle time.
Buyers without material on premise server, SQL, or other perpetual qualifying estates give up little by moving to EAS. The perpetual right that the EA preserves applies to product families the buyer is not using.
Retail, hospitality, agriculture, and project consulting models with persistent seasonal headcount cycles fit EAS naturally. The annual true down absorbs the cycle.
Companies with uncertain growth trajectories benefit from the optionality EAS provides on the downside while preserving the discount on the upside through true up.
Buyers absorbing acquired headcount during a multiyear integration program benefit from the true down right as integration synergies are captured and headcount normalizes downward.
EAS is the wrong answer for the inverse cohort. Three profiles in particular should default to the perpetual EA rather than EAS.
Buyers running Windows Server, SQL Server, and other perpetual qualifying SKUs at scale lose meaningful value moving to EAS. The perpetual rights the EA preserves on those product families are structurally valuable and are not replaced by anything in the EAS economics.
Buyers with predictable steady state headcount across the next three to six years extract no value from the EAS true down right because they will never need to use it. The slightly higher per seat economics of EAS is pure cost.
Buyers with established renewal practices already use the renewal event to right size. The EAS structural right is a substitute for negotiated true down at renewal. Buyers already winning that negotiation do not need the structural right.
Public sector and heavily regulated buyers often have documentation, audit, and budget governance requirements that fit the perpetual EA structure more cleanly than the EAS variant. The structural exit cost is sometimes not worth the flexibility.
EAS has its own drafting traps. They differ from the perpetual EA traps. We see four points where signature decisions persistently cost buyers value across the term.
The default true down percentage cap is calibrated to Microsoft's preferred posture rather than the buyer's volatility profile. Buyers should negotiate the cap up against their actual headcount swing history. Most buyers do not even ask. The cap is durable across the term.
The exit pathway should be documented at signature. Data egress timelines, perpetual product family carve outs, and post termination support need to be defined before the buyer needs them. Negotiating exit terms at end of term is negotiating without leverage.
If the buyer's profile may shift across the term, a defined mid term migration pathway to the perpetual EA preserves optionality. Microsoft will permit it on negotiation. Default behavior requires a full renegotiation.
Specific SKUs sometimes carry their own subscription term inside the broader EAS. The term should be aligned to the EAS anniversary. Out of phase SKU level subscriptions create annual reconciliation headaches and avoidable cost surprises.
The practice runs the EA versus EAS decision as a discrete model. The model is the same architecture as the EA versus MCA E decision but with different inputs and a different output set.
We start from the buyer's headcount profile across the prior five years and the projected five year horizon. The profile shows the realized volatility, the directional trend, and the inflection points that drove either growth or contraction. The volatility band is the input that drives most of the decision.
We then layer the SKU footprint. Buyers heavy on perpetual qualifying SKUs absorb more value loss on EAS than buyers with cloud first estates. The SKU footprint adjusts the volatility threshold at which EAS becomes the right answer.
We then run the five year economics. The output is two cost projections, two leverage profiles, and a recommendation calibrated against the buyer's procurement capability. The economics conversation focuses the CFO. The leverage profile focuses the CIO. The recommendation closes the decision.
When EAS is the right answer, the negotiation focuses on the four drafting traps above. When the perpetual EA is the right answer, EAS sometimes still becomes a useful negotiation lever because the credible threat of an EAS election sometimes opens additional concession band on the perpetual EA. The model creates the credibility.
Anonymized. Verifiable on reference call. Within the trailing twelve months.
The prior perpetual EA had been signed at peak seasonal headcount and had been carrying twenty five percent of that peak as stranded baseline year over year. The practice modeled both paths, found EAS economically dominant over the five year horizon despite the per seat premium, and negotiated a higher than default true down cap at signature.
We had been paying for the peak season every month for three years. The new agreement matched what we actually used.Senior Vice President of Finance · Global hospitality operator
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.