Licensing Across Programs: EA, CSP, SPLA, Open Value and OEM — The Enterprise Decision Guide

Why Choosing the Right Programme Matters

Microsoft's licensing ecosystem spans five distinct procurement routes, each carrying different commercial terms, flexibility rights, Software Assurance entitlements, and compliance obligations. Organisations that default to the programme their reseller prefers — rather than the one that fits their operational profile — routinely overspend by 20 to 35 percent or accept contractual constraints that limit their ability to optimise costs at renewal.

The five programmes are not interchangeable. An Enterprise Agreement (EA) designed for large organisations with 500 or more licensed users delivers fundamentally different economics and obligations than a Cloud Solution Provider (CSP) arrangement suited to dynamic, cloud-first environments. A Services Provider License Agreement (SPLA) built for hosted service delivery cannot substitute for Open Value's perpetual licensing rights. OEM licensing bound to specific hardware creates compliance exposures that organisations frequently fail to track when assets are decommissioned.

Understanding each programme's architecture — who it serves, what it costs, what it includes, and where it creates risk — is the prerequisite for rational Microsoft procurement strategy.

Enterprise Agreement (EA): The Large Enterprise Foundation

The Enterprise Agreement is Microsoft's flagship volume licensing programme for organisations with 500 or more qualified users or devices. Participants sign a three-year agreement and commit to licensing Microsoft products organisation-wide, with pricing locked for the agreement term and annual true-ups to account for growth.

How the EA Works

EA participants select product pools — typically Enterprise Products (M365/O365, Windows, EMS/Intune) and/or Server and Cloud Enrolment (SCE) for Azure and server products — and commit to a base quantity at contract signature. An anniversary true-up in months 12 and 24 captures any growth, and the third-year settlement reconciles the full agreement period. Participants can add products at any point but cannot remove them until renewal.

All EA licences include Software Assurance (SA), which provides upgrade rights to the latest product versions, deployment planning support, home-use rights, and access to Microsoft's technical training vouchers. For on-premises deployments still running perpetual licences, SA is the mechanism that keeps the organisation current without paying for new licences at each version release.

EA Commercial Strengths

The EA delivers its strongest value proposition for organisations with a large, stable Microsoft footprint. Pricing discounts against list are typically 15 to 30 percent at entry level and can reach 40 to 50 percent for large organisations with competitive leverage. The three-year price lock provides budget predictability that consumption-based CSP arrangements cannot match. EA also unlocks the widest range of Microsoft licensing programmes, including Azure Hybrid Benefit for cost-effective cloud migration and the ability to deploy licences on third-party cloud infrastructure under License Mobility.

EA Risk Factors

The EA creates significant risk when organisations overcommit at contract signature, lock in products they subsequently sunset, or fail to negotiate price protection clauses that limit Microsoft's ability to increase per-unit pricing at renewal. EA participants that grow through acquisition must manage complex licence reconciliation across multiple enrolments. Organisations that downsize face the EA's minimum commitment structure, which does not permit mid-term reduction.

The most common EA negotiation failure is accepting Microsoft's initial renewal proposal without independent benchmarking. Microsoft routinely presents renewal pricing at 10 to 20 percent above what comparable accounts negotiate through active commercial engagement.

Cloud Solution Provider (CSP): The Flexible Cloud Route

The Cloud Solution Provider programme allows organisations to purchase Microsoft cloud services — including Microsoft 365, Azure, Dynamics 365, and Power Platform — through accredited CSP partners on monthly or annual subscription terms. CSP was designed for cloud-first businesses that need flexibility to scale licensing up and down as requirements evolve.

CSP Commercial Structure

CSP licences are procured through a tiered reseller structure: either a Direct CSP Partner (who transacts directly with Microsoft) or an Indirect CSP Reseller (who operates through a Distributor). The final customer transacts exclusively with their CSP partner, not directly with Microsoft. Pricing, terms, and support levels vary between partners, creating meaningful variation in what organisations actually pay for the same Microsoft licences.

Monthly CSP subscriptions carry a premium of 10 to 20 percent over annual CSP commitments but provide the maximum flexibility — licences can be added or removed each month. Annual CSP subscriptions lock in seats for 12 months at reduced cost but cannot be reduced mid-term (though Microsoft introduced a mid-year seat reduction window in 2023 for some subscription types). Multi-year CSP terms introduced in 2022 now allow 1-, 2- or 3-year commitments through the CSP channel.

CSP vs EA: The Critical Difference

CSP does not include Software Assurance as a separate benefit. CSP cloud subscriptions include the right to use the current version of the service but do not provide on-premises perpetual licence rights unless explicitly purchased. Organisations with existing perpetual licences wanting to preserve those rights through an upgrade cycle cannot do so via CSP — they require Open Value or an EA with SA for that purpose.

For organisations that are fully cloud-native, have no on-premises perpetual licensing obligations, and value month-to-month flexibility over multi-year price certainty, CSP is typically the most rational route. For organisations with complex on-premises deployments, hybrid environments, or requirements for License Mobility to third-party cloud providers, EA remains the more commercially capable framework.

Services Provider License Agreement (SPLA): Hosting and Managed Services

The Services Provider License Agreement is Microsoft's programme for organisations that deliver software services to third-party customers — managed service providers, hosting companies, ISVs delivering SaaS applications built on Microsoft technology, and cloud desktop providers. SPLA allows participants to license Microsoft products on a monthly basis, paying only for what they use to serve their customers.

How SPLA Works

SPLA participants sign a three-year framework agreement with Microsoft (through a SPLA reseller) and report their monthly usage — the number of licences consumed by their customers — through a monthly use report submitted to the reseller. Billing is based on actual monthly usage at the SPLA subscriber-per-month or processor-per-month rates published in Microsoft's monthly price list.

The January 2024 SPLA template update simplified reporting: service providers now submit total licence counts per product rather than individual customer-level breakdowns (the end-customer enrolment requirement was removed). This significantly reduced administrative overhead for large SPLA participants with hundreds of customers.

SPLA Compliance Obligations

SPLA is one of Microsoft's most audited programmes. The key compliance obligations are accurate monthly use reporting, ensuring that all Microsoft products deployed in the hosted environment are licensed under SPLA (not under customer-owned licences, unless specific Licence Mobility rights apply), and maintaining records for audit purposes. Under-reporting — even inadvertent — creates material financial exposure when Microsoft conducts an SPLA audit.

Service providers using customer-owned EA or perpetual licences in their infrastructure must verify that their customers hold active Software Assurance with Licence Mobility rights. Absence of active SA voids the Licence Mobility rights and creates an unlicensed deployment in the SPLA environment.

Open Value: Volume Licensing for Mid-Market Organisations

Open Value is Microsoft's volume licensing programme for organisations with 5 to 500 users — too small for the Enterprise Agreement minimum commitment but wanting the benefits of volume pricing, Software Assurance, and perpetual licence ownership that CSP's pure subscription model does not provide.

Open Value Structure

Open Value agreements run for three years, with costs spread across three annual payments. At the end of the three-year term, participants own the perpetual licence for the products they licensed. Software Assurance is included throughout the term, providing upgrade rights to the latest product versions during the agreement period. The Open Value Subscription variant (OVS) follows the same structure but does not provide perpetual licence ownership — licences expire at the end of the term, similar to a subscription model.

Unlike the original Open License programme (retired by Microsoft in January 2022), Open Value requires a minimum commitment of 5 qualifying seats and must be purchased through a Microsoft authorised reseller, not directly from Microsoft. The retirement of Open License removed the no-minimum-commitment transactional licensing option that many SMBs relied upon, pushing smaller organisations toward CSP or Open Value depending on their on-premises versus cloud split.

Open Value vs CSP: The SMB Decision

The core Open Value versus CSP decision for SMBs turns on three questions. First, does the organisation have on-premises deployments requiring perpetual licences with Software Assurance? If yes, Open Value is the only route that provides SA outside of an EA. Second, does the organisation want full flexibility to add or remove licences monthly? If yes, CSP is more flexible. Third, does the organisation plan to deploy Microsoft workloads on third-party cloud infrastructure (AWS, GCP) requiring Licence Mobility? If yes, Open Value with active SA is required.

Microsoft has been steadily steering smaller organisations toward CSP through partner incentive structures and declining new Open License availability. Organisations should not assume that the channel's recommendation reflects their best commercial interests — independent analysis of total cost of ownership over the agreement term is essential.

OEM Licensing: Hardware-Bound Licences

OEM licences are pre-installed Microsoft licences sold by hardware manufacturers (Dell, HPE, Lenovo, Cisco UCS and others) bundled with server or desktop hardware. For Windows Server, OEM licences are commonly purchased when organisations procure new servers through their preferred hardware vendor.

OEM Licensing Restrictions

OEM licences are legally bound to the first piece of hardware on which they are installed. They cannot be transferred to a different server, cannot be used in virtual environments on other physical hosts, and expire when the associated hardware is decommissioned. This hardware binding creates three common compliance exposures. First, organisations that virtualise workloads from physical servers with OEM licences onto hypervisor clusters create unlicensed deployments if they do not retain or replace the OEM licence. Second, organisations that dispose of hardware through IT asset disposal programmes — selling or scrapping servers — lose the OEM licence permanently. Third, OEM licences do not include Software Assurance, which means organisations cannot use Azure Hybrid Benefit or Licence Mobility rights.

For server procurement, OEM Windows Server licences are typically 15 to 25 percent cheaper than volume licensing equivalents at point of purchase. However, the absence of SA, licence mobility, and transferability rights creates total cost of ownership disadvantages that the upfront saving does not justify for most enterprise environments.

When OEM Makes Sense

OEM Windows Server licences are appropriate in two specific scenarios: physical servers running a single, stable workload that will remain on that hardware for its full lifecycle without virtualisation, and environments where the hardware refresh cycle is frequent enough that the hardware binding is not a practical constraint. In both cases, the organisation must maintain accurate records of which OEM licences are assigned to which hardware, particularly through asset refresh cycles and disposal events.

Choosing Across Programmes: A Decision Framework

Most enterprise organisations use multiple Microsoft licensing programmes simultaneously. A typical configuration might use an EA for M365 and server products organisation-wide, CSP for acquired companies or subsidiaries not yet integrated into the EA, SPLA for managed service divisions hosting customer workloads, and OEM for specific hardware-bound deployments.

The Five Decision Criteria

Scale: EA requires 500+ qualified users. Open Value suits 5–500. CSP has no minimum. SPLA is for service providers. OEM is hardware-dependent. Organisations that procure under an EA when CSP or Open Value would serve their scale pay unnecessary minimum commitments.

On-Premises Perpetual Needs: Only EA and Open Value provide perpetual licences with Software Assurance. CSP provides only subscription rights. OEM provides perpetual licences without SA. SPLA provides monthly service rights only. Organisations needing perpetual ownership with upgrade rights must use EA or Open Value.

Cloud Flexibility: CSP provides the greatest month-to-month flexibility. EA provides three-year price certainty with annual true-ups. Organisations with rapidly changing cloud consumption profiles are better served by CSP than EA annual commitments.

Licence Mobility: Azure Hybrid Benefit (for cost-efficient cloud migration) and Licence Mobility to third-party clouds (AWS, GCP) require active Software Assurance. Only EA and Open Value provide SA. Organisations planning multi-cloud deployment must ensure they are licensed under a programme that enables these rights.

Commercial Leverage: EA provides the strongest basis for negotiation — price discounts, non-standard terms, and competitive positioning. CSP pricing is largely standardised through partners with limited room for deviation. Open Value has moderate negotiating latitude. SPLA pricing follows published Microsoft rate cards.

Six Common Programme Selection Mistakes

1. Defaulting to EA below the 500-seat threshold: Organisations with 200 to 400 users that are persuaded into an EA by resellers seeking commission on larger deals commit to unnecessary minimum spend. At this scale, Open Value or CSP typically delivers lower total cost with appropriate rights.

2. Using CSP without understanding SA limitations: Organisations that migrate to CSP and terminate their EA without retaining perpetual licences lose the Software Assurance rights needed for Azure Hybrid Benefit, Licence Mobility, and on-premises version upgrade rights. This creates both cost exposure and compliance risk at the point of Azure migration.

3. SPLA under-reporting: Managed service providers who do not accurately track the Microsoft products deployed in their hosted environments consistently under-report their monthly SPLA usage. Microsoft's SPLA audit programme identifies these gaps, creating retroactive licence settlements that can reach hundreds of thousands of dollars.

4. OEM licences in virtualised environments: Server hardware refreshes that consolidate OEM-licensed servers onto a hypervisor cluster create unlicensed deployments if the OEM licences are not explicitly managed through the transition. This is one of the most common sources of Microsoft audit findings.

5. Mixing programme tiers without a licence position map: Organisations using EA, CSP, and Open Value simultaneously for different entities frequently create gaps in their licence position where some deployments fall outside any active programme. A consolidated licence position map is essential for organisations with multi-programme Microsoft environments.

6. Renewing the existing programme without benchmarking: Microsoft's account teams are incentivised to renew organisations into their existing programme. Independent benchmarking of EA versus CSP versus Open Value — including the total cost of ownership over three years, SA benefits consumed, and Licence Mobility requirements — often identifies programme migration opportunities that deliver material savings.