Microsoft SQL Server Hosting Licensing

Why SQL Server hosting licensing deserves its own pillar

SQL Server is the highest unit-cost Microsoft product in most enterprise hosting estates. Per-core licensing at Enterprise edition runs 10x the per-core cost of Windows Server. The compounding effect of getting SQL Server hosting licensing wrong — over-declaring AHB, mis-classifying SPLA reports, or BYOL into a listed provider without rights — produces findings two and three orders of magnitude larger than the equivalent Windows Server mistake.

Compounding the unit-cost pressure, SQL Server has the most complex per-product hosting rules in the Microsoft estate: per-edition rules differ; unlimited-virtualization rights differ; AHB stacking with hosted infrastructure differs; the listed-provider boundary applies differently to Standard vs Enterprise. A configuration that is compliant for SQL Server Standard may be non-compliant for the same workload at SQL Server Enterprise on the same host.

For the broader IaaS-licensing context this guide sits inside, see our Microsoft IaaS Licensing Guide.

The three SQL Server hosting mechanisms

Most enterprise SQL Server hosting estates use more than one mechanism in parallel — SPLA for newer or non-SA-covered workloads, BYOL for the SA-protected backbone, and increasingly Arc-PAYG for dev/test or burst workloads. The optimization conversation is which workload should be on which mechanism, not which mechanism wins in the abstract.

SPLA SQL Server: monthly core reporting

SPLA SQL Server is reported per physical core on the host (or per virtual core in some constrained configurations) on the hoster's monthly SPLA report. The mechanics:

• Per-core monthly fee. Reported per physical core of the host running SQL Server, with a minimum core count per host (typically 4 cores per processor, 8 per server) that applies even if actual usage is lower.
• Edition matters. SPLA SQL Standard and Enterprise are priced very differently per core. Enterprise SPLA is roughly 4x Standard per core.
• Virtualization treatment. SPLA SQL on a VM is typically reported per vCPU assigned to the VM, with minimum-core constraints per VM. Unlimited-virtualization rights work differently under SPLA than under BYOL with SA.
• Customer-of-record question. Under SPLA the hoster is the customer-of-record; the end customer does not need their own SQL Server entitlement.

SPLA SQL is the mechanism for customers who do not have their own SQL Server SA entitlement and are not buying one as part of the hosting engagement. It is the dominant mechanism in healthcare-ISV, financial-services-managed-hosting, and vertical SaaS contexts where the hoster's customers do not have direct Microsoft EAs.

BYOL with SA: AHB and FVB economics

BYOL with SA is the cheapest SQL hosting mechanism for customers who have it. The two channels:

AHB into Azure. For customers with SA-qualified SQL Server, Azure Hybrid Benefit allows the entitlement to flow into Azure VMs, Azure SQL Managed Instance, and Azure SQL Database without paying for SQL Server software on top of Azure compute. The savings on the SQL Server cost layer are substantial — typically 55-75% relative to PAYG SQL on Azure. For Azure SQL Managed Instance, AHB can also unlock specific tier-pricing benefits.

FVB into non-listed-provider IaaS. The 2022 Flexible Virtualization Benefit extended BYOL for SA-qualified SQL Server into non-listed-provider hosted environments under specific conditions. A customer with SA can deploy SQL Server VMs on a colo, a regional cloud, or a non-listed-provider managed-services hoster without the historic "dedicated infrastructure" requirement that pre-2022 BYOL imposed.

Both paths require the same documentation: active SA on the underlying entitlement, correct per-core mapping from entitlement to deployment, and provider-eligibility documentation. The 2026 audit pattern is AHB / FVB declarations that exceed the per-core entitlement available.

Azure Arc-enabled SQL: PAYG and managed billing

Azure Arc-enabled SQL Server is an on-premises or hosted SQL Server instance connected to Azure for centralized management, billing, and Azure-native feature delivery. Licensing options on Arc-connected instances:

• PAYG SQL Server via Azure subscription. Per-core, per-hour billing on the Azure bill, no SA required. Uniquely valuable for short-lived or burst SQL workloads where conventional core licensing is over-priced for actual hours of use.
• BYOL via AHB declaration on the Arc-connected instance. Customer with SA-qualified SQL Server declares AHB on the Arc instance; no Microsoft software cost on the Azure bill; underlying SA must be live.
• Conventional SQL Server licensing. The Arc connection is purely management; the SQL Server license is held under EA / MPSA / SPLA in the normal way; Arc adds management value without changing the licensing posture.

The PAYG-via-Arc option has become materially more competitive through 2025-2026 as Microsoft has adjusted Arc-PAYG rate cards and improved the management integration. For dev/test and burst SQL workloads it is increasingly the right answer, not the niche answer.

Edition economics: Standard vs Enterprise vs Web

SQL Server hosting cost is dominated by edition selection. The three editions in current hosting contexts:

The hosting decision is rarely "Web vs Standard vs Enterprise on cost alone" — it is "what feature set does the workload actually require, what is the consolidation density we can achieve, and does Enterprise+SA unlimited virtualization beat Standard at the target consolidation ratio?"

Unlimited virtualization with Enterprise + SA

SQL Server Enterprise with active SA grants unlimited-virtualization rights on a fully-licensed physical host: license every physical core on the host with SQL Server Enterprise + SA, and run unlimited SQL Server VMs on that host without additional per-VM licensing. This is the single most important density lever in SQL Server hosting.

Practical implications:

• Cost crossover. Above ~6-8 SQL VMs per host, Enterprise+SA unlimited virtualization typically beats Standard per-VM licensing on the same hardware. The exact crossover depends on edition pricing, SA cost, and density.
• BYOL into AHB. Customers with Enterprise+SA can use AHB to bring unlimited-virtualization rights into Azure on dedicated-host configurations.
• BYOL into FVB. Same principle applies to non-listed-provider hosted environments under FVB. Listed-provider rules constrain the unlimited-virt rights — validate per provider.
• Documentation. Unlimited virtualization claims require physical-host licensing inventory; auditors will ask for it.

Listed-provider impact on SQL hosting

SQL Server BYOL into listed providers (AWS, Google Cloud, Alibaba and others on the rotating list) is the single highest-frequency 2025-2026 audit finding pattern in our enterprise SQL data.

The rules in current form:

• SQL Server Standard with SA. Some BYOL paths into listed providers exist with specific rights documentation. Default assumption: more constrained than non-listed-provider FVB.
• SQL Server Enterprise with SA. Different and more limited BYOL paths into listed providers. Unlimited-virtualization rights typically do not extend into listed-provider hosted environments without explicit additional rights.
• AHB on listed providers. Requires explicit attestation and audit-ready documentation per Microsoft Verification methodology.

The remediation pattern for findings in this space is forced revert to PAYG SQL Server pricing on the impacted VMs, with backdated true-up across the audit window. Findings in the $500K-$5M range are typical for enterprise SQL portfolios that BYOL into listed providers without rights documentation. See Microsoft Audit Defense for the engagement that prevents and resolves these.

Audit patterns specific to hosted SQL Server

Five audit patterns dominate hosted-SQL findings:

1. AHB over-declaration. More VMs flagged AHB-eligible than the per-core SA entitlement supports. The single most frequent finding pattern.
2. Listed-provider BYOL without rights documentation. SQL Server Enterprise BYOL on AWS or Google Cloud without FVB-equivalent rights. Highest unit-value findings.
3. Unlimited-virtualization claims without fully-licensed-host evidence. Enterprise+SA unlimited-virt is conditional on every physical core being licensed; partial licensing breaks the right.
4. SPLA SQL Web mis-application. Web edition is restricted to web-facing workloads with no internal business application use; misuse triggers reclassification.
5. Per-vCPU vs per-physical-core mismatches under SPLA reporting on virtualized hosts.

A practical cost model: one workload, three mechanisms

A 100-VM SQL Server estate, 4 cores per VM, mixed Standard / Enterprise, mid-market hosting. The Microsoft cost layer (illustrative 2026 rates, before negotiation) varies as follows:

The ranges are illustrative, not contractual. The pattern is consistent: the spread between the highest-cost and lowest-cost compliant mechanism for the same workload is 3-5x. Most enterprise SQL hosting estates we engage with have at least one major workload running on the wrong mechanism for its entitlement profile.

Major 2026 changes affecting SQL Server hosting

Four named 2026 changes shape the SQL Server hosting conversation:

1. Continued AHB-overdeclaration verification. Microsoft Verification has prioritized AHB-overdeclaration audits on SQL Server through 2025-2026. The remediation pattern is forced PAYG revert with backdated true-up.

2. Azure Arc-enabled SQL Server pricing competitiveness. Arc-PAYG SQL pricing has narrowed the gap with conventional licensing for burst and dev/test workloads. The 2026 right answer for these workloads is often Arc-PAYG, not conventional EA.

3. Listed-provider BYOL boundary moves. The listed-provider rule set continues to evolve quarterly. Validate at the start of any SQL hosting engagement on AWS or Google Cloud.

4. AI and Fabric-attached SQL workloads. SQL Server workloads attached to Fabric (Microsoft's analytics platform) or AI agent infrastructures have new entitlement scope clarifications through 2025-2026; validate before assuming standard hosting rights cover the workload.

For the broader 2026 licensing context, see our 2026 Microsoft Licensing Changes rollup and the companion Microsoft IaaS Licensing Guide.