Microsoft MPSA Licensing Guide: Everything Enterprises Need to Know in 2026

What Is the Microsoft Products and Services Agreement?

Microsoft stopped actively selling the MPSA to new enterprise customers and is now migrating existing MPSA holders toward the MCA-E — a transition that removes Software Assurance benefits and reduces the formal negotiating leverage MPSA buyers have historically enjoyed. For organisations still on MPSA, the question is not whether to review the agreement but when and how: unlike the Enterprise Agreement, the MPSA has no fixed expiry date and no mandatory deployment commitment, so the clock is defined by Microsoft's migration pressure rather than a renewal deadline.

The MPSA was introduced as a replacement for Select Plus, Microsoft's previous transactional volume licensing programme. It brought several structural improvements: a single master agreement with multiple Purchasing Accounts beneath it, support for both perpetual licences and cloud subscriptions under the same framework, and an online management portal (the Microsoft Business Center) for tracking orders, entitlements, and compliance positions.

In 2026, the MPSA remains available for commercial, government, and academic customers, though Microsoft has been de-emphasising it in favour of the Microsoft Customer Agreement (MCA-E) for enterprise clients and the Cloud Solution Provider (CSP) programme for smaller organisations. Understanding what MPSA does and does not offer is essential for organisations that are currently on MPSA and facing decisions about whether to renew, transition, or renegotiate their licensing structure.

How the MPSA Works: Core Structure and Mechanics

The Master Agreement and Purchasing Accounts

The MPSA is structured as a master agreement at the organisation level, beneath which individual Purchasing Accounts are created. A Purchasing Account is a distinct buying entity within your organisation — it could be a department, a subsidiary, a geographic region, or your entire organisation. Each Purchasing Account purchases licences independently and accumulates points toward its own price level within each product pool.

This structure gives organisations flexibility in how they manage licensing across complex corporate hierarchies. A multinational with subsidiaries in multiple countries can create separate Purchasing Accounts for each entity while still operating under a single master MPSA. The downside is administrative complexity: each Purchasing Account requires its own management and compliance tracking, and points do not automatically aggregate across accounts unless you specifically configure consolidated purchasing.

The Points System and Product Pools

Pricing under MPSA is determined by a points accumulation system within defined product pools. Microsoft assigns point values to each product licence. As you purchase licences within a product pool — the three commercial pools cover Applications, Systems, and Servers — your accumulated points determine your price level for that pool. The pricing tiers run from Level A (lowest, list price equivalent) through Level D (highest volume discount).

To maintain purchasing eligibility and access volume pricing, you must purchase a minimum of 500 points or Online Services for at least 250 users within each active product pool annually, measured on your compliance anniversary date. Organisations that fall below this threshold in a given pool lose their price level status for that pool at the next annual review.

It is important to note that from November 1, 2025, Microsoft eliminated the tiered volume discount structure for Online Services under both EA and MPSA. This means that cloud services — Microsoft 365, Dynamics 365, Power Platform, and equivalent cloud subscriptions — are now priced at Level A (list price) regardless of your MPSA point accumulation. The tiered pricing model for Online Services that previously rewarded volume buyers is gone. On-premises software licences are not affected by this change and continue to operate under the points-based tiered pricing model.

Software Assurance Under MPSA

Unlike the Enterprise Agreement, where Software Assurance was typically included by default across all licences, Software Assurance under MPSA is optional on a per-licence basis. You can choose to purchase SA on specific licences where the benefits — step-up licensing rights, deployment planning vouchers, training credits, home use programme access — justify the cost, and to forgo SA on licences where the ROI does not support it. This selective approach to SA is one of MPSA's genuine advantages over the EA model for organisations with heterogeneous licence portfolios where SA value varies significantly across product lines.

MPSA vs EA: Choosing the Right Agreement

The fundamental choice between MPSA and EA is the trade-off between flexibility and discount depth. The EA asks for a three-year organisation-wide commitment and delivers deeper pricing certainty, price lock, and automatic SA inclusion in exchange. The MPSA asks for nothing upfront and delivers flexibility to buy as needed, with optional SA, but historically delivered shallower discounts — and since November 2025, no volume discount at all on Online Services.

The elimination of Online Services volume discounts under MPSA from November 2025 significantly changes the decision calculus. The primary historical argument for MPSA over EA for cloud services — that you could build up volume without committing to a three-year term — has been neutralised. Both MPSA and EA now price Online Services at Level A by default, making the EA's price-lock benefit more valuable relative to MPSA's flexibility benefit than it was previously.

When EA Still Wins Over MPSA

The EA remains the stronger choice when your organisation has a stable, large-scale Microsoft 365 deployment and can benefit from the three-year price lock. Given that Microsoft's cloud list prices have increased 15–25% over the past three years, locking in today's price for three years delivers real budget protection that MPSA's transactional model cannot replicate. The EA also provides a structured negotiating moment — the three-year renewal — that creates leverage you can use to extract discounts that MPSA's rolling purchasing model does not generate.

When MPSA Remains the Right Choice

MPSA continues to make sense in several scenarios. Organisations with significant on-premises software requirements — Windows Server, SQL Server, System Center, legacy Office perpetual licences — where the points-based tiered pricing delivers real discounts are better served by MPSA than MCA-E for those product lines. Organisations with complex multi-entity structures where different subsidiaries have different Microsoft consumption profiles benefit from MPSA's Purchasing Account flexibility. And organisations below the EA's 500-seat threshold, or those with highly variable user counts, often find MPSA's commitment-free transactional model more appropriate than the EA's organisation-wide mandate.

MPSA vs MCA-E: The New Comparison That Matters

As Microsoft pushes enterprise customers toward MCA-E, the practical comparison for many MPSA customers is no longer EA-vs-MPSA but MPSA-vs-MCA-E. The two agreements share some characteristics — both are flexible, both lack the structured three-year commitment of the EA, and neither provides the automatic volume discounts for Online Services that both formerly offered. But there are meaningful structural differences that affect which is more appropriate for a given organisation.

Contract Structure and Flexibility

The MPSA's no-expiry structure means your agreement stays active indefinitely with no renewal decision point. This is genuinely advantageous for organisations that want stable, ongoing access to Microsoft's volume licensing catalogue without periodic renegotiation. MCA-E has a similar evergreen character but operates as a cloud-native agreement — its management tooling, billing mechanics, and product support all assume a cloud-first consumption model. Organisations with significant on-premises footprints often find MPSA's tooling and processes better suited to their environment than MCA-E's cloud-centric operational model.

Pricing Mechanics

Both MPSA and MCA-E now price Online Services at Level A by default. The difference is in how additional discounts are structured. Under MPSA, any negotiated discounts on cloud services are applied through the account management relationship and reflected in your agreement terms. Under MCA-E with NCE, discounts are built into commitment structures — annual terms get up to 5% below monthly list, and three-year terms offer deeper discounts in exchange for a longer commitment. Neither model provides automatic volume-based discounting, but MCA-E's NCE structure at least creates a defined framework for earning pricing benefits through term commitment.

Perpetual Licences

This is the clearest differentiator. MPSA supports perpetual software licence purchases — you can buy a perpetual Windows Server licence or a SQL Server perpetual licence under MPSA and own that licence indefinitely. MCA-E does not support perpetual licences — it is a subscription-only model. For organisations that maintain hybrid environments with perpetual on-premises infrastructure alongside cloud subscriptions, MPSA remains the only Microsoft volume licensing vehicle that accommodates both models under a single agreement.

The 2025–2026 Changes That Affect Every MPSA Customer

The most significant change affecting MPSA customers in recent years is the elimination of tiered volume discounts for Online Services from November 1, 2025. Previously, MPSA customers who accumulated sufficient points in the Applications product pool received progressively deeper discounts on Microsoft 365 and related cloud services. A large organisation at Level D pricing could receive approximately 13% off list price on Online Services. That is now gone — all MPSA customers pay Level A for cloud services regardless of their point accumulation.

This change has two practical implications. First, MPSA customers who were counting on volume discounts to offset Microsoft's regular price increases for cloud services need to revise their cost models. Second, it levels the pricing playing field between MPSA and MCA-E for cloud services, removing the pricing advantage that MPSA sometimes offered over the newer agreement structure. For organisations that were primarily on MPSA for the Online Services discounts, the case for transitioning to EA or MCA-E is now stronger than it was before November 2025.

Microsoft has also been actively encouraging MPSA customers — particularly those with 500 or more users — to evaluate MCA-E as an alternative. Microsoft's preferred commercial motion is to consolidate customers onto MCA-E, which provides better data on consumption patterns and higher renewal frequency (annual rather than three-year), both of which serve Microsoft's interests. MPSA customers should be aware that Microsoft's investment in MPSA tooling and programme support is declining, and that the programme is unlikely to receive significant feature development going forward.

Negotiating Under MPSA: What Buyers Can Still Achieve

Despite the structural changes, MPSA is not a fixed-price catalogue — negotiation remains possible and valuable for organisations with sufficient scale. For on-premises software, the tiered pricing model continues to operate, and buyers with large on-premises estates have negotiating leverage based on their point accumulation and commitment level. For Online Services, the elimination of automatic volume tiers does not preclude individually negotiated discounts — these require direct account management engagement and are not automatic, but they are achievable for organisations with sufficient cloud spend and commitment narrative.

Using Microsoft's Fiscal Calendar

Microsoft's fiscal year ends June 30. The Q4 window — April through June — is when Microsoft's account teams have the highest incentive and the most internal authority to approve discounts and favourable terms. MPSA customers who time their purchasing decisions, renewal discussions, or transition evaluations to coincide with Q4 consistently achieve better outcomes than those who transact outside this window. This is as true for MPSA negotiations as it is for EA renewals.

Leveraging Azure Commitments

Organisations with growing Azure consumption can use Azure Consumption Commitment (MACC) commitments to unlock Microsoft 365 and Dynamics 365 discounts in the same commercial conversation, even under MPSA. Microsoft's account teams have access to investment funding tied to MACC commitments that can be applied to offset Online Services costs. For MPSA customers with material Azure growth plans, framing that investment in MACC terms during an MPSA renewal or renegotiation discussion is one of the most effective tools available.

The M365 SKU Stack Decision

MPSA customers with Microsoft 365 subscriptions face the same SKU pressure as EA customers. Microsoft's field teams are actively promoting the E5-to-E7 migration motion across all agreement types. The M365 SKU hierarchy — E1, E3, E5, E7 — now has E7 as the top tier, with E7 bundling advanced AI capabilities (including Microsoft 365 Copilot, which otherwise costs $30 per user per month as a standalone), advanced security features, and compliance tools that E5 previously offered as separate add-ons. MPSA customers should evaluate E7 on its merits: the bundle economics depend on whether your users will actually deploy and utilise the AI and security capabilities within the agreement period. A mixed-tier approach — E7 for power users, E3 for standard users — often delivers better economics than a blanket tier upgrade.

Managing Your MPSA: Practical Considerations

The Microsoft Business Center (MBC) is the primary online portal for managing MPSA. Through MBC, you can view and manage Purchasing Accounts, access licence and Software Assurance summaries, download product keys, and track compliance positions. The portal replaced the older VLSC (Volume Licensing Service Center) for MPSA customers and is the operational backbone of ongoing MPSA management.

Compliance tracking under MPSA requires more active management than under an EA, where the annual True-Up process provides a structured reconciliation framework. Without a True-Up, MPSA organisations must maintain their own ongoing records of deployed versus entitled licences, updated as purchases are made. Organisations that allow this tracking to lapse are exposed to compliance gaps that can be costly to remediate, particularly for on-premises software where deployment counts must match licence entitlements.

The compliance anniversary date is the key annual trigger for MPSA management. On the anniversary of each Purchasing Account's compliance date, Microsoft reviews the account's point accumulation against the minimum thresholds required to maintain price level status. If the minimum (500 points per pool) is not met, the account's pricing tier resets. Proactive management of purchase timing relative to the compliance anniversary date is essential for maintaining pricing continuity.

The Future of MPSA: What to Expect

Microsoft has not announced a formal end date for the MPSA programme. It remains available and operational for new and existing customers as of 2026. However, several signals indicate that Microsoft's strategic investment in MPSA is winding down. The programme has received minimal feature updates in recent years. Microsoft's sales incentives for account teams are increasingly aligned with MCA-E transitions and NCE CSP growth, not MPSA expansion. And the November 2025 removal of tiered Online Services discounts under MPSA removed one of the programme's key commercial differentiators.

The most prudent approach for current MPSA customers is to conduct a structured evaluation of whether MPSA, EA, or MCA-E best serves their needs over the next three-to-five years, rather than assuming MPSA will remain the status quo indefinitely. For organisations with primarily cloud-based Microsoft deployments, MCA-E offers better-aligned tooling and a commercial model that Microsoft will continue to invest in. For organisations with significant on-premises infrastructure and perpetual licensing requirements, MPSA remains relevant — but those requirements should be modelled explicitly, not assumed to persist without review.

Our Microsoft licensing advisory team at Redress Compliance regularly supports MPSA customers through this evaluation. We have no commercial interest in recommending any particular agreement structure — our analysis is driven exclusively by the buyer's cost and operational requirements over the planning horizon.