The Services Provider License Agreement is the most expensive way to license Microsoft software. For hosting providers, SaaS companies, and managed service providers, it is often the only way. 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.
This guide is part of the Microsoft Knowledge Hub. For enterprise licensing, see the Microsoft Licensing Guide 2026. For SPLA audit defence, see the SPLA Audit Defence Guide. For Windows Server mechanics, see the Windows Server Licensing Guide 2026.
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 reported quantities at the current SPLA price list rate.
SPLA prices are set by Microsoft and published in the SPLA price list, updated periodically (typically annually with mid-year adjustments possible). The provider has no ability to negotiate individual product pricing. The only flexibility comes from volume-based discount tiers and choice of SPLA reseller.
The SPLA equivalent of a CAL. A SAL grants one subscriber the right to access a specific Microsoft product hosted by the provider for one month. SALs are not transferable and must be reported for every subscriber who accesses the hosted product during the reporting period.
Windows Server and SQL Server 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 and is billed at the per-2-core-pack monthly rate.
The following pricing reflects 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 Standard and Datacenter editions and the same 16-core minimum per server as enterprise licensing.
| Edition | Per 2-Core Pack/Month | 16-Core Server/Month | Virtualisation Rights |
|---|---|---|---|
| Standard | ~$4–$6 | ~$32–$48 | 2 OSEs per licence set (stacking for additional VMs). |
| Datacenter | ~$22–$28 | ~$176–$224 | Unlimited virtualisation. Essential for dense VM environments. |
The hosting economics: A 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 alone. This is the baseline infrastructure cost before SQL Server, RDS, or application licences. See Windows Server Licensing Guide 2026 and core-based licensing mechanics.
SQL Server is typically the most expensive SPLA line item for hosting providers and SaaS companies. Licensed per 2-core pack per month.
| Edition | Per 2-Core Pack/Month | 16-Core Server/Month | Key Limitations |
|---|---|---|---|
| Standard | ~$40–$55 | ~$320–$440 | Limited to 24 cores per instance and 128 GB memory. |
| Enterprise | ~$155–$190 | ~$1,240–$1,520 | Unlimited compute. Always On AG, columnstore, in-memory OLTP. |
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 alone. Enterprise costs 3.5–4x more per core than Standard. Every Enterprise instance 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.
| Product | Per Subscriber/Month | 1,000 Subscribers/Month | Annual Cost |
|---|---|---|---|
| RDS SAL | ~$5–$8 | ~$5,000–$8,000 | ~$60,000–$96,000 |
Combined VDI cost: 1,000 subscribers on 10 physical hosts (32 cores each) = ~$3,520–$4,480 Windows Server Datacenter + ~$5,000–$8,000 RDS SALs = $8,520–$12,480/month ($8.52–$12.48 per subscriber). This per-subscriber cost must be covered by hosting service pricing. See Azure RDS Licensing.
| Product | Tier | Per Subscriber or 2-Core Pack/Month | Competitive Pressure |
|---|---|---|---|
| Exchange Server | Standard SAL | ~$4–$5 | Exchange Online at $4–$8/user with Microsoft-managed infrastructure. |
| Exchange Server | Enterprise SAL | ~$9–$12 | M365 includes Exchange plus Teams, SharePoint, OneDrive. |
| SharePoint | Standard SAL | ~$5–$7 | SharePoint Online included in M365 plans. |
| SharePoint | Enterprise SAL | ~$8–$11 | Addressable market shrinking as M365 adoption grows. |
| Office | Standard SAL | ~$12–$16 | M365 Business plans at comparable or lower per-user pricing. |
| Office | Pro Plus SAL | ~$16–$20 | Commercial case for SPLA-hosted Office narrowing significantly. |
| System Center | Standard (2-core) | ~$5–$8 | Often overlooked in SPLA cost models. |
| System Center | Datacenter (2-core) | ~$18–$24 | Required for SCCM, SCOM, SCVMM management. |
Microsoft has implemented annual SPLA price increases of approximately 7–15% across most products in recent years, with some products experiencing steeper increases. These compound: a product increasing 10% annually doubles in cost within approximately 7 years.
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 ~$144,000 to $186,000–$228,000. Unless hosting service pricing increased proportionally, margins have eroded substantially.
SPLA pricing strategy is not random cost inflation. It is a deliberate commercial lever designed to shift workloads from third-party hosting 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 full infrastructure revenue) or continue paying increasingly expensive SPLA fees. See navigating the shift to CSP.
Microsoft has introduced subscription-based SPLA options alongside the traditional perpetual-use model. The subscription model costs 10–15% more than traditional SPLA rates but provides access to latest product versions and feature updates without purchasing version upgrades separately. For providers who typically upgrade within 1–2 years of release, the premium may be justified. For providers running stable versions for 3–5 years, the traditional model is cheaper. See Software Assurance benefits.
Every SPLA provider should continuously evaluate three commercial alternatives for each workload.
| Option | Advantages | Disadvantages |
|---|---|---|
| Remain on SPLA | Full infrastructure control, no Azure dependency, custom configurations, existing operational expertise and customer relationships. | Rising costs (7–15% annually), aggressive audits, no pricing negotiation leverage, increasing cost disadvantage vs Azure, Microsoft diminishing SPLA investment. |
| Migrate to Azure | Azure Hybrid Benefit (40–55% Windows Server, 55%+ SQL Server savings), Reserved Instances, Microsoft infrastructure investment, Azure consumption revenue. | Loss of infrastructure control, Azure pricing dependency, margin pressure from transparent pricing, migration complexity. |
| Transition to CSP | Resell M365, Azure, Dynamics 365 with margin. No infrastructure, licensing, or audit costs. Provider earns margin without bearing SPLA overhead. | Less differentiation, dependency on Microsoft cloud services, margin compression on commoditised products. |
The hybrid reality: Most providers will not make a binary transition. The practical path is hybrid: migrate commodity workloads (email, collaboration, standard databases) to Microsoft cloud via CSP, retain high-value or complex workloads on SPLA where the provider adds genuine differentiation, and use Azure for workloads where Hybrid Benefit and Reserved Instances make economics compelling. The SPLA footprint shrinks over time, concentrating on workloads where SPLA provides an advantage Azure and CSP cannot match. See EA vs CSP vs MCA decision guide and MCA guide.
SPLA has the most rigorous and frequent audit programme of any Microsoft licensing model. Microsoft audits SPLA providers more frequently and aggressively than enterprise customers, and the financial consequences of non-compliance are proportionally larger.
Why SPLA audits are different: In enterprise licensing, a compliance gap means the enterprise is under-licensed for its own use. In SPLA, a compliance gap means the provider has been under-reporting subscriber counts, which Microsoft treats as revenue leakage. Remediation includes back-billing at current rates (not historical rates) plus potential penalties. Every SPLA provider should expect periodic audits regardless of compliance history. Audit frequency has increased in recent years. See SPLA audit defence guide.
The most frequent finding. Provider reports 500 subscribers but audit determines 750 accessed during the period. The delta (250 subscribers × monthly rate × months) generates the back-billing claim.
Provider reports Standard but audit finds Enterprise features enabled (Always On AG, columnstore). Remediation is the Enterprise–Standard price difference for the entire audit period. 3.5–4x premium makes this extremely costly.
Core counts based on outdated hardware inventory. Server additions, processor upgrades, or blade configurations that increased physical core count create under-reporting.
Microsoft product deployed (System Center, SharePoint, management tool) without including in SPLA reporting. Audit back-bills for entire usage period.
SPLA licensing used for internal use (SPLA is only for external customers) or enterprise licences used to host services for external customers. Fundamental compliance issue.
Documentation supporting every reported count. This is your primary defence evidence.
Tools that reconcile against SPLA reports. Manual counting is the primary cause of audit findings.
Compare actual deployments against reported quantities. Catch discrepancies before Microsoft does.
Record which Enterprise features are enabled on each instance. Ensure Standard instances have no Enterprise features activated.
Current core counts for every server. Update after any hardware changes.
Microsoft's initial findings typically overstate exposure by 20–40%. Professional audit defence consistently reduces the final settlement. See common audit findings and negotiating audit outcomes.
Review every instance: is Enterprise required, or would Standard suffice? Features deployed but not used (columnstore enabled but never queried, Always On with only 2 replicas Standard supports) represent immediate savings. The 3.5–4x per-core difference makes this the highest-impact single optimisation. See SQL Server compliance pitfalls.
Run Datacenter only where VM density justifies it. Hosts with fewer than 4–6 VMs may be cheaper on Standard (even with stacking). Hosts with 10+ VMs should be Datacenter. Per-host analysis can reduce costs 10–20%. See Windows Server licensing models.
Every physical core requires a monthly payment. Migrating from 20 servers (16 cores each, 320 total) to 8 servers (32 cores each, 256 total) reduces core licence requirement by 20%, even with larger individual servers.
Manual subscriber counting is the primary cause of audit findings. Automation prevents back-billing and also prevents over-reporting (paying for more subscribers than actually access the service).
SPLA prices increase annually. Contracts that lock service pricing without escalation create margin squeeze. Include clauses: "Service pricing may be adjusted annually by up to [X]% to reflect changes in underlying licensing costs, with 60 days' notice."
Subscription costs 10–15% more but includes automatic version upgrades. If you upgrade within 1–2 years, the premium may be justified. If you run stable versions for 3–5 years, traditional is cheaper.
Hosted Exchange, SharePoint, and Office compete with M365 at comparable or lower per-user pricing. Evaluate whether transitioning to CSP (earning reseller margin) generates better economics than hosting on SPLA.
Azure with Hybrid Benefit and Reserved Instances may provide lower TCO than SPLA on owned hardware, especially when factoring in depreciation, data centre costs, and operational overhead. Model your top 10 workloads. See migration cost estimator and BYOL vs Azure calculator.
Different resellers apply different margins (typically 2–5%). At high volumes the difference accumulates. Benchmark your current reseller pricing against at least two alternatives annually. Switching is operationally straightforward.
Quality varies significantly. Some resellers proactively help optimise reporting. Others simply process orders. For complex environments, work with a reseller or independent licensing advisor who understands SPLA nuances.
Resellers are contractually responsible for compliance but depth varies. Do not rely solely on the reseller. Independent self-auditing and professional advisory provide essential protection.
No indication of moderation. Budget for 7–15% annual increases as baseline, with larger increases possible for products Microsoft wants to migrate to Azure (Exchange and SharePoint most likely targets).
New features and capabilities arrive 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.
As the SPLA provider population shrinks, Microsoft's audit focus on remaining providers intensifies. Fewer providers means more audit resources per provider. SPLA audit preparedness is a cost of doing business.
Microsoft has periodically restructured hosting programmes (SPLA replaced SALI). Future restructuring that limits SPLA flexibility or increases costs is consistent with the Azure-first strategy. Avoid multi-year infrastructure investments predicated on SPLA stability.
"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 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 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 is Microsoft's licensing programme for hosting providers, SaaS companies, ISVs, and managed service providers that deliver Microsoft software as a service. SPLA allows providers to licence products on a monthly per-subscriber or per-core basis. 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. Enterprise costs approximately $155–$190 per 2-core pack per month. A 16-core server running Enterprise costs ~$1,240–$1,520/month. Edition selection (Standard vs Enterprise) has the largest single impact on total SPLA cost.
Microsoft has implemented annual increases of approximately 7–15% across most products in recent years. A product increasing 10% annually doubles within approximately 7 years. Hosting providers should build annual price escalation provisions into customer contracts to protect margins.
SPLA is a fixed price list programme with minimal negotiation flexibility. Available levers are volume-based discount tiers, reseller selection (different margins), and programme-level negotiations for very large providers. The most effective cost reduction is optimisation within fixed pricing: right-sizing SQL Server editions, consolidating workloads, and migrating commodity services to CSP.
The answer is workload-specific. Commodity services (email, collaboration) are often more cost-effective as cloud services via CSP. Infrastructure workloads may be cheaper on Azure with Hybrid Benefit and Reserved Instances. Complex or differentiated workloads may still be most viable on SPLA. Evaluate each category independently and build a phased migration plan.