Microsoft Licensing — Programme Comparison Guide

Licensing Across Programs
EA, CSP, SPLA, Open Value, OEM

Microsoft software — including Windows Server, SQL Server, and the broader Microsoft 365 stack — can be acquired through multiple licensing programmes, each with distinct structures, pricing models, flexibility provisions, Software Assurance eligibility, licence transferability rules, and compliance requirements. Choosing the right programme (or combination of programmes) has a direct and significant impact on total cost of ownership, operational flexibility, cloud migration options, and audit risk. This guide provides CIOs, procurement professionals, and IT asset managers with a comprehensive comparison of the five primary Microsoft licensing channels — Enterprise Agreement (EA), Cloud Solution Provider (CSP), Service Provider Licence Agreement (SPLA), Open Value, and OEM — covering programme mechanics, advantages, limitations, and practical selection criteria for each organisational scenario.

By Fredrik FilipssonMicrosoft LicensingUpdated February 2026~22 min read
📘 Part of the Microsoft Licensing Knowledge Hub. See also: CSP vs Enterprise Agreement · Microsoft Optimisation Services
EA
Enterprise Agreement — 500+ Users, 3-Year Commitment, Volume Discounts
CSP
Cloud Solution Provider — Subscription or Perpetual Through Partner
SPLA
Service Provider Licence Agreement — Monthly Rental for Hosting
OEM
Original Equipment Manufacturer — Pre-Installed, Hardware-Locked

Programme Comparison — Summary Table

The following table provides a high-level comparison of the five primary Microsoft licensing programmes, highlighting the key structural differences that affect cost, flexibility, and compliance management. Each programme is explored in detail in the subsequent sections. For a focused comparison of the two most common enterprise channels, see: CSP vs Enterprise Agreement — Pros and Cons.

FeatureEACSPSPLAOpen ValueOEM
Target audienceLarge enterprises (500+ users)All sizesService providers / hostersSMBs (5+ PCs)All (device purchase)
Term3 yearsAnnual or monthly3 years (monthly billing)3 yearsPerpetual
SA includedYes (default)Subscription includes SA-equivalent rightsNo (not applicable)Yes (included)No
Volume discounts15–30%+Partner-set (modest)Tiered by volumeModerateNone
Licence transferabilityFully transferable (90-day rule)Perpetual: transferable; Subscription: noNot transferable (rental)Transferable (90-day rule)Locked to original hardware
Azure Hybrid BenefitYes (with SA)Yes (subscription or perpetual+SA)NoYes (with SA)No
Organisations frequently use multiple programmes simultaneously — EA for core estate, CSP for flexible workloads, OEM for device procurement

Enterprise Agreement (EA) — Large Enterprise Programme

The Enterprise Agreement is Microsoft's flagship volume licensing programme for large organisations, generally requiring a minimum of 500 users or devices (though public sector and education variants may have lower thresholds). EAs are three-year commitments that typically include Software Assurance by default on all licences, providing new version rights, Azure Hybrid Benefit eligibility, training vouchers, planning services, Home Use Programme access, and other SA benefits throughout the agreement term. The EA structure provides the deepest volume discounts available through any Microsoft programme (typically 15–30% off list price, with potential for additional negotiated discounts based on volume, commitment level, and competitive leverage), price predictability through locked pricing for the three-year term, and comprehensive coverage across the full Microsoft technology stack — Windows Server, SQL Server, Microsoft 365, Azure, Dynamics 365, and other products — under a single unified agreement. For EA optimisation guidance, see: Microsoft EA Optimisation Service.

📋

Enterprise-Wide Commitment

EAs typically require organisation-wide standardisation on selected platform products. For Windows Server, this means licensing all required cores enterprise-wide through a Server and Cloud Enrolment (SCE), which simplifies compliance by ensuring complete coverage. The commitment model means the organisation pays for a baseline quantity with annual true-up cycles to report any increases. The enterprise-wide requirement can be advantageous (guaranteed coverage) or constraining (paying for licences even during downsizing periods), depending on the organisation's stability and growth trajectory.

🔄

Software Assurance Benefits

SA included in EA licences provides new version rights (automatic access to the latest Windows Server and SQL Server releases), licence mobility to Azure through Azure Hybrid Benefit, 180-day dual-use rights during cloud migration, training vouchers, planning services, and the Home Use Programme. These benefits represent significant value beyond the licence itself and are a primary reason organisations choose EA over programmes that do not include SA. The cumulative value of SA benefits over a three-year EA term can be substantial for organisations actively using Microsoft technologies.

💰

Negotiable Terms and Pricing

Large EA customers can negotiate custom terms, special pricing, and unique concessions that are not available through other programmes. Common negotiations include enhanced discounts, price protection clauses, flexibility provisions for licence count adjustments, favourable audit terms, and Azure consumption commitments with additional incentives. The negotiation opportunity is one of the EA's most significant advantages — organisations that negotiate effectively consistently achieve materially better outcomes than those that accept Microsoft's standard proposal. See: Microsoft Contract Terms and Negotiation.

📝

Licence Transferability

Volume licences acquired through an EA are fully transferable — they can be reassigned to different hardware after a 90-day assignment period, moved between organisational entities, and transferred to affiliates or as part of mergers (with Microsoft's consent). This transferability is a critical advantage over OEM licences (which are permanently locked to the original hardware) and provides the flexibility needed for infrastructure changes, data centre consolidation, and organisational restructuring throughout the agreement term and beyond.

Cloud Solution Provider (CSP) — Flexible Subscription Channel

The Cloud Solution Provider programme is Microsoft's modern licensing channel where organisations purchase both cloud subscriptions and on-premises software through a Microsoft partner on a subscription or perpetual basis. CSP has become the primary replacement for the retired Open Licence programme (which closed to new transactions in January 2022) and is now the default recommendation for organisations that do not qualify for or prefer not to commit to an Enterprise Agreement. For Windows Server and SQL Server, CSP offers both annual subscription licences (which include SA-equivalent rights automatically) and perpetual licences (which can optionally have SA added as a separate purchase).

🎯 CSP Programme — Key Characteristics

Service Provider Licence Agreement (SPLA) — Hosting and Service Providers

SPLA is a specialised licensing programme designed exclusively for service providers — organisations that host Microsoft software for third-party customers. If the organisation offers cloud hosting, SaaS, managed services, or any form of externally-facing IT services running on Microsoft infrastructure, standard volume licences cannot be used; SPLA licensing is required. Under SPLA, the service provider rents Microsoft software on a monthly basis and can use it to serve external customers, with usage reported and billed monthly based on actual deployment. For SPLA compliance guidance, see: Microsoft SPLA Audit Defence Service.

Pricing

Monthly Per-Core Billing

Windows Server and SQL Server under SPLA are licensed per physical core with monthly reporting and billing. The per-core minimums (16 cores per server for Windows Server, 4 cores per VM for SQL Server) follow the same structure as volume licensing, but the cost is charged monthly at rates that reflect the external-use rights. No CALs are required for Windows Server under SPLA — the monthly core licensing fee covers access by any number of external users, which is a significant simplification compared to volume licensing's CAL requirements.

Flexibility

Consumption-Based Scaling

SPLA's monthly reporting model allows service providers to scale licensing up and down with actual usage — adding cores when new customer workloads are deployed and reducing when workloads are decommissioned. This consumption-based approach aligns licensing costs with revenue, which is essential for service providers whose infrastructure utilisation fluctuates with customer demand. The provider reports the maximum number of cores in use during each reporting period and pays accordingly.

Ownership

No Perpetual Rights

SPLA is a rental model — the service provider never owns the licences. When the SPLA agreement ends, all rights to use the software for customer-facing services terminate. This model suits service providers whose business model is based on ongoing operational expenditure aligned with customer contract revenue, but provides no residual asset value. The three-year SPLA agreement term is renewable, and most established service providers maintain continuous SPLA coverage.

Open Value — Mid-Market Volume Licensing

Open Value is Microsoft's volume licensing programme for small and mid-sized organisations that do not meet Enterprise Agreement thresholds but want the benefits of volume licensing, particularly Software Assurance. Open Value requires a minimum of only five PCs and provides a three-year agreement with annual payments, making it accessible to organisations that are too small for an EA but want more structure and SA benefits than retail or OEM purchasing provides. Following the retirement of the Open Licence programme in January 2022, Open Value has become the primary traditional volume licensing option for organisations below the EA threshold that prefer perpetual licence ownership over the CSP subscription model.

Open Value licences for Windows Server and SQL Server include Software Assurance by default, providing new version rights, Azure Hybrid Benefit eligibility, licence mobility, training vouchers, and other SA benefits during the three-year agreement term. The programme also offers an Open Value Subscription variant where the organisation subscribes to licences rather than purchasing them outright — typically at a lower annual cost — with the option to convert to perpetual ownership at the end of the term or simply renew the subscription for another period. Compared to EA, Open Value offers less custom negotiation opportunity and slightly higher per-unit pricing, but with significantly lower commitment thresholds, less administrative complexity, and no requirement for organisation-wide standardisation. Volume licences acquired through Open Value have the same transferability rights as EA licences — they can be reassigned to different hardware after the 90-day assignment period and moved within the organisation as infrastructure requirements change. For organisations below 500 users that want SA benefits and structured volume purchasing without the complexity of an EA, Open Value remains a relevant and practical programme despite the growth of CSP as an alternative channel. For Windows Server licensing details, see: Windows Server Licensing for SAM Professionals.

OEM Licensing — Pre-Installed and Hardware-Locked

OEM (Original Equipment Manufacturer) licences are pre-installed on server hardware by the manufacturer at the factory — the most common example being Windows Server licences that come bundled with physical server hardware purchased from Dell, HPE, Lenovo, Cisco, or other server vendors. OEM licensing is the simplest and often the cheapest way to acquire Windows Server for individual physical servers, but it comes with significant limitations that affect flexibility, cloud migration options, and long-term cost management across the licence lifecycle.

The most critical limitation of OEM licences is that they are permanently locked to the original hardware on which they were installed. An OEM Windows Server licence cannot be transferred to a replacement server, moved to a virtual machine on different hardware, or applied to a cloud deployment through Azure Hybrid Benefit. When the server hardware is decommissioned, the OEM licence expires with it — there is no residual asset value. OEM licences also do not include Software Assurance, meaning the organisation has no rights to new versions, no licence mobility, no Azure Hybrid Benefit eligibility, and no SA benefits. For organisations that expect to refresh hardware, migrate to virtualised environments, or move workloads to the cloud, OEM licensing creates a structural disadvantage because every infrastructure change requires purchasing new licences rather than transferring existing ones. However, for dedicated physical servers with stable, long-term workloads that will not be moved or virtualised, OEM licensing can be cost-effective because the upfront cost is typically lower than volume licensing alternatives. For virtualisation licensing guidance, see: Windows Server Licensing in Virtualisation and Containers.

Choosing the Right Programme — Decision Framework

1

Large Enterprise (500+ Users, Stable or Growing)

The Enterprise Agreement is the natural choice for large organisations with substantial Microsoft investments. EA provides the deepest discounts, comprehensive SA benefits, negotiation flexibility, and a single agreement covering the full Microsoft stack. The three-year commitment is manageable for organisations with predictable headcount and technology requirements. Combine EA for the core stable estate with CSP for flexible or temporary workloads that do not fit the EA commitment model. See: Microsoft EA Optimisation Service.

2

Mid-Market Organisation (50–500 Users)

CSP is typically the best primary channel for mid-market organisations, offering flexibility without the EA's minimum commitment. If the organisation values Software Assurance benefits (particularly Azure Hybrid Benefit and new version rights), CSP subscription licences include SA-equivalent rights automatically. Open Value remains an alternative for organisations that prefer traditional volume purchasing with perpetual ownership and structured SA coverage. Evaluate both options based on the organisation's preference for subscription versus perpetual ownership and the importance of a direct Microsoft licensing relationship versus a partner-managed relationship.

3

Service Provider or Hosting Company

SPLA is required for any organisation hosting Microsoft software for external customers on shared infrastructure. Standard volume licences and CSP licences cannot be used for external-facing hosting services (with limited exceptions under specific outsourcing provisions). The monthly consumption model aligns licensing costs with hosting revenue and customer demand. Some providers are now also using CSP Hoster arrangements as an alternative or complement to SPLA — evaluate both options based on the specific hosting model and customer requirements.

4

Device Procurement (Individual Servers)

OEM licensing is appropriate for individual physical servers that will run stable, long-term workloads without virtualisation, cloud migration, or hardware refresh requirements. The lower upfront cost is attractive, but the hardware-lock and absence of SA benefits make OEM unsuitable for dynamic environments. For servers that may be virtualised, migrated to the cloud, or refreshed during their expected life, volume licensing (EA, CSP, or Open Value) with Software Assurance provides better long-term value despite the higher initial cost.

Using Multiple Programmes Simultaneously

Most large organisations use multiple Microsoft licensing programmes simultaneously, and Microsoft's licensing rules explicitly permit this provided the correct programme is used for each deployment scenario and each licence is tracked to its source programme. A common enterprise pattern is: EA for the core stable estate (M365 E3/E5, Windows Server Datacenter, SQL Server Enterprise with SA), CSP for flexible or temporary workloads (project-based licences, seasonal workers, test and development environments, departmental pilots), OEM for server hardware that arrives pre-licensed from the manufacturer (standalone physical servers with stable workloads), and SPLA for any subsidiary or division that provides hosting or managed services to external third-party customers. The key governance requirement when operating across multiple programmes is maintaining a centralised licence inventory that tracks which licences were acquired through which programme, their SA status, their transferability rights, and their Azure Hybrid Benefit eligibility — because all of these attributes differ by programme and cannot be assumed or generalised across the licence estate.

A licence acquired through OEM cannot be treated as a volume licence for cloud migration or hardware transfer purposes, and an SPLA licence cannot be used for the organisation's own internal workloads — confusing these programme-specific rules is one of the most common compliance findings during Microsoft audits and can result in significant remediation costs. Organisations should periodically review their programme mix to ensure it still aligns with their deployment patterns and cost objectives, ideally as part of an annual licensing governance review conducted 12–18 months before each EA renewal. Common optimisation opportunities that emerge from programme reviews include: consolidating scattered CSP and OEM purchases into an EA when the organisation reaches the 500-user threshold (capturing volume discounts and comprehensive SA benefits), moving from SPLA to CSP Hoster arrangements when the commercial terms are more favourable for the specific hosting model, and replacing OEM licences with volume licences when hardware refresh cycles create a natural opportunity to establish transferable licence positions that will support future virtualisation and cloud migration initiatives. For audit defence guidance, see: Microsoft Audit Defence Service. For contract negotiation support, see: Microsoft Contract Negotiation Service.

Compliance and Audit Risk by Programme

Each Microsoft licensing programme carries different compliance requirements and audit risk profiles, and understanding these differences is essential for organisations managing licences across multiple channels. Microsoft audits (whether conducted directly or through third-party auditors such as Deloitte or KPMG) examine licence compliance across all programmes simultaneously — the organisation cannot manage compliance in programme-specific silos. The audit will assess whether each deployment is covered by the correct programme type, whether the quantities are within entitlements, and whether programme-specific restrictions (such as OEM's hardware-lock or SPLA's external-use-only rule) have been respected.

Common Audit Findings

Programme-Specific Compliance Risks

Enterprise Agreement audits typically focus on annual true-up accuracy — whether the organisation reported the correct number of deployed licences at each true-up anniversary. Under-reporting (whether intentional or accidental) is the most common EA finding and results in retroactive licence purchases at current pricing. CSP compliance issues often arise from confusion between subscription and perpetual licences — organisations that let subscriptions lapse but continue running the software are non-compliant. OEM audit findings frequently involve licence transfers — moving an OEM licence from its original hardware to a replacement server or virtual machine violates the programme terms. SPLA audits focus on accurate monthly reporting — service providers that under-report core counts or fail to licence all customer-facing deployments face substantial back-billing and potential programme termination.

Risk mitigation: Maintain a centralised licence inventory that records the programme source for every licence, conduct quarterly internal compliance reviews, and ensure that personnel responsible for provisioning new deployments understand which programme covers which use case. For audit defence support, see: Microsoft Audit Defence Service.

Conclusion — Programme Selection as a Strategic Licensing Decision

The choice of Microsoft licensing programme is not merely an administrative procurement decision — it directly and materially affects the organisation's total cost of ownership, operational flexibility, cloud migration options, Software Assurance benefits eligibility, licence transferability, and audit compliance posture over a multi-year horizon. Enterprise Agreements provide the deepest discounts and most comprehensive SA benefits for large organisations willing to make a three-year commitment. CSP offers flexibility and accessibility for organisations of all sizes without the EA's minimum commitment requirements and with SA-equivalent rights included in subscription licences. SPLA is essential and mandatory for service providers hosting Microsoft software for external third-party customers. Open Value serves mid-market organisations wanting structured volume purchasing with full SA benefits and perpetual ownership. OEM provides the simplest and cheapest initial acquisition option for individual server hardware but permanently locks licences to that specific hardware with no transferability or SA benefits.

The organisations that achieve the best overall licensing outcomes are those that deliberately match each deployment scenario to the most appropriate programme, maintain clear centralised governance over which programme covers which deployments and licences, and periodically review their programme mix to capture optimisation opportunities as the organisation's technology landscape, headcount, and cloud strategy evolve. For organisations that need specialist guidance on programme selection, licence optimisation, multi-programme compliance governance, or Microsoft contract negotiations, independent advisory firms like Redress Compliance provide the deep licensing expertise and complete vendor-independent objectivity needed to navigate Microsoft's programme landscape and achieve the most cost-effective and fully compliant licensing posture for each organisation's specific requirements, constraints, and strategic direction.

Frequently Asked Questions

What is the minimum size for a Microsoft Enterprise Agreement?+

The standard EA threshold is 500 users or devices, though public sector variants may have lower minimums. Organisations below this threshold should consider CSP or Open Value as alternatives. The EA's volume discount benefits typically only deliver meaningful savings above the minimum threshold — organisations at exactly 500 users may find CSP competitive on a per-licence basis, while organisations significantly above 500 users capture progressively larger volume discounts through EA negotiation.

Can we transfer OEM licences to new hardware?+

No. OEM licences are permanently locked to the original hardware on which they were installed by the manufacturer. When the server hardware is decommissioned, retired, or replaced, the OEM licence expires with it and cannot be transferred to the replacement server. This is the most significant limitation of OEM licensing and the primary reason that volume licensing (EA, CSP, or Open Value) is recommended for any environment where hardware refresh, virtualisation, or cloud migration is anticipated.

Does CSP include Software Assurance?+

CSP subscription licences include rights equivalent to Software Assurance — access to the latest versions, Azure Hybrid Benefit eligibility, and other benefits — without SA being a separate line item. The subscription itself provides these rights for its duration. However, perpetual licences purchased through CSP do not include SA by default — it must be added separately if the organisation wants new version rights, Azure Hybrid Benefit, and other SA benefits on those perpetual licences.

When is SPLA required instead of standard volume licensing?+

SPLA is required whenever an organisation hosts Microsoft software for external third-party customers on shared infrastructure. Standard volume licences (EA, CSP, Open Value) are licensed for internal use by the purchasing organisation and its employees — they cannot be used to provide hosting services, SaaS, or managed services to external customers. If the organisation's business model includes any form of externally-facing services running on Microsoft infrastructure, SPLA or an equivalent hosting arrangement is required.

Can we use multiple licensing programmes simultaneously?+

Yes — most large organisations use multiple programmes concurrently. A common pattern is EA for the core stable estate, CSP for flexible or temporary workloads, OEM for pre-licensed server hardware, and SPLA for hosting divisions. The key requirement is maintaining clear governance over which programme covers which deployments, because the transferability rules, SA coverage, and Azure Hybrid Benefit eligibility differ by programme. Confusing programme-specific rules is a common audit finding.

Is Open Value still relevant with CSP available?+

Open Value remains relevant for mid-market organisations that prefer traditional perpetual licence ownership with structured Software Assurance coverage over CSP's subscription model. The choice depends on whether the organisation values perpetual ownership (Open Value advantage) or subscription flexibility (CSP advantage). Some organisations use both — Open Value for core perpetual licences with SA, and CSP for cloud subscriptions and flexible workloads. Microsoft has not announced plans to retire Open Value.

Which programme provides the best Azure Hybrid Benefit eligibility?+

EA and Open Value licences with active Software Assurance provide full Azure Hybrid Benefit eligibility, as do CSP subscription licences (which include SA-equivalent rights). Perpetual CSP licences qualify only if SA is added separately. OEM licences do not qualify for Azure Hybrid Benefit under any circumstances because they do not include SA and cannot have SA added. SPLA licences are not eligible for Azure Hybrid Benefit as they are rental licences for hosting use. For cloud migration planning, EA and CSP subscriptions offer the most straightforward path to AHB savings.

Need Help Choosing the Right Licensing Programme?

Redress Compliance provides independent advisory on Microsoft licensing programme selection, EA optimisation, CSP evaluation, SPLA compliance, licence consolidation, and contract negotiation. No Microsoft partnerships, reseller relationships, or referral arrangements.

📚 Microsoft Licensing — Programme Guides and Services

Related Resources

FF
Fredrik Filipsson

Fredrik Filipsson brings two decades of enterprise software licensing experience to every client engagement. As co-founder of Redress Compliance, he has helped hundreds of organisations navigate Microsoft licensing programme selection, EA negotiations, CSP evaluations, SPLA compliance reviews, and licence optimisation across the full Microsoft technology stack.

← Back to Microsoft Licensing Knowledge Hub