Beyond EA and CSP: Understanding MPSA and Other Microsoft Licensing Programs

When most IT leaders talk about Microsoft licensing, the conversation quickly narrows to two options: the Enterprise Agreement (EA) for larger organisations, or Cloud Solution Provider (CSP) for everyone else. But that binary framing misses important nuance — and can cost organisations real money when they choose the wrong vehicle or fail to understand the strategic shifts Microsoft has engineered into its commercial licensing framework over the past three years.

This article is a practitioner's guide to the full Microsoft licensing landscape: the EA, the MPSA, the MCA, and the CSP/NCE framework. I'll explain what each programme is, when it applies, what Microsoft has changed recently, and how you can use this knowledge to negotiate better outcomes.

The Enterprise Agreement: Still the Power Negotiation Vehicle

The Enterprise Agreement remains Microsoft's primary commercial relationship with large organisations — broadly those with 500+ users (or devices). Under an EA, you commit to a three-year term covering a minimum of your current user count. In return, Microsoft historically offered volume discount tiers: Level A (baseline), B (6% off), C (9%), and D (12%).

That tiered structure no longer exists. On November 1, 2025, Microsoft eliminated Levels B, C, and D. Every new or renewed EA now starts at Level A — a flat, undiscounted list price. Whether you have 600 seats or 60,000, you begin the negotiation from the same baseline. This was a structural revenue optimisation that Microsoft executed quietly, and most organisations caught it only at their renewal when the expected discount simply wasn't there.

What hasn't changed is the True-Up mechanism. Each year on your EA anniversary, you true-up: you report actual user counts and pay the difference if you've grown. Shrinkage doesn't generate credits — it reduces next year's baseline. The True-Up is one of the most important negotiation levers you have: the timing of your growth declaration, how you classify users across SKU tiers, and whether you blend deployment data with contractual minimums all affect your True-Up cost significantly.

The EA remains the best vehicle for organisations that need maximum discounting authority, product list flexibility, and a direct Microsoft relationship. The negotiation dynamics have shifted — you need to push harder and use more external leverage to extract discounts that were once automatic — but the structure still rewards sophisticated buyers.

The MPSA: Flexible but Effectively End-of-Life for Cloud

The Microsoft Products and Services Agreement (MPSA) was designed for mid-market organisations that wanted a single contractual framework for both perpetual on-premises software and cloud services, without the three-year commitment of an EA. It offered purchasing flexibility: you could buy perpetual licences under one MPSA "pool" and cloud subscriptions under another, all under one umbrella agreement.

The MPSA still exists on paper, and organisations holding MPSA agreements can continue to purchase and maintain perpetual licences under their existing contracts. But Microsoft stopped offering new cloud workloads through MPSA in 2024. You cannot add Microsoft 365, Azure, or Dynamics 365 subscriptions to an MPSA today — those must go through MCA, CSP, or EA.

The MPSA remains relevant only in a narrow use case: organisations with significant perpetual on-premises software footprints (Windows Server, SQL Server, Office perpetual) that are not ready or willing to move those workloads to subscription. In that context, the MPSA provides a clean contractual home for perpetual licences while the organisation uses a separate vehicle for cloud.

For everyone else, the MPSA is a legacy programme. If you're in active renewal discussions and Microsoft raises MPSA as an option, treat it as a signal that they are trying to avoid an EA negotiation — which typically means more leverage for them, less for you.

The Microsoft Customer Agreement: Microsoft's Preferred Future

The Microsoft Customer Agreement (MCA) is Microsoft's preferred commercial vehicle for the modern era. Unlike the EA — which requires negotiation, custom pricing, and Microsoft field involvement — the MCA is a standard, non-negotiable online contract. There is no Microsoft account team required, no custom terms, and no multi-year negotiation cycle.

This is precisely why Microsoft is pushing customers toward it. The MCA reduces Microsoft's sales cost, removes the negotiation dynamic entirely, and locks customers into list pricing by default. When you buy through the MCA, you pay what the price list says, full stop.

The MCA is most commonly encountered through two channels. First, as the underlying contract for direct Azure consumption via the Azure portal — most organisations that "just go to Azure" are operating under an MCA. Second, as the framework for some enterprise agreements executed through Microsoft's direct commerce experience, where the EA terms sit on top of the MCA standard terms.

What MCA Means for Negotiation

The fundamental issue with the MCA from a procurement standpoint is that there is nothing to negotiate. The contract is standard; the pricing is list. The only lever available is whether you move to an EA (which requires meeting Microsoft's commercial thresholds and committing to a three-year term) or whether you use an intermediary — a CSP partner or an authorised reseller — who may be able to offer additional commercial terms.

Microsoft's push toward MCA is part of a broader strategy to reduce buyer leverage. The elimination of EA volume discount tiers in November 2025, the shift of mid-market customers to NCE/CSP, and the gradual sunsetting of MPSA for cloud all serve the same purpose: reducing the surface area over which buyers can extract commercial concessions.

Choosing the right agreement type is one of the highest-leverage decisions in your Microsoft commercial relationship. Our Microsoft EA advisory specialists provide independent programme selection analysis and negotiation support across EA, MCA, CSP, and MPSA — with no vendor affiliation.

CSP and the New Commerce Experience: The Mid-Market Reality

Cloud Solution Provider (CSP) is a channel programme, not a direct Microsoft agreement. Under CSP, you purchase Microsoft products through an authorised partner reseller. The partner buys from Microsoft and sells to you, adding their margin, support services, and sometimes additional commercial terms.

In 2022, Microsoft launched the New Commerce Experience (NCE) as the pricing framework for CSP. NCE introduced two subscription models: monthly (no commitment, cancel any time) and annual (twelve-month commitment). The commercial terms are strict.

• NCE monthly: List price with no discount. You pay the full Microsoft price list rate and can cancel on 30 days' notice. The flexibility premium is real — you're paying approximately 20% more per month compared to the annual equivalent.
• NCE annual: Up to 5% discount off list price. You are locked in for twelve months with no mid-term cancellations. Co-term renewals are available but must be carefully managed.
• NCE 3-year: Better discount but significant flexibility reduction. Most advisable only for stable, commodity workloads like Exchange Online-only deployments.

The CSP/NCE model works well for organisations under 300 users that do not qualify for or want an EA commitment. It also works for organisations that have standardised on a Microsoft partner for managed services and want to consolidate their procurement and support relationship.

Where CSP/NCE fails is when organisations treat it as a permanent steady-state rather than a bridge. I've seen organisations with 800 seats paying NCE monthly — effectively 20% above list price — because no one in IT leadership reviewed the commercial terms at the point of the last renewal. That is a recoverable situation, but it requires proactive action and ideally coincides with a Microsoft fiscal Q4 push (April–June) when partner and Microsoft incentives align.

Programme Comparison: Which Vehicle for Which Organisation

SKU Tiers Across All Programmes: The E7 Factor

Regardless of which licensing vehicle you use, the SKU tier decision has enormous cost implications. Microsoft 365 now has five tiers: F1, F3, E3, E5, and E7. E7 is the newest top-tier SKU, released above E5 and targeted at organisations wanting to consolidate AI, security, and compliance into a single licence.

From July 1, 2026, list prices are: E3 at $39/user/month (up from $36), E5 at $60/user/month (up from $57), and E7 at $99/user/month. The E7 value proposition from Microsoft is that it bundles what was previously sold separately: the E5 base, Microsoft 365 Copilot ($30/user/month), Agent 365 ($15/user/month), and Entra Suite ($12/user/month) — a total of $117 per user when purchased separately versus $99 as E7.

Microsoft's field teams are actively running an E5-to-E7 upsell motion at renewal. If you're currently on E5, you should expect your account team to model E7 as part of every renewal conversation. The question is whether E7 makes commercial sense for your organisation — or whether you can achieve equivalent functionality through targeted add-on purchasing at better effective rates.

One important nuance on E7: the Agent 365 component included in the bundle is a governance control plane — it manages AI agent policy, capacity, and visibility. It does not run agents. If you need to build or execute AI agents, you still require Copilot Studio or Microsoft Azure AI Foundry on top. This is a detail Microsoft's field teams often gloss over in E7 pitches, and it affects your total cost of ownership calculation significantly.

Using Licensing Programme Knowledge in Negotiations

Understanding the mechanics of each programme gives you leverage in negotiations that most buyers don't use. Here are the three most actionable angles.

1. Programme Alternatives Create Competitive Tension

If you're renewing an EA, Microsoft's field team knows that moving you to MCA or CSP/NCE is operationally straightforward. The threat of downgrading to CSP (accepting less discount in exchange for flexibility) is a credible signal that you don't need the EA relationship on Microsoft's terms. Mid-market organisations (500–2,000 seats) have successfully used this to extract incremental EA discounts of 5–8 percentage points above opening offer.

2. Q4 Is the Leverage Window

Microsoft's fiscal year ends June 30. The Q4 window — April 1 through June 30 — is when Microsoft's field teams have maximum discount authority and maximum incentive to close. Deals closed in Q4 consistently benchmark 15–20% better on effective discount than equivalent deals closed in Q1. If your renewal falls outside this window, it is worth exploring with your Microsoft account team whether an early renewal or co-term can align you to the Q4 close.

3. MPSA Customers Have Perpetual Licence Leverage

If you hold an MPSA with a substantial perpetual licence estate — Windows Server, SQL Server, or legacy Office — you have something Microsoft wants: migration to cloud. The Azure Hybrid Benefit (AHB) allows existing on-premises Windows Server and SQL Server licences with Software Assurance to be used in Azure at a significant discount (30–50% reduction in compute costs). This creates a constructive migration conversation where both parties benefit, and where your existing licence investment becomes a negotiating asset rather than a sunk cost.

Transitioning Between Licensing Vehicles

The most operationally risky moment in any Microsoft licensing relationship is the transition between vehicles. Organisations that move from MPSA to EA, or from CSP to EA, often experience a coverage gap, duplicate billing, or incorrect seat counts if the transition isn't carefully managed.

Key things to manage during a transition include: ensuring your Software Assurance or subscription expiry dates are correctly documented, confirming that Azure Reserved Instances and Savings Plans are aligned to the new contract vehicle (they often aren't automatically transferred), and verifying that your CSP partner's NCE term doesn't auto-renew at a time that conflicts with your new EA start date.

A structured transition plan — ideally drafted 90–120 days before the intended vehicle change — prevents the most common mistakes. If your organisation is currently on MPSA and evaluating an EA or MCA transition, that planning horizon is not optional; it is the minimum time required to do it cleanly.

Conclusion: Know the Map Before You Negotiate

Microsoft's licensing programmes are not interchangeable routes to the same destination. Each has a different commercial logic, a different discount profile, and a different strategic implication for your organisation's flexibility and leverage.

The EA remains the best vehicle for serious commercial negotiation, but it now requires more effort to extract the discounts that were once automatic. The MCA is convenient but commercially passive. CSP/NCE works for mid-market organisations but demands active management. And MPSA — once an elegant bridge between on-premises and cloud — is now effectively a stranded programme for anything beyond perpetual licence maintenance.

The organisations that get the best Microsoft outcomes in 2026 are those that understand these structural dynamics before they sit down at the renewal table. They know which programme serves their interests, which window to use, and what alternatives they can credibly threaten. That knowledge — not goodwill with the account team — is what drives competitive commercial outcomes.