CIO Playbook: Windows Server & SQL Server Licensing in Hybrid Environments

Traditional model: Licenses are tied to physical hardware — assigned to a host's physical cores, and VM rights determined by edition. This remains fully in effect and is simplest for enterprise data centers where you control the host.

Per-VM licensing (Oct 2022+): For customers with active SA or subscription licenses, you can now assign licenses just to the virtual cores in a VM (minimum 8 core licenses per VM) without licensing the entire host. This is particularly useful with the Flexible Virtualization Benefit on third-party clouds — it removes the requirement to dedicate an entire physical server to your licenses.

Practical Guidance: Use traditional per-host licensing for your own data centers (Datacenter for unlimited VMs). Use per-VM licensing for hosted or multi-tenant cloud environments where you have a few Windows workloads on a larger hypervisor you don't want to fully license.

License-Included (Pay-as-You-Go): Pay the cloud provider for Windows Server as part of the VM's hourly cost. Convenient and compliant. Best for short-term or elastic workloads. More expensive for long-running servers.

Bring Your Own License (BYOL): Use your organization's Windows Server licenses to cover cloud VMs. For Azure, use Azure Hybrid Benefit (straightforward). For AWS/GCP, BYOL requires active SA with License Mobility rights and typically dedicated hosts or special BYOL programs.

Key Rule: For Azure, BYOL is straightforward via Azure Hybrid Benefit. For other clouds, Windows Server BYOL is only allowed if you have SA or subscription licenses and are using an "Authorized Outsourcer" environment — not simply the default shared cloud of AWS/GCP unless using a dedicated host.

Starting with Windows Server 2025, organizations can connect on-premises servers to Azure Arc and enable a pay-as-you-go licensing model. Organizations without unlimited virtualization rights can "spill over" capacity on a pay-per-core basis (~$33.58/core/month).

Useful for handling seasonal spikes or pilot projects on-premises without over-provisioning licenses. Azure Arc bridges your on-prem environment to Azure's billing for dynamic scaling.

Evaluate Carefully: Compare the pay-as-you-go cost against traditional license purchases for steady-state needs. This model adds flexibility but may be more expensive than perpetual licenses for permanent workloads.

Strategy 1 — License Per VM: License each virtual machine individually based on vCPUs assigned (minimum 4 core licenses per VM). Straightforward for few SQL VMs. Requires SA for license mobility. Without SA, license assignment is locked to a specific host for 90 days.

Strategy 2 — License the Host (All Cores): License all physical cores on the virtualization host with SQL Enterprise + SA. Grants rights to run any number of SQL instances. Simplifies management — any new SQL VM on the host is automatically licensed. In VMware/Hyper-V clusters, apply to each host to enable free VM movement (vMotion/Live Migration).

Example: 20 SQL VMs with 4 vCPUs each → per-VM = 80 core licenses. Same VMs on a 2-host cluster (20 cores each, 40 total) → license hosts = 40 cores of SQL Enterprise + SA. The host approach uses half the licenses when SQL density is high. Analyze your consolidation ratio.

With Software Assurance, SQL Server provides generous HA/DR benefits. As of SQL Server 2022, SA allows up to two passive secondary instances per primary at no additional license cost — one for high availability clustering and one for disaster recovery.

Example: Active SQL Server on-premises + passive failover node at remote site + passive copy in Azure for DR = two secondary servers require no separate licenses (with SA), as long as they are truly passive (not serving queries except during failover).

Caution: If a secondary is ever used for read workloads or reporting, it ceases to be "passive" and requires separate licensing. Document all passive instances covered by SA to avoid accidental double-licensing.

Azure: SQL Server available as IaaS (SQL on Azure VMs) or PaaS (Azure SQL Database, Managed Instance). Apply Azure Hybrid Benefit to avoid SQL licensing charges. One SQL Enterprise core license = 4 vCores in Azure SQL Database General Purpose tier. 180-day dual-use grace period for migration.

AWS & Other Clouds: License Mobility through SA enables BYOL for SQL Server on shared servers. On AWS: use license-included EC2 images (simple, full cost), BYOL via SA (install your own), or Dedicated Hosts (full control, BYOL even without SA). Same 90-day reassignment rule applies without SA; waived with SA via License Mobility.

Bottom Line: For hybrid cloud use of SQL Server, having Software Assurance is almost a de facto requirement to enable flexibility — migration, mobility, Azure benefits, and HA rights. Factor SA costs into overall licensing strategy; the benefits often pay for themselves.

Select a Windows Server BYOL image for your Azure VM and indicate you're using your existing license. Azure charges only the base compute rate (equivalent to Linux VM) instead of the higher Windows rate. Requires active SA or subscription licenses.

Standard vs. Datacenter — Critical Difference:

Standard Edition: Cannot use the same license simultaneously on-premises and in Azure. Must assign to one environment. Exception: 180-day overlap during migration (run in both places while migrating, then retire one).

Datacenter Edition + SA: Permits simultaneous dual usage — both on-premises for unlimited VMs and in Azure for additional VMs. Unlimited in duration. This makes Datacenter + SA extremely attractive for hybrid deployments — maintain on-prem capacity and burst to Azure or gradually migrate without needing new Windows licenses.

License Math: Each 2-core pack of Windows Server Standard covers 1 Azure VM with up to 8 vCPUs. Datacenter covers 1 Azure VM with up to 16 vCPUs per 2-core pack. Ensure you have enough eligible licenses allocated to Azure for compliance.

Apply AHB to Azure VMs running SQL Server to avoid SQL licensing charges. Each core of SQL Enterprise with SA = 1 vCPU in Azure SQL VM (Enterprise) or up to 4 vCores in Azure SQL Database (PaaS). SQL Standard: 1 core = 1 vCPU or 1 vCore in General Purpose tier.

180-day dual-use grace period for migration. Unlike Windows Datacenter, SQL Server licenses do not allow indefinite dual use — once migrated, the license must be assigned solely to Azure.

PaaS Multiplier: Moving to Azure SQL Database can effectively multiply the value of your licenses — one on-prem SQL Enterprise core covers four vCores in PaaS General Purpose. Factor this into migration ROI calculations.

Track license usage carefully when using AHB. Azure provides indicators on your bill and in the portal showing how many VMs use AHB. Ensure you have at least as many eligible licenses (with SA) as the VMs you're covering. Microsoft has the right to verify assignments.

Establish policies to ensure any eligible workload migrating to Azure utilizes AHB. Train cloud engineers to mark VMs for BYOL. Coordinate with asset management to confirm license availability. Use Azure Policy or deployment templates that default to BYOL if the organization has available licenses.

Azure Dedicated Hosts: AHB also works on Azure Dedicated Hosts. With Windows Datacenter, license all cores of a dedicated host with on-prem licenses and run unlimited Windows VMs. Treating Azure hardware as an extension of your on-prem environment — ensure you have enough licenses to cover the entire host.

Windows Server 2025 launches with licensing updates. While the core model (per 2-core packs, Standard vs. Datacenter) remains, Microsoft is adjusting pricing. On-premises server products face a price increase of approximately 10% in 2025.

Budget owners may want to true up or renew licenses before the increase takes effect to lock in pre-increase pricing. Enterprise agreements renewing around 2025 should account for slightly higher Windows Server costs.

Microsoft is transitioning some server products to subscription-only models. While Windows Server 2025 is still offered as traditional license or Azure subscription, Microsoft encourages subscription licensing. Azure Arc pay-as-you-go for on-premises represents the trend toward cloud-like billing models.

This changes OpEx vs. CapEx forecasting. If your organization prefers perpetual licenses for predictability, these options remain — but the trend gradually shifts toward cloud-like models. Consider piloting Azure Arc pay-as-you-go on a small set of servers to evaluate the model.

Global pricing adjustments: Some regions saw increases in 2023–2024 to align with USD pricing. Include a buffer in multi-year budgets. Core CAL and Enterprise CAL suites have slated increases in 2025.

Extended Security Updates (ESUs): Windows Server 2012/R2 and SQL 2012 have reached end of support. ESUs are very expensive on-premises but free if you migrate workloads to Azure (aside from Azure VM charges). Sometimes moving an old server to Azure for 1–2 years is cheaper when considering on-premises ESU costs.