What the Microsoft MPSA Is — and How It Differs from EA and CSP
The Microsoft Products and Services Agreement (MPSA) is a transactional volume licensing programme for organisations with 250 or more qualifying users or devices. It occupies the territory between SMB purchasing channels, which cap out at around 249 seats, and Enterprise Agreements, which require a minimum commitment of 500 seats. The MPSA allows purchasing across products and services from a single master agreement with multiple purchasing accounts — useful for organisations with decentralised procurement or subsidiary structures where a single EA entity is impractical.
The structural difference from an Enterprise Agreement is significant. Under an EA, an organisation commits to licensing a baseline technology (typically Microsoft 365 or Windows) enterprise-wide at the agreement start date, locking in a minimum seat count for three years. Under an MPSA, there is no enterprise-wide commitment. Organisations purchase licences when needed, for the users or devices they choose, without committing to broad deployment. Software Assurance — which provides upgrade rights, training vouchers, and certain cloud migration benefits — is optional under MPSA, whereas it is bundled into most EA products by default. When evaluating total cost, it is worth modelling your MPSA position against the EA vs MCA-E comparison to understand where commitment delivers value and where it does not.
CSP (Cloud Solution Provider) represents a third route, now increasingly competitive with both EA and MPSA for Online Services. CSP offers monthly or annual commitment options through Microsoft-authorised partners, with three-year CSP terms for core suites introduced in recent years to narrow the gap with EA pricing. The Microsoft Vendor Management Toolkit from Redress Compliance includes a structured comparison of EA, MPSA, and CSP total cost models across a range of organisation sizes.
Independent Microsoft Agreement Review
Redress Compliance reviews MPSA, EA, and CSP positions for enterprise clients — analysing whether the current agreement structure delivers the best commercial terms given your actual purchasing patterns.
Explore Microsoft Advisory →When MPSA Makes Sense in 2026
MPSA is not Microsoft's preferred vehicle for new enterprise customers in 2026 — the company's commercial incentives flow through EA and CSP. However, MPSA remains the right instrument in specific scenarios, and existing MPSA customers are not under immediate pressure to migrate.
Organisations between 250 and 499 users that primarily need perpetual licences
EA requires a 500-seat minimum. For organisations between 250 and 499 seats that rely on traditional perpetual licences for products like Office Professional Plus, Windows Server, or SQL Server, MPSA is the only volume licensing route available outside of CSP (which is subscription-only for most products). Perpetual licences purchased through MPSA carry the same perpetual use rights as EA-acquired licences.
Organisations with decentralised or multi-entity purchasing structures
MPSA's multiple purchasing account model supports organisations where different subsidiaries, departments, or affiliates buy licences independently under a single master commercial framework. This consolidates volume for pricing purposes without requiring a single EA agreement entity to carry the full commitment. Organisations that have grown through acquisition and carry mixed agreement histories often use MPSA as the unifying vehicle while maintaining flexibility in what each entity actually buys.
Hybrid on-premises and cloud environments with unpredictable cloud growth
MPSA supports both perpetual licences and Online Services subscriptions under the same agreement. For organisations running significant on-premises workloads alongside selective cloud adoption — and where the pace of cloud migration is difficult to project — MPSA avoids locking in an EA baseline that would be mis-sized within 12 months. This is especially relevant for SQL Server and Windows Server estates where Azure Hybrid Benefit and on-premises licensing interact. For the Azure workload side, review the Azure Hybrid Benefit optimisation guide alongside any MPSA perpetual licence review.
The Impact of Microsoft's November 2025 Pricing Changes on MPSA
From 1 November 2025, Microsoft eliminated tiered volume discount levels for Online Services under both EA and MPSA. Previously, customers received progressive discounts — Level A through D — based on total agreement value, with the largest customers receiving up to 15% off list for certain products. Under the new model, all customers pay Level A pricing for Online Services, regardless of spend volume or agreement size. This applies equally to Microsoft 365, Teams, Power Platform, and other cloud subscriptions.
The practical effect on MPSA is that one of its traditional weaknesses — its lower discount ceiling compared to large EAs — is no longer material for Online Services. An MPSA customer buying Microsoft 365 E3 now pays the same price as a large EA customer buying the same product. The remaining pricing advantage of EA lies in negotiated non-standard terms, product bundles, and Azure MACC commitments — none of which are available through MPSA.
For perpetual licence products, the November 2025 changes do not apply in the same way — perpetual pricing tiers were not formally abolished under the same mechanism. MPSA customers should verify their current pricing tier status with their reseller before concluding that list price parity exists across their full product portfolio. Book a review with Redress Compliance to map your specific product mix against current market benchmarks.
Microsoft Licence Optimisation Calculator
Model your MPSA, EA, and CSP options side by side using the Redress Compliance Microsoft Licence Optimisation Calculator — covering M365, perpetual server licences, and Azure hybrid scenarios.
Open the Calculator →Evaluating Your MPSA Position: Stay, Migrate, or Supplement
The decision to retain MPSA, migrate to EA or MCA-E, or supplement with CSP depends on three factors: your trajectory toward EA minimum thresholds, your on-premises vs cloud licensing split, and your procurement structure.
Organisations approaching the 500-seat threshold should model a full three-year EA commitment alongside their current MPSA run-rate. An EA becomes commercially superior when the organisation can genuinely commit to enterprise-wide deployment of Microsoft 365 or equivalent — and when the non-standard term negotiation, MACC credits, and Azure discounts available through EA create measurable savings versus MPSA plus ad-hoc CSP. The break-even point varies significantly by product mix. A 500-seat organisation heavily weighted toward on-premises SQL Server and Windows Server will reach EA value faster than one buying only cloud subscriptions at Level A pricing.
Organisations that are migrating primarily to Microsoft 365 and Azure should evaluate whether CSP — potentially with three-year annual commitment terms — delivers equivalent pricing with greater flexibility than MPSA. CSP partners can negotiate terms and provide support services that are unavailable through the MPSA transactional channel, and CSP three-year pricing for M365 suites now sits at parity with EA. Understanding the Microsoft 365 E3 vs E5 licensing economics is a prerequisite for this analysis, as the right suite selection significantly outweighs the agreement vehicle selection in most cases.
For existing MPSA customers with active perpetual licences, the most common mistake is migrating the full estate prematurely. Perpetual licences acquired under MPSA carry permanent use rights, and Software Assurance on those licences continues to deliver value (upgrade rights, extended security updates eligibility) until expiry. Moving to EA before SA expires forfeits that remaining SA value. Redress Compliance maps SA expiry schedules, perpetual licence inventories, and cloud migration timelines in a single analysis before recommending any agreement transition.