Microsoft SPLA Licensing for Service Providers: Complete Guide

The Microsoft Services Provider License Agreement (SPLA) is the only legitimate route for managed service providers, data centres, SaaS vendors, and hosters to deploy Microsoft software for customer benefit. Any service provider that runs Microsoft software — Windows Server, SQL Server, Exchange, RDS — for third-party customers without a SPLA is not "using their own EA" or "covered by the customer's licence." They are unlicensed, and Microsoft's SPLA audit programme actively identifies and pursues these situations.

SPLA audit liability can be significant: a data centre running 50 SQL Server Standard instances for customers without SPLA coverage faces retroactive liability of $50,000–$200,000 depending on core counts, time period, and prior knowledge. This guide covers SPLA structure, eligible products, monthly reporting requirements, audit defence, and the SPLA vs CSP decision for modern MSPs shifting to cloud delivery.

SPLA Programme Structure

SPLA is a 3-year agreement between Microsoft and an authorised distributor (Ingram Micro, TD SYNNEX, Arrow, and other Microsoft-authorised SPLA distributors), under which the service provider reports monthly usage and is billed accordingly. The service provider does not have a direct commercial relationship with Microsoft — the contract flows through the distributor. This matters for negotiation: your price concessions and commercial terms are negotiated at the distributor level, and distributor incentive structures affect pricing visibility.

SPLA Licence Models

SPLA Eligible Products: Complete Reference

Monthly Reporting: Operational Requirements

SPLA reporting is the most operationally demanding aspect of the programme. Reports are due by the 5th business day of each month for the prior month's usage. The report must declare actual usage — not minimum commitments, not estimates. Inaccurate or late reporting is the most common SPLA audit trigger.

What to Track for Accurate Reporting

For Processor/Core-based products (Windows Server, SQL Server): track every physical server and VM running the licensed product for any customer, with the core count of the physical host. The report declares physical processors or cores — not VM counts. For SAL-based products (RDS, Exchange, SharePoint): track every named subscriber who accessed the service in the reporting month. The PUR defines "subscriber" broadly — any individual who accesses the hosted service, including read-only access, constitutes a subscriber. Concurrent user tracking is specifically prohibited — you must count all active subscribers, not peak concurrent users.

The SAL miscounting trap: an MSP operating a hosted RDS environment tracking "peak concurrent users" of 50 will typically underreport by 3–5x compared to actual named subscriber count of 150–250. At $14–$22/RDS SAL/month, a 200-subscriber undercounting represents $2,800–$4,400/month of under-reporting — $33,600–$52,800/year in cumulative liability.

SPLA Audit Risk and Defence

Microsoft conducts SPLA audits through authorised audit partners (typically BDO or Deloitte) under contractual audit rights in the SPLA agreement. Audit triggers include: irregular reporting patterns (consistent round-number reports suggesting estimation rather than measurement); competitor intelligence (former employees reporting unlicensed hosting); customer complaints; and random selection under Microsoft's SPLA audit schedule.

Top SPLA Audit Findings

SPLA vs CSP: The Strategic Decision for Modern MSPs

The most significant strategic licensing question for service providers in 2026 is the balance between SPLA (on-premises and hybrid delivery) and CSP (cloud delivery via Microsoft 365, Azure). Many MSPs operate both — SPLA for legacy customer environments they continue to manage, CSP for net-new Microsoft 365 and Azure deployments.

The strategic recommendation for MSPs with significant SPLA revenue: begin transitioning customers to CSP/M365 equivalents now, while managing SPLA compliance tightly for the remaining on-premises estate. The SPLA revenue is declining structurally; the compliance risk remains constant. MSPs that over-invest in SPLA operational infrastructure to manage a declining portfolio are misallocating resources that should be building CSP managed services capability.

SPLA Price Negotiation

SPLA prices are distributor-specific and negotiable at the distributor level, not directly with Microsoft. The published Microsoft SPLA price list represents list price — distributors apply discount off this list, with typical discount ranging from 5–20% depending on volume and relationship. For MSPs with $1M+/year SPLA spend, it is reasonable to request competitive pricing from two or three SPLA distributors annually. Distributor consolidation (moving all SPLA spend to one distributor) typically unlocks an additional 3–5% discount from that distributor's margin.

Frequently Asked Questions

What is a Microsoft SPLA?

The Services Provider License Agreement allows MSPs, hosters, and SaaS vendors to host Microsoft software for customer use on a monthly consumption basis. SPLA is the only Microsoft licence type that legally permits hosting for third-party customer benefit.

What products are available under SPLA?

Windows Server, SQL Server, Exchange Server, SharePoint Server, RDS, Microsoft 365 Apps (SPLA edition), System Centre, and Dynamics 365 Business Central (on-premises). Microsoft 365 cloud services must be delivered via CSP — they are not available under SPLA.

How does SPLA monthly reporting work?

Reports are due by the 5th business day of each month for prior month usage. Declare actual usage — Processor/Core counts for server products, named subscriber counts for SAL products. Inaccurate or late reporting is the most common SPLA audit trigger.

Can an enterprise use SPLA to reduce costs?

No — SPLA is only available to service providers hosting Microsoft software for third-party customers. Enterprise internal deployment requires EA, CSP, or retail licensing. Using SPLA for internal enterprise deployment is a licensing violation with significant audit exposure.

What are the most common SPLA audit findings?

Unreported SQL Server processors/cores; RDS SAL under-reporting (counting concurrent vs named subscribers); unregistered affiliate usage; unlicensed M365 Apps for Enterprise; and Windows Server Standard VM excess beyond the 2-VM-per-licence rule.

What is the difference between SPLA Processor and SAL?

Processor licences are billed per physical processor — unlimited subscribers, simpler admin. SAL is billed per named subscriber per month — lower cost at low subscriber density, significant tracking overhead at scale. Per Core (SQL Server) is the most common model for multi-tenant SQL hosting.

How do SPLA prices compare to EA prices?

SPLA per-unit rates are typically 60–80% higher than equivalent EA perpetual licence costs amortised over 3 years. The premium reflects the monthly flexibility, hosting rights, and no upfront commitment. SPLA prices are negotiable at distributor level — request competitive quotes from multiple distributors annually for $1M+ spend.