Beyond EA and CSP — MPSA and Other Microsoft Licensing Programs

Why Look Beyond EA and CSP?

Most Microsoft licensing conversations focus on the Enterprise Agreement and Cloud Solution Provider model. But a significant population of organisations — particularly mid-market companies, government entities, educational institutions, and non-profits — are better served by other programmes. Understanding the full landscape helps procurement teams avoid locking into a programme that doesn't fit their structure, growth trajectory, or governance requirements.

The Enterprise Agreement (EA) has long been positioned as the default for large organisations, but it carries minimum user thresholds, annual commitment requirements, and standardisation mandates that don't work for every buyer. Meanwhile, CSP, while flexible on cloud subscriptions, doesn't always provide the Software Assurance benefits or on-premises flexibility that some organisations need. This guide explores five alternative pathways — MPSA, MCA, EES, government programmes, and OEM/retail licensing — and when each one delivers better economics and operational fit.

MPSA: The Flexible Alternative to Enterprise Agreements

The Microsoft Products and Services Agreement (MPSA) is a transactional volume licensing programme that allows organisations to purchase perpetual licences and cloud subscriptions without the minimum user thresholds or standardisation requirements of an Enterprise Agreement. Unlike the EA's annual true-up mechanism, MPSA purchases are pay-as-you-go with no commitment to a fixed user count.

MPSA's core value proposition is simplicity and flexibility. You purchase what you need, when you need it, at a predictable per-seat or per-subscription cost. There's no annual reconciliation, no true-up, and no penalty for purchasing more than you use. This structure makes MPSA particularly attractive for organisations with:

• Uneven growth patterns across divisions or geographies
• High employee turnover or seasonal staffing fluctuations
• Heterogeneous licensing needs (some departments on cloud, others on premises)
• Limited ability to forecast user requirements 12–24 months ahead

When MPSA Makes Sense

MPSA is best suited for organisations with the following profile:

• Fewer than 500 users who don't meet EA minimums
• Companies with uneven deployment across divisions that can't standardise
• Organisations that prefer predictable per-transaction costs over EA's commitment model
• Hybrid environments where different divisions require different licence mixes
• Buyers with low forecasting confidence who want to avoid large true-up bills

One common scenario is the regional distributor or managed service provider with customer-facing licensing needs. Because your customer base changes, so does your licensing footprint. MPSA allows you to scale without being locked into a fixed annual commitment. Similarly, organisations in high-growth sectors (biotech, fintech, construction) often experience headcount volatility that makes EA terms uncomfortable.

MPSA Limitations

MPSA is not a free lunch. It comes with important trade-offs:

• Discount depth — MPSA pricing is typically 5–15% lower than retail, but 20–35% higher than EA pricing for large deployments
• No unified billing or anniversary — purchases scatter across the calendar, making budget forecasting harder
• Narrower cloud product mix — some Azure SKUs and Microsoft 365 features are only available under EA or MCA
• Software Assurance benefits differ — limited access to deployment, training, and home-use rights compared to EA
• No volume-stacking discounts — you can't bundle Office, Windows, and enterprise applications into a single incentive pool

For organisations with strong forecasting capability and stable user bases above 500 seats, EA still delivers lower total cost of ownership despite its commitment requirements.

The Microsoft Customer Agreement (MCA): The Future of Microsoft Licensing

The MCA is Microsoft's commercial framework for purchasing Microsoft 365 and Azure services through the web direct or partner channel. It replaces the traditional licensing model with a subscription-first, pay-as-you-go structure that eliminates minimum seats, annual commitments, and formal renewal events.

Unlike MPSA, which still supports perpetual on-premises licences, MCA is explicitly cloud-first. You purchase subscriptions monthly or annually with no multi-year lock-in. Pricing is transparent and published; discounts are available through partners but are narrower than EA equivalents. The trade-off is operational simplicity: you manage your consumption through the Azure portal or Microsoft 365 admin centre in real time, with auto-scaling to match demand.

Microsoft has signalled that MCA is the long-term direction for all cloud and SaaS purchasing. If you're evaluating a new licensing programme, MCA is worth serious consideration, especially if your workloads are cloud-native or you want to avoid the complexity of hybrid EA/CSP/MPSA portfolios.

Education: Enrollment for Education Solutions (EES)

EES is Microsoft's dedicated programme for academic institutions, providing institution-wide licensing at significant discounts versus commercial pricing. EES requires all qualified faculty and staff to be licensed — the "blanket" model — which simplifies compliance but requires careful headcount management.

Under EES, you pay a fixed per-qualified-user cost (typically $5–$8 per user per year for core products). All employees on that list receive licences; there's no true-up or reconciliation. The catch is definitional: Microsoft has strict rules about who counts as "qualified." Full-time faculty, staff, and permanent graduate assistants typically qualify. Adjuncts, part-time staff, and contractors often don't — and disputes over headcount definitions can create audit risk.

For universities, K–12 districts, and research institutions, EES remains the best-value licensing programme. But procurement teams must invest in headcount governance to avoid overpaying for ineligible users or triggering compliance exceptions during Microsoft audits.

Government: Public Sector Agreements

Microsoft's government agreements provide Public Sector entities with specific compliance certifications (FedRAMP, StateRAMP), sovereign cloud options, and procurement flexibility that commercial agreements don't offer.

Key differences from commercial licensing:

• Compliance certifications — Microsoft provides FedRAMP Moderate/High and StateRAMP certifications, essential for federal and state agencies
• Sovereign cloud options — some government buyers have access to dedicated data centres and restricted-access cloud environments
• Published pricing — government pricing is standardised and transparent, though incremental volume discounts are available for large deployments
• Multi-year purchase agreements — government budgets often support multi-year commitments, which can unlock additional discounts

Government procurement is highly regulated, and Microsoft's government programmes are designed to work with solicitation processes, appropriations cycles, and audit requirements unique to public sector buyers.

OEM and Retail: Small-Scale and Device-Tied Licensing

OEM licences are tied permanently to the hardware they ship with. OEM Windows 10/11 licences, for example, cannot be transferred to new hardware and are typically $40–$80 cheaper than retail equivalents. Retail licences (sold via Best Buy, Amazon, etc.) provide full transferability and come with product keys you can use across devices.

Neither provides the management, compliance, or audit protection features of volume licensing. OEM and retail licences:

• Lack Software Assurance benefits
• Don't support enterprise deployment tools
• Carry no audit indemnity or compliance assistance
• Don't qualify for volume discount incentives

For small teams under 20 people or one-off device purchases, OEM/retail is cost-effective. For any organisation with formal compliance, audit, or deployment requirements, volume licensing is essential.

Programme Selection: A Decision Framework

Choosing the right Microsoft licensing programme requires aligning programme features with four key variables: organisation size, sector, workload mix, and risk tolerance.

Organisation Size

• Below 500 users: MPSA or MCA (web direct)
• 500–2,400 users: EA or MCA (partner with discounts)
• Above 2,500 users: EA (for on-premises dominance) or hybrid EA + CSP (for cloud workloads)

Sector

• Education: EES
• Government/Public Sector: Public Sector Agreement
• Commercial/Enterprise: EA, MPSA, or MCA depending on size
• Non-profit: MPSA or EES (if eligible)

Cloud vs On-Premises Mix

• Cloud-first (Azure, Microsoft 365): MCA or CSP
• On-premises dominant (Windows Server, SQL Server): EA or MPSA
• Hybrid (both equally): EA + CSP (if large enough) or MCA (if pure cloud path acceptable)

Commitment Preference

• Predictable costs, no surprises: MPSA or multi-year MCA
• Flexibility and optionality: MCA (monthly) or CSP
• Best unit economics: EA (if forecasting confidence is high)

Master Comparison: EA vs CSP vs MPSA vs MCA

Dimension	EA	CSP	MPSA	MCA
Minimum Size	500 users	None	None	None
Commitment Term	1 or 2 years	Month to month	None	1 year or month to month
True-Up	Yes (annual)	No	No	No
Software Assurance	Full (25–29%)	Limited	Partial	None (cloud-first model)
Discount Range	20–35%	10–20%	5–15%	Published + partner discounts
Best For	Large, stable, on-premises workloads	Cloud-first, variable consumption	Mid-market, heterogeneous needs	Cloud-native, simplicity-first buyers

Negotiation Tactics for Non-EA Programmes

Negotiation leverage looks different outside the EA framework:

• MPSA pricing is influenced by total purchase volume, not committed seats — if you commit to $500K annual MPSA spend across all products, you can unlock 10–15% volume discounts on published rates
• MCA pricing through partners can be negotiated — published list prices aren't fixed; partners have margin to discount based on volume, term length, and customer profile
• Government and education discounts are published but negotiable at scale — incremental concessions are available for deployments above 5,000 users or multi-year commitments
• Bundling Azure with non-EA purchases can unlock additional discounts — Microsoft incentivises cloud adoption; combining Microsoft 365 commitments with Azure can yield 5–10% incremental discounts
• Ancillary services (deployment, training, licensing assessment) — Microsoft Sales often throw in free or discounted services (FastTrack, implementation support) to close deals outside EA

The key difference from EA negotiation is the lack of a true-up lever. You can't over-commit and rely on software assurance credits to offset excess spend. Instead, focus negotiations on total volume commitments, multi-year terms, and cloud bundling.

Common Programme Selection Mistakes

We've seen these errors repeatedly in vendor negotiations:

• Choosing EA when organisation size doesn't justify the minimum commitment — a 350-user organisation forced into EA because of historical precedent will pay 20–30% more than MPSA or MCA. Reevaluate every 2–3 years as you scale.
• Locking into MPSA when growth trajectory will cross EA threshold within 18 months — if you're hiring aggressively, model the EA breakeven point and transition timing to avoid renegotiating mid-contract
• Choosing CSP over EA when Software Assurance benefits are critical — if your organisation heavily uses Software Assurance deployment tools, training credits, or home-use rights, CSP will cost more over time despite lower monthly fees
• Failing to negotiate EES headcount definitions to avoid paying for contractors — EES blanket licensing can become expensive if your headcount definition is too broad. Negotiate definitions upfront.
• Assuming government discounts are automatic — government pricing requires a government account and proof of public sector status. Many state and local buyers miss opportunities because they're not set up for government procurement channels.

Planning for Microsoft's Programme Consolidation

Microsoft is consolidating its licensing programmes toward MCA and CSP. MPSA functionality is gradually absorbed by MCA's commercial terms. Organisations on legacy programmes should model a transition timeline:

• MPSA buyers (sub-500 users) — plan migration to MCA or CSP within 2–3 years. MCA is preferred for on-premises workloads; CSP for cloud-first buyers.
• Open Value Agreement (OVA) buyers — OVA is being phased out in favour of MCA. If you're on OVA, you're likely already receiving migration offers from Microsoft or resellers.
• EA buyers — EA remains the strategic programme for large organisations, but Microsoft is pushing EA+ (an EA variant with cloud bundling). No urgent migration, but be aware of new terms in renewal negotiations.

The strategic direction is clear: Microsoft wants all customers on subscription-first, cloud-inclusive models. MPSA perpetual licensing is increasingly out of favour. If you're evaluating a new programme, MCA is the safer long-term bet than MPSA, even if MPSA pricing looks better short-term.

FAQ: Microsoft Licensing Programmes

Optimise Your Microsoft Licensing Programme

Selecting the right licensing programme is one of the highest-impact procurement decisions you'll make. A mismatch between your organisation's size, structure, and workload mix and your licensing programme can cost 20–40% in unnecessary spending or operational friction.

Our advisory team works with procurement, IT, and finance leaders to:

• Analyse your current licensing footprint and identify programme misalignment
• Model the economics of switching programmes (EA, MPSA, MCA, CSP)
• Negotiate renewal terms that lock in savings for 2–3 years
• Build a roadmap for cloud adoption and Software Assurance optimisation

Contact us for a complimentary licensing assessment or to discuss your renewal strategy.