MPSA and the Enterprise Agreement answer different questions. One lets you buy without committing. The other trades commitment for a lower price. This guide maps each to the buying pattern it actually fits.
The Microsoft Products and Services Agreement and the Enterprise Agreement are not interchangeable. This guide sets out the commitment difference, the discount difference, the Software Assurance treatment, and which agreement fits your buying pattern in 2026.
MPSA and the EA answer different questions. MPSA answers buy now without committing. The EA answers commit volume for a lower price.
The mistake we see most is treating the choice as inertia. The right agreement follows the buying pattern, not the agreement you happen to hold.
MPSA is a single, perpetual purchasing agreement with no volume commitment and no term. The EA is a three year commitment that earns a negotiated discount level in exchange for that commitment.
You sign once, then buy as you need across affiliates and locations. The Microsoft Products and Services Agreement carries no minimum and no annual true up.
You commit a baseline of qualified users or devices for three years. The Enterprise Agreement rewards that commitment with a price level and price protection.
This is the line that decides most cases. Commitment buys discount. No commitment buys flexibility.
You owe nothing until you place an order. That protects an estate with falling or unpredictable demand.
You commit a baseline and true up annually as you grow. The commitment is what unlocks the discount level you cannot reach on MPSA.
MPSA versus EA on the dimensions buyers ask about
| Dimension | MPSA | Enterprise Agreement |
|---|---|---|
| Commitment | None | Three years |
| Discount level | Transactional | Negotiated by volume |
| Software Assurance | Optional per purchase | Bundled across term |
| Price protection | None | Held across term |
| Best buyer | Irregular, no commitment | Steady, committed volume |
Software Assurance changes the math, because it carries upgrade rights and benefits that recur every year of an EA term.
It is optional and bought per transaction. You can add it where it pays and skip it where it does not. Review the benefits on the Software Assurance overview before you decide.
It is bundled across the term. That is valuable when you upgrade often and wasteful when you sit on a static version for years.
The common advice is that the EA is the grown up choice and MPSA is a stopgap for small buyers. We disagree. In close to a third of the estates we reviewed, the buyer held an EA out of habit while demand had flattened or fallen, and the committed spend went partly unused. MPSA, paired with CSP for cloud, would have cost less and carried no idle commitment. The agreement is a tool, not a status symbol. Match it to the real buying pattern, and be willing to step down from the EA when the volume no longer earns the discount.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
An agreement is a tool, not a trophy. Hold the EA when the volume earns the discount, and step down when it does not.
The decision reduces to three questions about how you actually buy.
Steady or growing demand favors the EA. Irregular or falling demand favors MPSA paired with CSP for cloud.
If most of your spend is cloud subscriptions, neither MPSA nor the EA may be the right home. Review the CSP model and the Microsoft Customer Agreement first.
If you buy perpetual licenses without a volume commitment, MPSA remains a clean home for those transactions.
Yes. MPSA remains available as a transactional, no commitment purchasing agreement, mainly for perpetual on premises licenses. Microsoft has moved most cloud purchasing to CSP and the Microsoft Customer Agreement, which has narrowed where MPSA fits.
Commitment. MPSA has no volume commitment and no term, so you buy as needed. The EA commits a baseline for three years in exchange for a negotiated discount level and price protection.
No. MPSA prices are transactional and reset with each purchase. Only the EA holds your negotiated price level flat across the full three year term, which protects a growing estate from mid term list increases.
Software Assurance is optional and bought per transaction on MPSA. You add it where the upgrade rights and benefits pay off and skip it elsewhere. On the EA it is bundled across the whole term.
Usually not. MPSA discounts are transactional and shallower because there is no volume commitment behind them. The EA discount level is the reward for committing three years of baseline volume.
Often neither. Cloud first buyers are usually better served by CSP or the Microsoft Customer Agreement. Use MPSA mainly for perpetual on premises purchases and reserve the EA for large committed estates.
Consider it when your demand has flattened or fallen and the committed EA spend is going partly unused. If the volume no longer earns the discount, MPSA paired with CSP can cost less and carry no idle commitment.
Match the agreement to your buying pattern, not to the paper you already hold. Steady committed volume favors the EA. Irregular or falling demand favors MPSA. Always price both paths before you renew.
Microsoft renewal moves, the EA framework, the M365 SKU framework, the Copilot framework, and the buyer side moves across the full Microsoft estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
