The Microsoft Services Provider License Agreement (SPLA) allows hosting providers, SaaS companies, ISVs, and managed service providers to license Microsoft software on a monthly per-subscriber or per-core basis and deliver it as a service to their customers. It is the licensing programme that underpins every non-Azure Windows hosting environment, every third-party hosted Exchange deployment, every SaaS application running on SQL Server, and every outsourced desktop delivered on Windows Server RDS. It is also the Microsoft licensing programme with the steepest pricing trajectory, the most aggressive audit programme, and the most significant strategic pressure from Microsoft to migrate to Azure. SPLA pricing has increased annually for the past several years, with cumulative increases that have doubled or tripled the cost of key products since the programme’s earlier days. Microsoft’s strategic intent is clear: make SPLA progressively more expensive relative to Azure, incentivising providers to migrate workloads to Microsoft’s own cloud. For providers who cannot or will not migrate, understanding the current pricing, the trend direction, the audit exposure, and the available optimisation levers is essential to maintaining viable margins. This guide provides the 2026 SPLA pricing landscape, product by product, with the commercial context that determines whether SPLA remains economically sustainable for your business.
Unlike Enterprise Agreements (which lock pricing for 3 years) or perpetual licences (purchased once), SPLA operates on a monthly reporting and billing cycle. Each month, the service provider counts the number of subscribers, devices, or processor cores consuming each Microsoft product and reports that count to Microsoft (or the SPLA reseller). The provider is invoiced based on the reported quantities at the current SPLA price list rate.
The pricing structure: SPLA prices are set by Microsoft and published in the SPLA price list, which is updated periodically (typically annually, with mid-year adjustments possible). Prices are denominated per Subscriber Access Licence (SAL) per month for user-facing products, or per 2-core pack per month for server products licensed on a core basis. The provider has no ability to negotiate individual product pricing — SPLA is a take-it-or-leave-it price list programme. The only pricing flexibility comes from volume-based discount tiers and the choice of SPLA reseller (resellers may apply different margins).
Subscriber Access Licence (SAL): The SPLA equivalent of a CAL. A SAL grants one subscriber (end user or device) the right to access a specific Microsoft product hosted by the provider for one month. SALs are not transferable between subscribers and must be reported for every subscriber who accesses the hosted product during the reporting period.
Core-based licensing in SPLA: Windows Server and SQL Server in SPLA environments are licensed per physical core (same 16-core minimum per server as enterprise licensing), reported monthly. The provider reports the physical core count of every server running Windows Server or SQL Server and is billed at the per-2-core-pack monthly rate.
The following pricing reflects the 2026 SPLA price list ranges. Actual pricing varies by region, reseller, and volume tier. All prices are monthly and represent list-level guidance rather than contracted rates.
Windows Server in SPLA is licensed per 2-core pack per month, with the same Standard and Datacenter editions and the same 16-core minimum per server as enterprise licensing.
Windows Server Standard: Approximately $4–$6 per 2-core pack per month. A 16-core server costs approximately $32–$48/month for Standard Edition. Standard provides rights for 2 OSEs (virtual machines) per licence set, with stacking for additional VMs. For virtualisation hosts running more than a few VMs, the stacking cost escalates rapidly.
Windows Server Datacenter: Approximately $22–$28 per 2-core pack per month. A 16-core server costs approximately $176–$224/month for Datacenter Edition. Datacenter provides unlimited virtualisation rights — essential for hosting providers running dense VM environments. For a provider hosting 20–50 VMs per physical host, Datacenter is the only practical choice.
The hosting economics: A hosting provider with 100 physical servers averaging 32 cores each, all on Datacenter, pays approximately $35,200–$44,800/month ($422,400–$537,600/year) for Windows Server Datacenter alone. This is the baseline infrastructure licensing cost before adding SQL Server, RDS, or any application licences. See Windows Server Licensing Guide 2026 for edition selection mechanics and core-based licensing mechanics.
SQL Server is typically the most expensive SPLA line item for hosting providers and SaaS companies. It is licensed per 2-core pack per month in SPLA.
SQL Server Standard: Approximately $40–$55 per 2-core pack per month. A 16-core server costs approximately $320–$440/month. Standard is limited to 24 cores per instance and 128 GB memory.
SQL Server Enterprise: Approximately $155–$190 per 2-core pack per month. A 16-core server costs approximately $1,240–$1,520/month. Enterprise provides unlimited compute resources, Always On Availability Groups, columnstore indexes, in-memory OLTP, and other advanced features.
SQL Server cost reality: A SaaS company running 10 SQL Server Enterprise instances on 16-core servers pays approximately $12,400–$15,200/month ($148,800–$182,400/year) for SQL Server licensing alone. This single line item often exceeds the combined cost of all other SPLA products. The edition selection decision (Standard vs Enterprise) has a direct and immediate impact on margins: Enterprise costs approximately 3.5–4x more per core than Standard. Every SQL Server instance running Enterprise should have a documented requirement for Enterprise-only features. See SQL Server 2022 Licensing Guide and edition strategy guide.
RDS SALs are required for every subscriber who accesses a hosted Windows Server desktop or published application through Remote Desktop Services.
RDS SAL: Approximately $5–$8 per subscriber per month. For a hosting provider delivering virtual desktops to 1,000 subscribers, the RDS SAL cost is approximately $5,000–$8,000/month ($60,000–$96,000/year) — on top of the Windows Server core licences for the RDS hosts.
The combined VDI cost in SPLA: A provider delivering Windows Server RDS-based virtual desktops needs Windows Server Datacenter licences for the hosts plus RDS SALs for every subscriber. For 1,000 subscribers on 10 physical hosts (32 cores each), the monthly cost is approximately $3,520–$4,480 for Windows Server Datacenter + $5,000–$8,000 for RDS SALs = $8,520–$12,480/month total. This per-subscriber cost ($8.52–$12.48) must be covered by the hosting service pricing. See Azure RDS Licensing.
Exchange Server in SPLA is licensed per SAL (subscriber) per month, with Standard and Enterprise editions.
Exchange Server Standard SAL: Approximately $4–$5 per subscriber per month. Covers a single 50 GB mailbox.
Exchange Server Enterprise SAL: Approximately $9–$12 per subscriber per month. Provides a 100 GB mailbox and additional features.
The competitive pressure: Exchange Server SPLA pricing competes directly with Microsoft 365 Exchange Online, which is available at $4–$8/user/month with Microsoft managing the infrastructure. For many providers, the SPLA cost of hosting Exchange plus the infrastructure and operational costs exceeds the total cost of migrating subscribers to Exchange Online. Microsoft has intentionally structured this pricing differential to encourage migration away from provider-hosted Exchange to Microsoft 365. Providers still hosting Exchange on SPLA should evaluate whether the service remains commercially viable as SPLA Exchange pricing continues to rise.
SharePoint Server Standard SAL: Approximately $5–$7 per subscriber per month. SharePoint Server Enterprise SAL: Approximately $8–$11 per subscriber per month. Similar to Exchange, SharePoint SPLA pricing faces competitive pressure from SharePoint Online included in Microsoft 365 plans. The trend toward Microsoft 365 adoption is progressively reducing the addressable market for SPLA-hosted SharePoint.
Microsoft Office in SPLA is licensed per subscriber per month. Office Standard SAL: Approximately $12–$16 per subscriber per month. Office Professional Plus SAL: Approximately $16–$20 per subscriber per month. These rates compete directly with Microsoft 365 Business and Enterprise plans that include the same Office applications plus cloud services (Exchange Online, SharePoint Online, Teams) at comparable or lower per-user prices. The commercial case for SPLA-hosted Office is narrowing significantly.
System Center Standard: Approximately $5–$8 per 2-core pack per month. System Center Datacenter: Approximately $18–$24 per 2-core pack per month. System Center licences are required for providers using SCCM, SCOM, SCVMM, or other System Center components to manage the SPLA environment. Often overlooked in SPLA cost models.
SPLA pricing has followed a consistent upward trajectory for several years, and the 2026 landscape continues that trend.
Microsoft has implemented annual SPLA price increases of approximately 7–15% across most products in recent years, with some products experiencing even steeper increases. These increases compound: a product that increases 10% annually doubles in cost within approximately 7 years. Hosting providers that set customer pricing based on current SPLA rates without building in escalation provisions find their margins compressed with each Microsoft price increase.
The compounding effect: A SQL Server Enterprise licence that cost $120/2-core pack/month in 2020 costs approximately $155–$190 in 2026 — a 30–58% increase over 6 years. A provider with 100 SQL Server Enterprise 2-core packs has seen annual costs increase from approximately $144,000 to $186,000–$228,000 over this period. Unless hosting service pricing increased proportionally, the margin has eroded substantially.
Microsoft’s SPLA pricing strategy is not random cost inflation. It is a deliberate commercial lever designed to shift workloads from third-party hosting environments to Azure. By making SPLA progressively more expensive while holding or reducing Azure pricing, Microsoft widens the cost gap between “run it yourself on SPLA” and “run it on Azure.” The message to hosting providers is explicit: migrate your customers to Azure (where Microsoft captures the full infrastructure revenue) or continue paying increasingly expensive SPLA fees (where Microsoft captures only the licensing revenue). See navigating Microsoft’s shift to CSP.
Microsoft has introduced subscription-based SPLA options alongside the traditional perpetual-use model. Under the subscription model, the provider gains access to the latest product versions and feature updates during the subscription term, similar to Software Assurance benefits. The subscription model typically costs 10–15% more than the traditional SPLA rate but provides access to the latest SQL Server, Windows Server, and other product versions without purchasing version upgrades separately. For providers who historically delayed version upgrades to avoid re-certification costs, the subscription model simplifies version management at a premium price.
Every SPLA provider should be continuously evaluating three commercial alternatives for each workload they host:
Advantages: Full control of the infrastructure, no dependency on Azure availability or pricing changes, ability to differentiate services with custom configurations, existing operational expertise and customer relationships. Disadvantages: Rising costs (7–15% annually), aggressive audit programme, no negotiation leverage on pricing, increasing cost disadvantage relative to Azure, and Microsoft’s diminishing investment in SPLA as a programme.
Advantages: Access to Azure Hybrid Benefit (40–55% savings for Windows Server, 55%+ for SQL Server for customers who bring their own licences), Azure Reserved Instances for predictable pricing, Microsoft’s ongoing infrastructure investment, and the ability to become a Microsoft-aligned partner earning Azure consumption revenue. Disadvantages: Loss of infrastructure control, dependency on Azure pricing (which Microsoft can change), margin pressure from Azure’s transparent pricing, and the operational complexity of migrating existing customer environments. See Azure cost optimisation playbook.
The Cloud Solution Provider (CSP) programme allows providers to resell Microsoft cloud services (Microsoft 365, Azure, Dynamics 365) with a margin, rather than hosting the software themselves under SPLA. For workloads that are available as Microsoft cloud services (email via Exchange Online, collaboration via Microsoft 365, databases via Azure SQL), CSP may provide a commercially superior model: the provider earns a margin on the Microsoft subscription without bearing the infrastructure, licensing, or audit costs of SPLA. See EA vs CSP vs MCA decision guide. For more detail, see our Microsoft Customer Agreement guide.
Most providers will not make a binary SPLA-to-Azure or SPLA-to-CSP transition. The practical path is a hybrid model: migrate commodity workloads (email, collaboration, standard databases) to Microsoft cloud services via CSP, retain high-value or complex workloads on SPLA where the provider adds genuine differentiation, and use Azure for workloads where Azure Hybrid Benefit and Reserved Instances make the economics compelling. The SPLA footprint shrinks over time, concentrating on the workloads where SPLA provides a commercial or technical advantage that Azure and CSP cannot match.
SPLA has the most rigorous and frequent audit programme of any Microsoft licensing model. Microsoft audits SPLA providers more frequently and more aggressively than enterprise customers, and the financial consequences of non-compliance are proportionally larger.
In enterprise licensing, a compliance gap means the enterprise is under-licensed for its own use — the financial impact is the cost of purchasing the missing licences. In SPLA, a compliance gap means the provider has been under-reporting subscriber counts to Microsoft — which Microsoft treats as a revenue leakage issue. The remediation includes back-billing for the under-reported quantities (at current SPLA rates, not the historical rates when the under-reporting occurred), plus potential penalties and programme compliance charges.
The audit trigger: Microsoft conducts SPLA audits proactively, not just reactively. Every SPLA provider should expect periodic audits as a normal part of the programme, regardless of whether Microsoft has specific suspicion of non-compliance. The audit frequency has increased in recent years as Microsoft invests in SPLA compliance enforcement. See the SPLA audit defence guide.
Under-reported subscriber counts: The most frequent finding. The provider reports 500 subscribers for a product but the audit determines that 750 subscribers accessed it during the audit period. The delta (250 subscribers × monthly SPLA rate × months of under-reporting) generates the back-billing claim.
SQL Server edition discrepancies: The provider reports SQL Server Standard but the audit finds Enterprise Edition features enabled (Always On Availability Groups, columnstore indexes). The remediation is the difference between Enterprise and Standard pricing for the audit period — which can be substantial given Enterprise’s 3.5–4x price premium.
Windows Server core count discrepancies: The provider reports core counts based on an outdated hardware inventory. Server additions, processor upgrades, or blade server configurations that increase the physical core count create under-reporting. The audit compares the reported core count against the actual physical infrastructure.
Unlicensed products: The provider deploys a Microsoft product (System Center, SharePoint, a management tool) without including it in SPLA reporting. The audit identifies the deployment and back-bills for the entire usage period.
Incorrect licensing model: The provider uses SPLA licensing for internal use (SPLA is only for delivering services to external customers) or uses enterprise licences to host services for external customers (enterprise licences generally do not permit this). The licensing model mismatch creates a fundamental compliance issue that can be costly to remediate.
SPLA audit defence requires preparation long before the audit notice arrives. The essential elements: maintain accurate monthly reporting records with documentation supporting every reported count, implement automated subscriber counting tools that reconcile against SPLA reports, conduct quarterly self-audits comparing actual deployments against reported quantities, ensure SQL Server edition compliance by documenting which features are enabled on each instance, and maintain an accurate physical server inventory with current core counts. Engage independent SPLA audit defence when the audit notice arrives — Microsoft’s initial findings typically overstate the exposure by 20–40%, and professional audit defence consistently reduces the final settlement. See common audit findings and negotiating audit outcomes.
SQL Server is the largest SPLA cost driver for most providers. Review every SQL Server instance: is Enterprise Edition required, or would Standard suffice? Enterprise features that are deployed but not actually used (columnstore indexes enabled but never queried, Always On configured but only using 2 replicas which Standard supports) represent an immediate savings opportunity by downgrading to Standard. The per-core savings of 3.5–4x make this the highest-impact single optimisation. See SQL Server compliance pitfalls.
Run Datacenter only on hosts where the VM density justifies it. Hosts running fewer than 4–6 VMs may be cheaper on Standard (even with stacking). Hosts running 10+ VMs should be on Datacenter. This per-host analysis can reduce Windows Server SPLA costs by 10–20% for providers with mixed VM densities. See Windows Server licensing models.
Every physical core requires a monthly licence payment. Consolidating workloads onto fewer, denser hosts reduces the total core count and therefore the monthly SPLA cost. A migration from 20 servers (16 cores each, 320 total cores) to 8 servers (32 cores each, 256 total cores) reduces the core licence requirement by 20%, even though the remaining servers are individually larger.
Manual subscriber counting is the primary cause of SPLA audit findings. Implement automated tools that count subscribers, map them to SPLA products, and generate monthly reports. The automation investment pays for itself by preventing the first audit back-billing event. Accurate reporting also ensures you are not over-reporting (paying for more subscribers than actually access the service), which is equally wasteful though less painful than under-reporting.
SPLA prices increase annually. Customer contracts that lock service pricing for multi-year terms without escalation provisions create a margin squeeze every time Microsoft increases SPLA rates. Include annual price adjustment clauses in hosting agreements that allow pass-through of Microsoft licensing cost increases. A typical clause: “Service pricing may be adjusted annually by up to [X]% to reflect changes in underlying software licensing costs, with 60 days’ notice.”
Compare the subscription SPLA rate (higher monthly cost, automatic version upgrades) against the traditional SPLA rate (lower monthly cost, version upgrades require separate action). If you typically upgrade to new product versions within 1–2 years of release, the subscription model’s 10–15% premium may be justified by the avoided upgrade cost and complexity. If you run stable versions for 3–5 years, the traditional model is cheaper.
Identify workloads where SPLA hosting no longer provides a commercial advantage over Microsoft cloud alternatives. Hosted Exchange competes with Exchange Online at comparable or lower per-user pricing. Hosted SharePoint competes with SharePoint Online. Hosted Office competes with Microsoft 365. For each of these commoditised services, evaluate whether transitioning customers to Microsoft 365 via CSP (earning a reseller margin) generates better economics than continuing to host on SPLA (bearing infrastructure, licensing, and operational costs). See navigating the shift to CSP.
For Windows Server and SQL Server workloads, Azure with Hybrid Benefit and Reserved Instances may provide lower total cost than SPLA on owned hardware — particularly when factoring in hardware depreciation, data centre costs, and operational overhead. Model the total cost of ownership for your top 10 workloads on both SPLA and Azure before making investment decisions. The on-premise to cloud migration cost estimator and the BYOL vs Azure licensing calculator can model the comparison.
SPLA is purchased through authorised SPLA resellers, not directly from Microsoft. The reseller relationship affects the effective pricing and the quality of licensing guidance:
Reseller margin variance: Different resellers apply different margins to SPLA pricing. While the variance is modest (typically 2–5%), at high volumes the difference accumulates. Providers should benchmark their current SPLA reseller pricing against at least two alternatives annually. The switch between SPLA resellers is operationally straightforward and does not affect deployed licences.
Licensing guidance quality: The quality of licensing advice from SPLA resellers varies significantly. Some resellers proactively help providers optimise their SPLA reporting and identify cost reduction opportunities. Others simply process orders. For complex SPLA environments (multi-product, multi-tenant, virtualised), working with a reseller or independent licensing advisor who understands the SPLA programme’s nuances prevents costly reporting errors and audit exposure.
Programme compliance support: SPLA resellers are contractually responsible for ensuring their SPLA partners comply with the programme terms. In practice, the depth of compliance support varies. Providers should not rely solely on the reseller for compliance assurance — independent self-auditing and professional licensing advisory provide a second layer of protection.
Providers planning their Microsoft licensing strategy for the next 3–5 years should factor in the following trajectory:
Continued annual price increases. Microsoft has shown no indication of moderating SPLA price increases. Budget for 7–15% annual increases as the baseline, with the possibility of larger increases for specific products that Microsoft is particularly motivated to migrate to Azure (Exchange and SharePoint are the most likely targets for aggressive repricing).
Progressive feature restrictions. Microsoft has historically introduced new product features and capabilities in Azure first, with SPLA versions receiving updates later or not at all. This feature gap will widen, making SPLA-hosted services progressively less competitive with Azure-native equivalents. Providers relying on feature parity between SPLA and Azure versions should plan for divergence.
Intensifying audit activity. As the SPLA provider population shrinks (with providers migrating to Azure and CSP), Microsoft’s audit focus on remaining SPLA providers intensifies. Fewer providers means more audit resources per provider. SPLA audit preparedness is not optional — it is a cost of doing business in the programme.
Potential programme restructuring. Microsoft has periodically restructured hosting licensing programmes (SPLA replaced the earlier SALI programme). A future restructuring that further limits SPLA flexibility or increases costs is consistent with Microsoft’s Azure-first strategy. Providers should avoid making multi-year infrastructure investments predicated on SPLA availability and pricing remaining stable.
“SPLA is not dying, but it is being repriced into a niche. Microsoft does not want to eliminate SPLA because it generates licensing revenue from third-party hosting. But Microsoft wants that hosting revenue to shrink relative to Azure consumption revenue. The pricing trajectory reflects this: SPLA gets 7–15% more expensive each year while Azure costs remain stable or decrease through Reserved Instances and Hybrid Benefit. For hosting providers, the commercial question is not ‘should we leave SPLA’ but ‘which workloads should leave SPLA and when.’ The answer is different for every provider, and the answer changes every year as SPLA pricing rises and Azure economics improve. The providers that thrive are the ones that make this evaluation continuously, not once.” — Fredrik Filipsson, Co-Founder, Redress Compliance
The Services Provider License Agreement (SPLA) is Microsoft’s licensing programme for hosting providers, SaaS companies, ISVs, and managed service providers that deliver Microsoft software as a service to their customers. SPLA allows providers to licence Microsoft products on a monthly per-subscriber or per-core basis, reporting and paying for the quantities consumed each month. Unlike enterprise licensing (where the customer owns the licences), SPLA licences belong to the provider and are used to deliver services to end customers.
SQL Server Standard costs approximately $40–$55 per 2-core pack per month in SPLA. SQL Server Enterprise costs approximately $155–$190 per 2-core pack per month. A 16-core server running SQL Server Enterprise costs approximately $1,240–$1,520/month. SQL Server is typically the most expensive line item in an SPLA agreement, and edition selection (Standard vs Enterprise) has the largest single impact on total SPLA cost.
Microsoft has implemented annual SPLA price increases of approximately 7–15% across most products in recent years. These increases compound, meaning a product that increases 10% annually doubles in cost within approximately 7 years. Hosting providers should build annual price escalation provisions into customer contracts to protect margins against Microsoft’s increases.
SPLA is a fixed price list programme with minimal negotiation flexibility on individual product pricing. The available levers are volume-based discount tiers (larger deployments qualify for lower per-unit pricing), reseller selection (different resellers may apply different margins), and programme-level negotiations with Microsoft for very large SPLA providers. The most effective cost reduction strategy is optimisation within the fixed pricing: right-sizing SQL Server editions, consolidating workloads, and migrating commodity services to CSP.
The answer is workload-specific. Commodity services (email, collaboration, standard databases) are often more cost-effective as Microsoft cloud services via CSP. Infrastructure workloads (Windows Server, SQL Server) may be more cost-effective on Azure with Hybrid Benefit and Reserved Instances, particularly when factoring in hardware and operational costs. Complex or differentiated workloads where the provider adds genuine value may still be most viable on SPLA. Evaluate each workload category independently and build a phased migration plan rather than making a binary decision.
Redress Compliance provides independent SPLA licensing assessments, audit defence, cost optimisation, and transition planning for hosting providers and managed service providers. We help providers reduce SPLA costs, defend against audit back-billing, and build commercially viable licensing strategies for the Azure-first era.