The Microsoft Enterprise Agreement, read from the buyer side.

The Enterprise Agreement is still the largest line in most software budgets. Knowing how it is built is the first step to paying less for it.

How is a Microsoft Enterprise Agreement structured?

An Enterprise Agreement is a three year contract with an upfront baseline commitment and annual true ups for growth. It runs through enrollments that sit under a master agreement, described on the Microsoft Enterprise Agreement program page. The structure rewards scale and punishes uncommitted change, which is exactly why the baseline number deserves scrutiny.

What is the role of enrollments?

Enrollments are the sub agreements for specific product families, such as the enrollment for Microsoft 365 or for server and cloud. They carry their own terms and dates, which is why co terminating them matters for leverage at renewal.

How does the EA true up work?

The true up is the annual count of licenses added during the year, billed in arrears. The base EA has no symmetric true down, so growth is captured but shrinkage is not refunded. That asymmetry is the single most expensive feature of the agreement for a changing organization.

• Annual count: additions are reported and billed once a year.
• No true down: reductions wait for the renewal to take effect.
• Price exposure: additions priced at the level rate unless protected.

How do you protect the true up?

• Price hold: lock the unit price so growth is billed at your rate.
• Annual basis: report once a year, not at every change.
• Reduction right: negotiate the ability to drop counts at anniversary.

What does Software Assurance give you?

Software Assurance bundles upgrade rights, deployment benefits, training, and support into the EA. The full list sits in Software Assurance benefits. Most buyers pay for it and use a fraction, so the optimization is to inventory the rights and either use them or factor them into the price.

• New version rights: access to upgrades released in the term.
• Use rights: home use, roaming, and disaster recovery benefits.
• Planning and training: bundled days that often expire unused.

Where the common advice on the Microsoft Enterprise Agreement is wrong

The common advice is that the EA is always the cheapest route once you pass 500 seats, so large organizations should default to it. We disagree. In a meaningful share of the estates we benchmarked, a Microsoft Customer Agreement or a Cloud Solution Provider arrangement beat the EA on flexibility and, for cloud heavy or shrinking estates, on price. The buyer side move is to price at least one alternative every renewal rather than rolling the EA forward by reflex. The EA suits stable, growing, on premises heavy estates. It is a poor fit for organizations that are consolidating, divesting, or moving fast to consumption based cloud, where the lack of a true down quietly costs real money.

The EA is not expensive because of its price. It is expensive because of what people commit to without checking.

When should you consider an EA alternative?

Consider an alternative when your estate is shrinking, highly variable, or moving to pure cloud consumption. the Microsoft Customer Agreement and the Cloud Solution Provider program offer monthly flexibility the EA lacks. The right answer depends on size, growth, and how much of your estate is cloud.

How do you decide?

Model your real twelve month trajectory under each program, including true ups and minimums. Decide on total cost across the term and on flexibility, not on the day one discount alone.

What to do next

1. Baseline actual deployment and active users before you set any renewal number.
2. Inventory Software Assurance rights and either use them or price them in.
3. Confirm your pricing level and whether you are near a higher band.
4. Negotiate a price hold and a reduction right on the true up.
5. Co terminate enrollments to one date for renewal leverage.
6. Price at least one alternative program against the EA.
7. Decide on total term cost and flexibility, not the headline discount.

Frequently asked questions

What is a Microsoft Enterprise Agreement?

A Microsoft Enterprise Agreement is a three year volume licensing contract for organizations with 500 or more seats. You commit to a baseline upfront and true up any growth annually, with Software Assurance bundled in.

How does Microsoft EA pricing work?

EA pricing is tiered by organization size into levels A to D, with larger seat counts earning better discount bands. Your unit price reflects your level unless you negotiate a price hold for the term.

What is an EA true up?

A true up is the annual reconciliation that counts and bills licenses added during the year. The base EA has no symmetric true down, so growth is billed but reductions only take effect at renewal.

Is the Enterprise Agreement always the cheapest option?

No. For shrinking, variable, or cloud heavy estates a Microsoft Customer Agreement or Cloud Solution Provider arrangement can beat the EA, so price at least one alternative at every renewal.

What is Software Assurance in an EA?

Software Assurance is a bundle of upgrade rights, use rights, planning, and training included in the EA. It carries real value, but most buyers use only a fraction, so inventory the rights before renewal.

Can you reduce licenses during an EA term?

Not under the base agreement. Reductions normally take effect only at renewal, which is why negotiating a midterm reduction right is valuable for organizations that expect to shrink.

How many seats do you need for an EA?

An Enterprise Agreement generally requires at least 500 users or devices. Below that threshold, other programs such as CSP are usually the appropriate route.

When does it make sense to leave the EA?

Leaving the EA makes sense when your estate is consolidating, divesting, or moving to consumption based cloud, where monthly flexibility and the absence of a fixed baseline outweigh EA discounts.