Microsoft EA vs MPSA: Enterprise Agreement or Products and Services Agreement?

What Is the Microsoft Products and Services Agreement?

The Microsoft Products and Services Agreement (MPSA) is a transactional volume licensing agreement designed to provide procurement flexibility without the organisation-wide commitment of an Enterprise Agreement. Unlike the EA, the MPSA has no fixed term — once signed, the agreement remains open for ongoing licence and cloud service purchases without any expiry or renewal obligation. There are no minimum user thresholds and no requirement to license the full qualifying user population.

MPSA purchases earn points that accumulate toward volume pricing levels A through D. As cumulative purchase volume reaches higher thresholds, unit pricing improves. Software Assurance under MPSA is optional — it can be attached to individual licence purchases rather than being compulsory across all purchases as it is under the EA. This optionality is genuinely useful for organisations that do not want to pay SA on products where they derive no SA benefit value.

The MPSA was historically positioned as the right vehicle for organisations that wanted volume pricing flexibility without the three-year EA commitment. In the 2026 environment, however, a critical change has altered the MPSA's pricing advantage: from November 2025, Microsoft removed volume-based pricing tiers for online services — Microsoft 365, Office 365, Dynamics 365, and Power Platform — under both the EA and MPSA. All customers now pay Level A list price for online services regardless of volume, regardless of which agreement they use.

Enterprise Agreement: Structure and Value Proposition

The EA is a three-year contract requiring 500 or more users or devices and organisation-wide licensing coverage for included products. All licences include compulsory Software Assurance. Pricing is locked for the three-year term, and the annual True-Up mechanism reconciles any additions above the initial order quantity at the contracted price.

The EA's primary advantage in 2026 is still price certainty — locking pricing for three years provides meaningful budget protection in an environment where Microsoft has increased list prices at 8 to 25 percent in each of the past three cycles. The EA also provides the most structured negotiation framework available in Microsoft's commercial programme, with discounts negotiated against a defined baseline and SA benefits catalogued explicitly.

For M365 workloads spanning the E1, E3, E5, and E7 SKU tiers — with E7 representing the new top of the stack above E5 and bundling AI, security, and compliance capabilities previously sold as E5 add-ons — the EA's three-year price lock delivers the most predictable total cost of ownership. Microsoft's field teams are actively moving E5 customers to E7 at renewal, and the E7 negotiation is most effectively conducted within an EA framework where all workloads are negotiated together rather than piecemeal.

Key Structural Differences

Commitment Scope

The EA requires organisation-wide deployment commitment. Every qualifying user and device within the organisation must be covered by the EA licences for products included in the agreement. This creates a licence floor that can represent significant cost for products with low actual deployment rates. The MPSA has no coverage requirement — purchases are made as needed, for specific users, projects, or departments. This targeted procurement model avoids paying for licences across the full user population for products that are not universally deployed.

Software Assurance Treatment

Under the EA, Software Assurance is compulsory and applies to all licences. SA provides new version rights, deployment planning services, training vouchers, home use rights, and licence mobility rights. Organisations that actively consume SA benefits receive 10 to 15 percent additional value against the SA cost. Organisations with low SA benefit utilisation effectively pay a premium for benefits they do not use.

Under the MPSA, SA is optional per purchase. This flexibility means organisations can attach SA to licences where the benefit value justifies the cost and omit it where it does not. For a large organisation with a mixed product footprint — where some products are actively deployed and benefiting from SA, and others are legacy installations receiving no new version entitlement — MPSA's SA optionality can represent real savings.

Pricing Structure After November 2025

The November 2025 pricing change eliminated the volume tier advantage that MPSA historically provided for online services. All online services now price at Level A list price regardless of volume under both EA and MPSA, making the pricing differential between the two agreements narrower than at any previous point. EA discount negotiation, however, still applies — a well-negotiated EA can achieve 10 to 20 percent off list, whereas MPSA online services pricing under the new structure does not carry an equivalent negotiated discount framework for online services.

For on-premises perpetual software — Windows Server, SQL Server, and other server products — MPSA's point-accumulation pricing model still applies. Organisations with significant on-premises software spend that does not qualify for an EA or does not want EA-level commitment can achieve meaningful volume pricing through MPSA for on-premises products.

Term and Renewal

The EA has a defined three-year term with a formal renewal process. The renewal creates a structured opportunity to renegotiate pricing, adjust scope, and optimise the licence mix. The MPSA has no defined term — it runs indefinitely, which removes the formal renewal leverage point but also eliminates the risk of being caught in an unfavourable renewal without adequate preparation.

Who Should Use MPSA Instead of EA?

The MPSA serves specific enterprise profiles where the EA's organisation-wide commitment creates more cost than it saves. These include organisations with fragmented Microsoft deployments where different departments use different products with no universal deployment requirement. They also include organisations that want full control over SA attachment decisions product by product, particularly where certain legacy software has SA but will not be upgraded to a new version. Organisations with fewer than 500 qualifying users — and for whom EA qualification is unavailable — find MPSA a more structured option than pure transactional purchasing.

The MPSA is also appropriate as a complement to an EA for products not covered under the primary EA. Many organisations maintain both an EA for core M365 and Azure workloads and an MPSA for supplementary or departmental software purchases that do not fit within the EA scope.

Who Should Favour EA Over MPSA?

Any organisation with 500 or more users and a standardised Microsoft deployment — particularly across the M365 E-SKU stack from E1 through E7 — will typically achieve better commercial outcomes under an EA than an MPSA. The EA's three-year price lock, negotiated discounts of 10 to 20 percent off list, compulsory SA benefit entitlement, and structured True-Up mechanism collectively deliver better total cost of ownership than MPSA for organisations that deploy Microsoft broadly and consistently.

The EA's most significant advantage over MPSA remains the three-year price lock at a time of consistent Microsoft price increases. An organisation that locks pricing at the April 2026 EA signing avoids the pricing resets that will occur in 2027 and 2028 under MPSA's list price exposure. For a $5 million annual Microsoft spend, a 10 percent annual price increase protection over three years represents approximately $1.5 million in cumulative cost avoidance.

The 2026 Decision Framework

The choice between EA and MPSA in 2026 should be based on four factors. First, deployment breadth: if Microsoft products are deployed universally across the organisation, the EA's coverage requirement creates no wasted spend and the price lock, SA, and discount framework add net value. If deployment is fragmented or highly variable, MPSA's targeted procurement model reduces waste.

Second, SA benefit consumption: if your organisation actively uses deployment planning services, training vouchers, and licence mobility rights, compulsory SA under EA adds value. If SA benefits are largely unused, MPSA's optional SA model may reduce overall cost.

Third, pricing trajectory: in a rising price environment, the EA's three-year lock delivers cumulative savings versus MPSA's list price exposure. Model the three-year cost trajectory for both agreements at realistic price increase assumptions before choosing.

Fourth, negotiation capability: the EA requires a structured negotiation process to realise its discount potential. Organisations without the procurement resource or specialist support to negotiate effectively may not achieve EA discounts that justify the coverage commitment. MPSA's straightforward purchase model requires less negotiation infrastructure.