Microsoft MPSA versus the Enterprise Agreement which fits in 2026.

MPSA and the Enterprise Agreement solve different problems. One is a flexible purchasing vehicle with no commitment, the other a discounted three year lock. Picking wrong costs real money.

This guide is for procurement and license teams choosing between the Microsoft Products and Services Agreement and the Enterprise Agreement. Read it with the Microsoft Enterprise Agreement guide and the Microsoft NCE licensing guide.

The choice is not about size alone. It is about how predictable your buying is and how much commitment you are willing to trade for a deeper discount.

What are MPSA and the Enterprise Agreement?

Both are Microsoft volume licensing agreements, but they sit at different points on the commitment scale. One is a flexible buying account, the other a negotiated enterprise contract.

What is the MPSA?

The Microsoft Products and Services Agreement is a single transactional agreement with no enterprise wide commitment. You buy what you need when you need it. The Microsoft MPSA program page describes its structure.

• No commitment: no minimum seat count or term lock.
• Transactional: buy in batches as needs arise.
• Single agreement: one account across business units.

What is the Enterprise Agreement?

The Enterprise Agreement is a three year contract with a minimum qualified seat count. It bundles deeper discounts and Software Assurance in return for the volume commitment across the term.

How does commitment differ between MPSA and EA?

Commitment is the core difference. The EA asks you to lock volume for three years. The MPSA asks for nothing beyond the current order.

What does the EA commit you to?

An EA requires a minimum qualified device or user count, historically around 500, and an enterprise wide standard for the products you commit to. You true up additions each year and the term runs three years.

How flexible is the MPSA in practice?

MPSA lets you buy licenses and online services without a forecast. There is no annual true up obligation and no enterprise standard. That flexibility is its main advantage for irregular buyers.

The EA discount is real, but it is a discount on a three year commitment. MPSA trades that discount for the freedom to buy on your own schedule.

How do pricing and discounts compare?

The EA generally wins on headline discount because of the volume commitment. The MPSA trades some discount for the freedom to buy on your own schedule.

Which agreement discounts deeper?

The EA price levels reward higher committed volume with steeper discounts. MPSA pricing tiers exist but tend to sit above EA pricing for the same volume, because there is no multi year commitment behind them.

• EA: deeper discount, tied to committed volume.
• MPSA: moderate discount, no commitment required.
• Net effect: EA wins on price when volume is predictable.

How does Software Assurance differ?

Under an EA, Software Assurance is bundled into the enterprise products by default. Under MPSA you choose Software Assurance per purchase, which suits estates that only want it on some products.

Which agreement fits your estate?

The fit follows your buying pattern. Predictable, large, and standardized leans EA. Variable, smaller, and selective leans MPSA.

When does the EA make sense?

Choose the EA when you have stable headcount above the minimum, a standardized product set, and the appetite to commit for three years in return for the deepest discount.

When is MPSA the better choice?

Choose MPSA when buying is irregular, headcount is uncertain, or you want to avoid a three year lock. It also fits estates buying a narrow set of products rather than an enterprise wide standard.

Suggested reading

• Microsoft Enterprise Agreement guide. Cross vendor reading from the wider library.
• Microsoft NCE licensing in 2026. Cross vendor reading from the wider library.
• Microsoft licensing pillar hub. Cross vendor reading from the wider library.

What to do next

1. Map your Microsoft buying pattern over the last three years for predictability.
2. Count qualified seats against the EA minimum to test eligibility.
3. Model EA discount levels against your committed volume.
4. Price the same volume under MPSA tiers for comparison.
5. Decide where Software Assurance is genuinely needed across the estate.
6. Choose the agreement that matches your buying pattern, not just your size.

Frequently asked questions

What is the difference between MPSA and an Enterprise Agreement?

MPSA is a transactional agreement with no commitment, while the Enterprise Agreement is a three year contract with a minimum seat count and deeper discounts. MPSA favors flexibility; the EA favors price through commitment.

Does MPSA require a minimum purchase?

No, the MPSA has no enterprise wide commitment or minimum seat count. You buy licenses and online services as you need them, which makes it suitable for estates that purchase in irregular batches.

Which agreement gives a deeper discount?

The Enterprise Agreement generally discounts deeper because the price levels reward committed volume over three years. MPSA pricing tends to sit above EA pricing for the same volume, since there is no multi year commitment.

How long is an Enterprise Agreement term?

An Enterprise Agreement runs for three years. You commit to a minimum qualified seat count, set an enterprise standard for committed products, and true up additions each year across the term.

Is MPSA being retired?

Microsoft has steered new cloud purchasing toward the New Commerce Experience, but MPSA remains a valid path for many license and on premises purchases. Confirm current availability with your reseller before planning a renewal.

Should a mid sized company choose EA or MPSA?

It depends on buying pattern, not size alone. A mid sized estate with stable headcount and a standard product set may benefit from an EA, while an estate with variable demand often fits MPSA better.