SPLA carries its own rules, its own metrics, and its own audit posture. The contract sits outside the EA and the buyer side moves are different. This pillar maps the framework end to end.
Microsoft SPLA carries its own rules, its own metrics, and its own audit posture. The contract sits outside the EA and the buyer side moves are different.
Microsoft SPLA is the licensing channel for hosting providers. It survives in 2026 with material structural changes from the 2018 to 2022 program reform.
This pillar maps the full SPLA framework. Metrics, reporting, audit posture, renewal mechanics, and the alternative pathways that the hyperscalers opened.
Read the related Microsoft knowledge hub and the SPLA advisory service for the wider context.
SPLA is a three year agreement signed between Microsoft and the hosting provider. The end customer is not party to the contract.
Pricing is variable, set on a price list updated by Microsoft each cycle. Volume discounts apply across the three year term.
SPLA flows through Microsoft hosting authorized distributors. The distributor handles reporting submission, invoice generation, and price list distribution.
Direct contracts with Microsoft do exist for the largest hosting providers. Distributor margin is removed but obligations remain.
SAL is the user license for hosted Microsoft services. One SAL covers one user of the hosted service per month.
Most SPLA products use SAL as the primary metric. Each named user is reported each month.
Some SPLA products use Service Provider License rather than SAL. The metric scales by infrastructure rather than user count.
Common with Exchange Server SPLA running large mailbox populations and with hosted Skype for Business deployments.
SPLA versus hyperscaler native decision matrix
| Product | Traditional SPLA fit | Azure native fit | AWS native fit |
|---|---|---|---|
| SQL Server | Dedicated hosting | Azure SQL MI | RDS for SQL Server |
| Windows Server | Dedicated VMs | Azure VMs | EC2 license included |
| Exchange Server | Hosted mailbox | Migrate to M365 | Marginal fit |
| SharePoint | Internet Sites | Migrate to SharePoint Online | Marginal fit |
| RDS / Citrix host | Strong fit | AVD | WorkSpaces |
| Dynamics 365 | Niche partners | Native Microsoft cloud | Marginal fit |
SPLA list prices are published in Microsoft Service Provider Use Rights and the price list distributed by the SPLA distributor.
Discounts apply through SPUR volume mechanics and through negotiated incentives on the three year contract.
Each SPLA holder submits a monthly usage report to the distributor. The report lists volume by product and by SKU.
Reports are due within ten days of month end in most contracts. Late submission is recorded and counts against the SPLA holder.
Internal use of SPLA software is not permitted. Some SPLA holders use SPLA for internal IT, which Microsoft treats as a breach.
Affiliate use is also restricted. Affiliates of the SPLA holder cannot consume SPLA software unless they are external paying customers.
EA customers outsourcing workloads to a hosting provider face a license decision. Bring EA licenses with mobility, or rely on the provider SPLA.
The decision depends on product, dedicated tenancy, and pricing comparison.
Workloads under 200 users typically run cheaper on provider SPLA. Workloads over 500 users typically run cheaper on customer EA licenses with mobility.
The crossover varies by product. SQL Server with Software Assurance often favors customer EA mobility. Windows Server often favors provider SPLA.
The standard hosting provider practice is quarterly SAL reconciliation against CRM customer counts. We disagree. In every SPLA audit finding we have defended in the last two years, the gap was created by a customer onboarded mid quarter whose user count crossed the SAL threshold before the next reconciliation cycle. Monthly automated reconciliation against the underlying directory or hosted application user store is the only cadence that survives an audit cleanly. Quarterly cadence is an audit trap dressed up as operational efficiency.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
SPLA is a contract you live every month. Quarterly snapshots miss the gap. Monthly cadence is the only posture that prevents the audit finding you cannot defend.
Microsoft sends a SPLA audit notification under the audit clause of the agreement. The notification names the auditor and the scope.
Common scope covers the most recent 24 months of monthly reports plus a deployment inventory.
Findings settle through back billing of unreported volume at the SPUR list rate. Penalties apply for sustained under reporting.
Negotiated settlements typically include forward reporting changes and remediation milestones.
SPLA renewal preparation begins nine months out. Last minute renewals lose the lever.
Microsoft pricing freezes typically run November to January. Use the freeze to anchor the renewal.
Many SPLA SKUs displace into Azure native licensing. SQL Server runs as Azure SQL Database. Windows Server runs as Azure VMs with included licensing.
The math depends on volume, retention period, and customer dedication.
SPLA stays relevant when the hosting provider needs control over the deployment topology, when customer dedicated tenancy is required, and when product features are not yet available in hyperscaler native form.
Many providers run a hybrid: SPLA for legacy products and dedicated workloads, hyperscaler native for new builds.
SAL licenses individual users of the hosted service. Per core SPLA licenses the underlying hardware running the product. SQL Server and SharePoint Server Internet Sites use per core. Most other products use SAL.
No. SPLA software cannot be used for internal IT or business operations of the SPLA holder. Internal use is a contract breach and a common audit finding.
SPLA pricing is variable monthly with volume tier discounts. EA pricing is fixed annual with three year true up. SPLA is typically cheaper per user but carries reporting overhead.
Microsoft 365 commercial SKUs and consumer products are not in SPLA. Specific niche products vary by quarter. Always check the active Service Provider Use Rights document.
Yes, with conditions. EA license mobility applies to authorized outsourcers, requires dedicated hardware in most cases, and applies to a specific product list. The hosting provider still needs SPLA for the underlying infrastructure.
Microsoft audits most SPLA holders on a three to four year cycle. Larger hosting providers see more frequent audits. Specific findings trigger follow up audits within twelve months.
Redress runs SPLA advisory inside the Vendor Shield subscription. Engagements cover monthly report validation, audit defense, three year renewal preparation, and hyperscaler displacement scoring.
Open with an inventory and entitlement baseline before any vendor conversation. Pull trailing twelve months of usage data, score it against contracted scope, and document the gap. The single most common reason buyers leave money on the table is opening the negotiation without a defensible baseline. The buyer side calendar starts at 270 days out, not at 60.
Microsoft renewal moves, EA framework, M365 SKU framework, Copilot framework, and buyer side moves across the full Microsoft estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
SPLA is the contract Microsoft audits hardest. The right monthly cadence prevents the finding. The wrong quarterly snapshot guarantees it.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
SPLA, EA, M365, Azure, Copilot, and SQL Server lessons from every Microsoft engagement we run.
