Hybrid and multi-cloud deployments introduce significant licensing complexity for SQL Server workloads. IT asset managers must navigate on-premises perpetual licensing, cloud subscription models, Azure Hybrid Benefit, License Mobility through Software Assurance, Listed Provider restrictions for AWS and GCP, dual-use migration rights, disaster recovery licensing, and the Flexible Virtualisation Benefit. This guide provides a comprehensive framework for understanding SQL Server licensing rules across on-premises, Azure, AWS, and GCP deployments.
On-premises SQL Server is licensed through perpetual licences using either per-core or Server+CAL models. Per-core licensing requires one licence for every two physical cores, with a minimum of four cores per server or virtual machine. These perpetual licences provide indefinite usage rights on the organisation's own hardware.
In cloud environments, SQL Server can be licensed through provider-included (pay-as-you-go) pricing, where the hourly VM rate includes the SQL Server licence cost, or through BYOL (Bring Your Own Licence), where existing on-premises licences are applied to cloud instances and the organisation pays only the lower base compute rate. Provider-included pricing carries a 30 to 50% cost premium over BYOL for sustained workloads.
BYOL requires active Software Assurance on the licences being moved and adherence to Microsoft's specific BYOL rules for each target cloud platform. Provider-included pricing is operationally simple but significantly more expensive for steady-state workloads. The choice depends on existing licence entitlements, target cloud platform, expected workload duration and utilisation pattern, and SQL Server edition. See SQL Server 2022 Licensing Guide.
Azure Hybrid Benefit (AHB) is the single most impactful cost optimisation mechanism for SQL Server workloads in hybrid environments. AHB allows organisations with existing SQL Server licences covered by active Software Assurance to apply those licences to Azure VMs or Azure SQL managed services, paying only the base compute and storage rate. Savings are typically 30 to 50% compared to standard pay-as-you-go pricing.
Each SQL Server Enterprise core licence with SA covers one virtual core on Azure (or one physical core on Azure Dedicated Host). AHB for SQL VMs can be toggled on and off through the Azure portal, allowing flexible management as workloads move between environments. The organisation must ensure that the total number of cores deployed on Azure via AHB does not exceed its licensed core entitlement.
AHB extends beyond VMs to Azure SQL Database, Azure SQL Managed Instance, and Azure Synapse Analytics. This means organisations can apply existing SQL Server licences to fully managed PaaS services, not just IaaS VMs. The cost savings on managed services are comparable to those on VMs, making AHB valuable across both IaaS and PaaS deployment models.
SQL Server Enterprise with active Software Assurance qualifies for an unlimited virtualisation benefit on Azure Dedicated Hosts. The organisation can run any number of SQL Server instances on dedicated hardware without licensing each VM's cores individually. This mirrors the on-premises unlimited virtualisation right and is particularly valuable for large, dense SQL Server deployments.
AHB includes up to 180 days of simultaneous dual-use rights during migration. The organisation can run SQL Server on-premises and in Azure concurrently using the same licences while transitioning workloads. This eliminates additional licence purchases during migration testing, validation, and cutover. AWS and GCP do not offer equivalent dual-use provisions, making Azure the most migration-friendly platform for SQL Server workloads with existing licences.
SQL Server BYOL on AWS and GCP is permitted through License Mobility with active Software Assurance, but the process and constraints differ significantly from Azure. Microsoft classifies AWS, GCP, and Alibaba Cloud as "Listed Providers" with specific restrictions and verification requirements.
| Capability | Azure | AWS / GCP (Listed Providers) |
|---|---|---|
| SQL Server BYOL (with SA) | AHB on shared VMs and managed services | License Mobility on shared VMs (verification required) |
| SQL Server BYOL (without SA) | Dedicated Host only | Provider-included only: no BYOL |
| Dual-use migration rights | 180 days concurrent on-prem + Azure | No equivalent dual-use provision |
| Unlimited virtualisation (Enterprise + SA) | Available on Dedicated Hosts | Requires dedicated hosts with all cores licensed |
| Verification process | Self-managed through Azure portal | License Mobility verification form to Microsoft required |
| Managed database services | AHB applies to Azure SQL DB, MI, Synapse | RDS includes licence in pricing: no BYOL |
Azure provides self-service AHB toggling, dual-use migration rights, BYOL on managed PaaS services, and no verification form requirement. AWS and GCP require License Mobility verification forms, offer no dual-use provisions, and do not support BYOL on managed database services (RDS, Cloud SQL). For organisations with existing SQL Server licences and SA, Azure is the most cost-effective and operationally simple cloud platform for SQL Server workloads.
An organisation migrating production SQL Server databases from on-premises to Azure can leverage the 180-day dual-use rights under AHB. During the migration period, the same SQL Server licences cover both the on-premises instance (running for parallel validation and fallback) and the Azure VM or managed instance (being configured, tested, and validated). This eliminates the need to purchase additional licences for the migration period. The dual-use period is limited to 180 days. Plan migration timelines to complete the transition within this window, and ensure on-premises deployments are decommissioned or relicensed after migration.
Organisations running SQL Server on-premises as the primary instance can maintain a passive secondary failover instance in Azure at minimal licensing cost. Software Assurance includes failover rights that allow a passive secondary replica without a separate SQL Server licence, provided the secondary is truly passive (not serving read workloads or queries). The organisation pays only Azure compute and storage costs for the standby VM, with no additional SQL Server licensing cost.
If the secondary instance is configured to serve read-only queries, reporting workloads, or analytics traffic, it is no longer "passive" under Microsoft's terms and requires its own SQL Server licence. The distinction between passive failover (no licence required) and active secondary (full licence required) is one of the most frequently misunderstood areas of SQL Server hybrid licensing and a common audit finding. If read workloads on the secondary are not business-critical, disable them and save the licensing cost.
Organisations deploying SQL Server across multiple cloud providers must manage licence allocation carefully to avoid both duplicate licensing (paying for more licences than needed) and compliance gaps (using SQL Server in more environments than entitlements permit). A single SQL Server licence can be assigned to one environment at a time.
Use BYOL via AHB for sustained Azure workloads (greatest savings, lowest administrative overhead). Use provider-included licensing for AWS or GCP workloads where BYOL administrative requirements are not justified by the savings. Use dedicated host deployments on AWS for SQL Server Enterprise workloads requiring unlimited virtualisation or where the organisation lacks active SA. Review licence allocation decisions at least quarterly as workloads move between environments. See Common Compliance Pitfalls in SQL Server Licensing.
License Mobility allows moving SQL Server licences from one server to another or to cloud VMs more frequently than the standard 90-day reassignment limitation. SQL Server licences with active SA can be deployed on AWS, GCP, or other eligible cloud providers' shared infrastructure without the 90-day waiting period. This flexibility is critical for dynamic cloud environments where workloads shift between infrastructure regularly. See Software Assurance Benefits for SQL Server.
Introduced in 2022, this benefit allows organisations with active Software Assurance to bring SQL Server licences to authorised cloud providers' shared data centres without requiring dedicated hardware. While the major Listed Providers (AWS, GCP, Alibaba) still have specific restrictions, the Flexible Virtualisation Benefit expanded options for smaller and regional cloud providers. This means additional vendor choice for placing SQL Server workloads.
SQL Server container licensing follows the same core-based principles as VM licensing: each container host node must have sufficient SQL Server core licences to cover cores allocated to SQL Server containers, with a minimum of four cores per container. For SQL Server Enterprise with SA on container orchestration platforms, the unlimited virtualisation benefit covers unlimited containers on fully licensed host nodes. In cloud-managed Kubernetes (AKS, EKS, GKE), AHB can be used for SQL Server containers on Azure Kubernetes Service, while AWS and GCP follow Listed Provider rules. Container scheduling policies should ensure SQL Server pods are only scheduled on properly licensed nodes.
Azure Hybrid Benefit (AHB) allows organisations with existing SQL Server licences covered by active Software Assurance to apply those licences to Azure VMs or Azure SQL managed services (Azure SQL Database, Managed Instance, Synapse Analytics). The organisation pays only the base compute and storage rate rather than the full licence-included price, saving 30 to 50% on Azure SQL costs. AHB can be toggled on and off through the Azure portal and includes 180-day dual-use migration rights for concurrent on-premises and Azure operation.
Yes, through License Mobility with active Software Assurance. Microsoft classifies AWS, GCP, and Alibaba as "Listed Providers" with specific restrictions: a License Mobility verification form must be submitted to Microsoft, no dual-use migration rights are available (unlike Azure's 180-day provision), and BYOL does not apply to managed database services (RDS, Cloud SQL). For AWS/GCP deployments without SA, you must use provider-included pricing which includes the SQL Server licence cost in the VM rate.
Under Azure Hybrid Benefit, organisations can run SQL Server on-premises and in Azure concurrently using the same licences for up to 180 days during migration. This eliminates additional licence purchases during migration testing, validation, and cutover. After 180 days, the licence must be assigned to either on-premises or Azure, not both. AWS and GCP do not offer equivalent dual-use provisions. Plan migration timelines to complete within the 180-day window.
Not if it is truly passive. With Software Assurance, one passive secondary failover instance can be deployed without a separate SQL Server licence, provided the secondary runs no queries, reporting, maintenance, or other workloads. If the secondary serves read-only queries or reporting (including Always On readable secondaries), it requires its own full per-core licensing. This passive vs active distinction is one of the most common SQL Server audit findings.
SQL Server container licensing follows core-based principles: each container host node must have sufficient SQL Server core licences (minimum 4 cores per container). SQL Server Enterprise with SA on container platforms gets unlimited virtualisation, covering unlimited containers on fully licensed host nodes. In cloud-managed Kubernetes (AKS, EKS, GKE), AHB applies for Azure Kubernetes Service, while AWS and GCP follow Listed Provider BYOL rules. Ensure container scheduling policies only place SQL Server pods on properly licensed nodes.
Introduced in 2022, the Flexible Virtualisation Benefit allows organisations with active Software Assurance to bring SQL Server licences to authorised cloud providers' shared data centres without requiring dedicated hardware. While the major Listed Providers (AWS, GCP, Alibaba) still have specific restrictions, this benefit expanded options for smaller and regional cloud providers. It provides additional vendor choice for placing SQL Server workloads beyond the traditional Azure, AWS, and GCP options.
Azure consistently offers the most favourable SQL Server BYOL terms: self-service AHB toggling through the portal, 180-day dual-use migration rights, BYOL on managed PaaS services (Azure SQL Database, Managed Instance, Synapse), unlimited virtualisation on Dedicated Hosts, and no verification form requirement. AWS and GCP require License Mobility verification forms, offer no dual-use provisions, and do not support BYOL on managed database services. For organisations with existing SQL Server licences and SA, Azure provides the greatest savings with the least administrative overhead.
Redress Compliance provides independent Microsoft advisory for SQL Server hybrid and multi-cloud licensing: Azure Hybrid Benefit optimisation, BYOL assessment across Azure/AWS/GCP, License Mobility verification, virtualisation rights analysis, failover licensing review, container licensing assessment, and audit defence. We help enterprises reduce SQL Server cloud costs by 30 to 50% through optimal licence allocation. Complete vendor independence. No Microsoft partnerships, no resale commissions.
Microsoft Advisory ServicesIndependent Microsoft advisory helping enterprises optimise SQL Server licensing across hybrid and multi-cloud environments through AHB maximisation, BYOL assessment, and compliance management. Fixed-fee engagement models.