Why Look Beyond EA and CSP?
Most Microsoft licensing conversations centre on two programmes: the Enterprise Agreement (EA) for large organisations and the Cloud Solution Provider (CSP) for smaller or cloud-first buyers. But Microsoft's licensing landscape is far broader than these two options — and selecting the wrong programme can cost your organisation hundreds of thousands of dollars in unnecessary spend, or worse, leave you locked into a structure that does not match your purchasing patterns.
Mid-sized enterprises, organisations in transition (mergers, divestitures, rapid growth), public-sector agencies, and educational institutions all face scenarios where neither EA nor CSP is the optimal fit. Understanding the full portfolio of Microsoft licensing programmes — MPSA, MCA, EES, government agreements, and OEM licensing — gives procurement and IT leaders the ability to select the structure that aligns with their actual needs rather than defaulting to whatever Microsoft's sales team recommends.
"Microsoft's sales incentives do not always align with your organisation's best interests. Understanding the full programme portfolio gives you leverage to choose the structure that fits — not the one Microsoft wants to sell you."
This is particularly important right now because Microsoft is actively consolidating its licensing programmes. The retirement of Open License, the de-emphasis of MPSA, and the aggressive push toward the Microsoft Customer Agreement (MCA) mean that the landscape is shifting. Organisations that understand these dynamics can negotiate from a position of strength during programme transitions — rather than being caught off guard when Microsoft announces the next retirement.
MPSA: The Flexible Alternative to Enterprise Agreements
The Microsoft Products & Services Agreement (MPSA) replaced the legacy Select and Select Plus programmes and serves as Microsoft's primary transactional volume licensing vehicle. Unlike the EA — which requires a three-year, organisation-wide commitment for 500+ seats — MPSA is designed for flexibility.
| Dimension | MPSA | Enterprise Agreement |
|---|---|---|
| Contract term | Evergreen (no end date) | 3 years (fixed) |
| Minimum size | ~250 users/devices | 500+ users/devices |
| Commitment required | None — buy as needed | Organisation-wide for core products |
| Pricing model | Volume tiers (points accumulate over time) | Negotiated upfront discounts (levels A–D) |
| Discount depth | Modest — standard volume pricing | Significant — custom negotiation possible |
| Software Assurance | Optional per licence | Included by default |
| Cloud services | Limited — primarily on-premises focus | Full — M365, Azure, Dynamics bundled |
| True-up process | None — pay at time of purchase | Annual true-up (retroactive settlement) |
| Best for | Mid-size, on-prem, or transitional orgs | Large, stable, cloud-and-on-prem enterprises |
MPSA's core advantage is that it imposes no organisation-wide commitment and no fixed term. You purchase licences when you need them, in the quantities you need, and each purchase accumulates toward volume discount tiers. This makes it ideal for organisations that cannot predict their licensing needs three years in advance — whether because of pending M&A activity, rapid growth, or a strategic shift away from Microsoft products.
When MPSA Makes Sense
Below EA Threshold
Organisations with 250–499 users that need volume licensing benefits but do not qualify for a standard Enterprise Agreement. MPSA provides volume pricing without the 500-seat minimum.
Organisations in Transition
Companies facing mergers, divestitures, or strategic pivots that make a three-year commitment risky. MPSA's evergreen structure allows licensing decisions to flex with business changes.
On-Premises Focus
Enterprises that still rely heavily on perpetual server and desktop licences (Windows Server, SQL Server, Office volume) rather than cloud subscriptions. MPSA handles perpetual licensing well.
Decentralised Procurement
Multi-entity organisations where different divisions or affiliates need to purchase independently but want a single master agreement for volume consolidation and administrative simplicity.
MPSA Limitations
MPSA is not without drawbacks — and understanding them is critical for making the right programme choice.
Weak Cloud Economics
MPSA offers no Azure monetary commitments, no special M365 bundling, and no consumption-based discounts. Cloud services under MPSA are priced at or near list — making it unsuitable for cloud-heavy strategies.
Limited Negotiation Leverage
MPSA uses standardised volume pricing tiers. There is minimal room for custom discounts or one-off concessions. The discounts available through accumulated volume are modest compared to EA negotiations.
Potential Retirement
Microsoft is actively steering customers toward MCA and CSP. MPSA may be deprecated or retired in coming years — similar to the fate of Open License and Select Plus. Plan a transition path.
Manufacturing Company: MPSA to EA Transition
Situation: A 400-employee manufacturer had been on MPSA for four years, purchasing Windows Server, SQL Server, and Office 2019 licences transactionally. Annual spend averaged $320,000 at MPSA volume pricing.
What happened: After a hiring wave pushed headcount past 500, the company qualified for an Enterprise Agreement. An independent licensing review revealed that consolidating the same products under an EA — with negotiated discounts and included Software Assurance — would reduce annual spend by approximately 22 %.
The Microsoft Customer Agreement (MCA): The Future of Microsoft Licensing
The Microsoft Customer Agreement is Microsoft's next-generation purchasing framework — a simplified, digital-first agreement that Microsoft is positioning to eventually replace both MPSA and the traditional EA for many customers. Understanding the MCA is essential because it is not merely an alternative to existing programmes — it is the programme Microsoft is building its future commerce platform around.
The MCA is an evergreen, digital agreement (like MPSA) but is cloud-focused by design. It is already the default agreement for direct Azure purchases, and Microsoft is progressively expanding it to cover CSP partner transactions and, eventually, broader enterprise purchases including on-premises licensing.
| MCA Dimension | Current State (2026) | Expected Trajectory |
|---|---|---|
| Agreement type | Evergreen, digital, no expiry | Remains — standard for all new customers |
| Primary scope | Azure, M365, Dynamics 365 (cloud services) | Expanding to cover on-premises licensing |
| Purchasing channel | Direct with Microsoft, or via CSP partners | May absorb EA-style enrollments for large enterprises |
| Replaces | Open License (retired), Direct EA for some | Likely to replace MPSA; may absorb traditional EA |
| Negotiation flexibility | Limited for standard purchases; growing for enterprise tier | Microsoft developing "Enterprise MCA" for large customers |
"The MCA is not optional — it is the direction Microsoft is taking all customers. The question is not whether you will be on the MCA, but when, and whether you will have negotiated the transition on your terms or Microsoft's."
Education, Government, and Sector-Specific Programmes
Microsoft maintains tailored licensing programmes for specific sectors that offer structural advantages unavailable in commercial agreements. If your organisation qualifies, these programmes almost always deliver better economics than generic EA, CSP, or MPSA structures.
Education: Enrollment for Education Solutions (EES)
EES is the academic equivalent of an Enterprise Agreement. It uses a Full-Time Equivalent (FTE) metric — typically counting faculty and staff — and provides per-student use benefits at no additional cost. When staff are licensed, students in the institution often receive free or deeply discounted access to Microsoft 365, Office desktop apps, and Windows upgrades. EES offers one-year or three-year terms, with annual adjustment flexibility as enrolment changes. Academic pricing is substantially below commercial rates — typically 60–80 % off list.
Government: Public Sector Agreements
Government organisations can access EA variants with a lower minimum threshold (250 seats vs. 500), fixed or capped pricing structures suited to annual budget cycles, and enhanced compliance and transparency provisions. In many regions, government agencies also have access to consortium or framework agreements where multiple agencies share a master contract — pooling volume for deeper discounts and simplified procurement. Government pricing is typically 10–30 % below equivalent commercial EA rates, depending on deal size and country.
OEM and Retail: Small-Scale and Device-Tied Licensing
For very small organisations or edge cases, OEM licences (pre-installed on hardware) and retail purchases remain relevant. OEM Windows or Windows Server licences are the cheapest per-unit option but are non-transferable — tied to the device on which they were originally installed. Retail (FPP) and direct web purchases are suitable for individual licence needs but carry no volume discount. In today's landscape, most small businesses have migrated from these channels to CSP subscriptions for cloud services, using OEM only for the operating system that ships with new hardware.
Programme Selection: A Decision Framework
Choosing the right Microsoft licensing programme is a strategic decision that should be driven by your organisation's size, purchasing patterns, cloud maturity, and sector. The following framework maps common organisational profiles to the programmes that typically deliver the best outcome.
Assess Your Organisation Size and Stability
500+ stable seats → EA is usually optimal. 250–499 seats or rapidly changing headcount → MPSA or CSP. Under 250 seats → CSP (cloud) or MCA (direct). Education or government → sector-specific programme first, always.
Evaluate Your Cloud vs. On-Premises Mix
Predominantly cloud (M365, Azure, Dynamics) → EA or CSP. Predominantly on-premises (Windows Server, SQL Server, Office perpetual) → MPSA. Hybrid → Consider a split strategy: MPSA for perpetual on-prem, CSP for cloud subscriptions.
Determine Your Commitment Appetite
Willing to commit for 3 years → EA delivers the deepest discounts. Unwilling or unable to commit → MPSA (evergreen, no obligation) or CSP (month-to-month or annual). Facing M&A or restructuring → MPSA's flexibility is a material advantage.
Model the Total Cost Under Each Programme
Request pricing for your specific product mix under EA, MPSA, and CSP. Compare the three-year TCO including discounts, Software Assurance value, Azure Hybrid Benefit eligibility, and administrative overhead. The programme with the lowest TCO — factoring in flexibility value — is typically the right choice.
Plan for Microsoft's Programme Consolidation
Regardless of which programme you select today, ensure you understand the MCA trajectory and have a transition plan. Include contractual language for programme migration if Microsoft retires your current agreement mid-term.
Master Comparison: EA vs CSP vs MPSA vs MCA
| Factor | EA | CSP | MPSA | MCA |
|---|---|---|---|---|
| Best for | Large, stable enterprises | Small/dynamic orgs; cloud-first | Mid-size; on-prem focus | All sizes (emerging) |
| Minimum size | 500+ seats | No minimum | ~250 seats | No minimum |
| Term | 3 years fixed | Monthly or annual | Evergreen | Evergreen |
| Commitment | Organisation-wide | None | None | None (unless enrolled) |
| Discount depth | Highest (negotiated) | List / minimal | Moderate (volume tiers) | Growing (enterprise tier) |
| Cloud coverage | Full | Full | Limited | Full |
| On-prem licensing | Full | Limited | Full | Expanding |
| SA included | Yes | No | Optional | No (equivalent benefits via subscription) |
| Future viability | Evolving (may merge with MCA) | Stable | At risk of retirement | Microsoft's long-term platform |
Negotiation Tactics for Non-EA Programmes
Negotiating within MPSA, CSP, or sector-specific programmes requires a different approach from EA negotiations — but there are still meaningful ways to optimise costs and terms.
🎯 Non-EA Negotiation Checklist
- Consolidate MPSA purchases: Batch orders to hit higher volume tiers. Ordering 200 licences in one transaction yields better pricing than 20 orders of 10 over the same period.
- Negotiate with your reseller: MPSA and CSP transactions flow through partners. While Microsoft's list prices are fixed, partners can reduce their margin, offer free services, or provide implementation support as part of the deal.
- Leverage hybrid strategies: Use MPSA for perpetual on-prem purchases (SQL Server, Windows Server) and CSP for cloud subscriptions (M365, Azure). This captures the best economics from each programme.
- Claim sector benefits: If you qualify for education (EES) or government pricing, always use the sector-specific programme. The discounts (60–80 % for education, 10–30 % for government) far exceed anything available in commercial MPSA or CSP.
- Time purchases around fiscal year-end: Microsoft's fiscal year ends in June. Partners often have quota targets that create flexibility in Q4 (April–June). Even without EA-style negotiations, timing large MPSA or CSP purchases for this window can yield better partner pricing.
- Secure transition protections: Ask your reseller or Microsoft account team for written assurances on programme migration. If MPSA is retired, what happens to your accumulated volume tier? Can you transfer into an MCA or EA seamlessly? Get this in writing now.
Healthcare Network: Hybrid MPSA + CSP Strategy
Situation: A 350-user healthcare network needed Windows Server and SQL Server licences for on-premises clinical systems (regulatory requirement) plus Microsoft 365 E3 for all staff. The organisation was too small for an EA and was purchasing everything through a single CSP partner at list pricing.
What changed: An independent licensing review recommended splitting the estate: MPSA for the perpetual server licences (with optional Software Assurance for Azure Hybrid Benefit) and CSP for the M365 E3 subscriptions. The MPSA volume tier reduced server licence costs by 12 %, and the SA investment unlocked Azure Hybrid Benefit savings on a planned Azure migration.
"The future of Microsoft licensing is consolidation around the MCA. But the present is messy — and in messy landscapes, the organisations that understand all the options are the ones that pay least."
Common Programme Selection Mistakes
In our advisory work, we see the same programme-selection errors repeated across industries. These mistakes are not about choosing the wrong product — they are about choosing the wrong contractual vehicle for the products you need, which silently inflates costs for years.
Defaulting to EA When Too Small
Organisations with 500–700 users sometimes sign EAs because Microsoft's sales team recommends it. But at these sizes, the organisation-wide commitment requirement means licensing users who do not need premium products. MPSA or a targeted CSP approach often delivers lower total cost at this scale.
Using CSP for Perpetual Needs
CSP is subscription-oriented. Organisations that need perpetual Windows Server or SQL Server licences (common in regulated industries) should not be buying these through CSP. MPSA handles perpetual licensing far more efficiently, with volume pricing and optional Software Assurance.
Ignoring Sector-Specific Programmes
We regularly encounter educational institutions and government agencies on commercial EAs or CSP agreements when they should be on EES or government-specific contracts. The pricing difference can be 40–70 % — tens of thousands of dollars annually that are simply left on the table.
Not Planning for MCA Transition
Organisations that invest heavily in MPSA without a migration plan risk disruption when Microsoft retires the programme. Build a transition strategy now — not when Microsoft sends the retirement notice.
The single most expensive mistake is treating programme selection as an administrative decision rather than a strategic one. The difference between the right and wrong programme for a 500-user organisation can easily exceed $150,000 per year — $450,000 over a three-year term. At 2,000+ users, the delta can reach seven figures. An independent programme assessment typically pays for itself within the first quarter of the optimised agreement.
Planning for Microsoft's Programme Consolidation
Microsoft's licensing programme strategy is clear: consolidate everything under the MCA framework. The trajectory has been consistent — Open License was retired in 2022, Select Plus was replaced by MPSA, and MPSA itself is now being de-emphasised. The EA is evolving, with Microsoft introducing "new commerce experience" (NCE) terms that align EA-style purchases with MCA infrastructure.
For procurement and IT leaders, this consolidation creates both risk and opportunity. The risk is being caught unprepared when Microsoft announces the next retirement — forced into a migration on Microsoft's timeline rather than yours. The opportunity is that programme transitions are negotiation events. Every time Microsoft asks you to move from one programme to another, you have leverage to extract concessions: better pricing, extended terms, transition credits, or favourable contractual language.
🎯 Programme Transition Preparation Checklist
- Document your current programme: Which agreements are active (EA, MPSA, CSP, MCA)? When do they expire or renew? What products and volumes are covered under each?
- Identify programme dependencies: Are any products, benefits, or pricing terms specific to your current programme that would be lost in a transition (e.g., MPSA volume tier, EA Software Assurance, government pricing)?
- Model the MCA alternative: Request MCA pricing for your current product mix from your Microsoft partner. Compare the three-year TCO against your current programme to understand the financial impact of transition.
- Negotiate transition terms proactively: Do not wait for Microsoft to force the move. Approach your account team now to discuss transition options and secure commitments on pricing continuity, benefit preservation, and timeline flexibility.
- Secure contractual protections: In any new agreement, include language that addresses programme retirement: what happens to your pricing if the programme is deprecated mid-term? Can you migrate to the successor programme without penalty?