Azure Hybrid Benefit Explained: Windows Server and SQL Server, What Qualifies, the 180-Day Window, and How to Prove It
Azure Hybrid Benefit is the line on an Azure quote that turns a Windows Server or SQL Server VM from license-included pricing into base compute. It is not a discount you ask for; it is a licensing attestation you make, and Microsoft reserves the right to check it. Here is what qualifies, what the 180-day window allows, how to switch it on, and what to keep so you can prove it.
What the benefit does
Windows Server. Azure bills a Windows VM at a rate that includes the Windows Server license. With Azure Hybrid Benefit for Windows Server you allocate your own Windows Server core licenses to the VM and pay the base compute rate, which Microsoft's documentation equates to the Linux rate for the same size. It also covers Azure Local and AKS on Windows Server and Azure Local.
SQL Server. Azure bills SQL Server on an Azure VM, Azure SQL Managed Instance and Azure SQL Database at license-included rates. With Azure Hybrid Benefit for SQL Server you allocate your SQL Server core licenses and pay the base rate; compute, storage, backups and I/O remain your Azure charges. Microsoft's Product Terms require you to indicate that you are using the benefit when you configure the workload. It is not applied for you.
What you need to qualify
Both benefits have the same gate: Windows Server Standard or Datacenter core licenses, or SQL Server Standard or Enterprise core licenses, with active Software Assurance or a qualifying subscription. Three consequences follow.
A perpetual license bought without Software Assurance does not qualify, and that includes perpetual Windows Server and SQL Server bought through CSP. Our Windows Server licensing calculator and SQL Server licensing calculator price the one- and three-year subscription SKUs beside the perpetual ones for exactly this reason.
Server + CAL licenses for SQL Server do not qualify even with Software Assurance; Microsoft's SQL Server on Azure VM documentation allows them license mobility to an Azure VM, but not the rest of the benefit.
The benefit lasts only as long as the Software Assurance or subscription term: at expiry you renew, disable the benefit, or deprovision the workload. If your Enterprise Agreement is ending, this is one of the entitlements that does not automatically survive the move to CSP; our EA transition advisory maps which do.
How licenses convert: minimums, ratios and the 180-day window
Windows Server. You need a minimum of eight core licenses per VM, so a four-core VM still consumes eight. Standard licenses can be used on premises or in Azure but not both at once, with one exception: a one-time period of up to 180 days to migrate the same workloads. Datacenter is different: for VM licensing Microsoft allows simultaneous use on premises and in Azure indefinitely while migrating, and unlimited virtualization on an Azure Dedicated Host if you allocate Datacenter licenses for all of its physical cores; for Dedicated Host licensing the dual-use window is 180 days.
On your own hardware every server is licensed for at least 16 cores; in Azure the floor is eight per VM, so a 16-core Standard license set covers two eight-core VMs.
SQL Server. Microsoft's Azure SQL documentation gives the ratios: one Enterprise core covers four General Purpose vCores or one Business Critical vCore; one Standard core covers one General Purpose vCore, and four Standard cores cover one Business Critical vCore. On a SQL Server VM the four-core minimum applies. The migration allowance is 180 days of dual use, after which the license can be used only in Azure, and the benefit also licenses one passive high-availability replica and one disaster-recovery replica at no license charge.
The Windows Server licensing calculator counts the core licenses your on-premises hosts consume under the minimums, which is what you have to bring; the SQL Server licensing calculator sets Azure VM and Azure SQL rows with the benefit beside pay-as-you-go, with license prices live and compute rates as labeled samples.
How to apply it
Windows Server VM. At creation, tick the Licensing box on the Basics tab to use an existing Windows Server license; on an existing VM, open Operating system and set Azure Hybrid Benefit to Enable. Underneath it is the licenseType property with the value Windows_Server, settable with Update-AzVM or az vm update; changing it neither restarts the VM nor interrupts service. Scale sets take the same property; classic VMs are not supported.
SQL Server on an Azure VM. The VM must be registered with the SQL IaaS Agent extension, automatic for Marketplace images deployed through the portal and manual for self-installed SQL Server. Then, in the SQL virtual machines resource under Configure, choose Azure Hybrid Benefit and confirm you hold a license with Software Assurance; the CLI and PowerShell equivalents take the license type AHUB, and the change takes effect without a restart. Two traps: adding the VM to an availability set recreates it and resets the license type to pay-as-you-go, and deleting the SQL virtual machines resource returns the VM to the image default.
Azure SQL Database and Managed Instance. The benefit applies to the vCore purchasing model on provisioned compute only, not DTU or serverless. In the portal it is the Save money option under Compute + storage; in PowerShell and the CLI the license type is BasePrice.
At scale. Centrally managed Azure Hybrid Benefit assigns SQL Server licenses at subscription or billing-account scope; once it is on, per-VM license changes are locked. CSP customers on an Azure plan deploy a pay-as-you-go VM first, then activate the benefit.
Proving entitlement: what to keep and what Microsoft can ask for
Microsoft's Windows Server documentation says it plainly: Microsoft reserves the right to audit customers at any time to verify eligibility. The evidence has to exist before the question is asked.
- A license inventory: agreement or CSP order, product, edition, core count, and the Software Assurance or subscription end date. Software Assurance records live in the Volume Licensing Service Center or the Business Center; subscription records are the partner invoice.
- A resource inventory: every VM and scale set with the benefit enabled, from the portal's OS licensing benefit column, Get-AzVM filtered on license type, or az vm list with a licenseType query; the SQL virtual machines resource shows each SQL VM's license type.
- The arithmetic: cores consumed in Azure under the minimums, plus cores still in use on premises outside the 180-day window, against cores owned. Windows Server Standard is the one to watch, because dual use outside the window is a breach.
- The bill: Azure invoices show WindowsServerBYOL in the additional information for VMs on the benefit, several hours after activation.
If the count comes up short, Microsoft gives three choices: buy more licenses with Software Assurance or a subscription, disable the benefit on some VMs, or deallocate them. Our Windows Server and SQL Server Licensing and True-Up Advisory builds exactly this reconciliation, and the Azure Migrate Datacenter Discovery and Assessment prices the benefit and reservations into the target cost model before a migration starts.
Frequently asked questions
Can I use Azure Hybrid Benefit with licenses bought through CSP?
Subscription licenses, yes; perpetual CSP licenses, no, because they carry no Software Assurance.
What happens when Software Assurance expires?
The benefit ends with it. Renew, disable the benefit on the affected resources, or deprovision them.
Can a Windows Server Standard license run on premises while the Azure VM uses it?
Only during the one-time 180-day migration window. Datacenter licenses used for Azure VMs may run on both sides while migrating.
Does the benefit cover the disaster-recovery copy of my SQL Server?
On SQL Server on Azure VMs, one passive high-availability replica and one disaster-recovery replica carry no license charge, and since November 2022 pay-as-you-go VMs get the same.
How do I see everything that has the benefit turned on?
The OS licensing benefit column in the portal, Get-AzVM filtered on license type, or az vm list with a licenseType query; the Azure bill marks them WindowsServerBYOL.
Sources
- Microsoft Learn: Azure Hybrid Benefit for Windows Server (Windows Server documentation); Explore Azure Hybrid Benefit for Windows VMs (Azure Virtual Machines); Azure Hybrid Benefit for Azure SQL Database and SQL Managed Instance; Change the license model for a SQL virtual machine in Azure; Pricing guidance for SQL Server on Azure VMs
- Microsoft Learn training module: Optimize costs using Azure Hybrid Benefit (the four-core minimum per SQL Server VM)
- IT Partner: Windows Server and SQL Server licensing calculator rule tables; Windows Server 2025 Licensing: What Changed
The Microsoft Product Terms take precedence over every article above and were not opened; where a rule lives only there, the text says so.
| Azure Hybrid Benefit for Windows Server | Azure Hybrid Benefit for SQL Server | |
|---|---|---|
| Qualifying license | Standard or Datacenter core licenses with active Software Assurance or a subscription | Standard or Enterprise core licenses with Software Assurance or a SQL Server subscription; Server + CAL does not qualify |
| Where it applies | Azure VMs and scale sets, Azure Local, AKS | SQL Server on Azure VMs, Azure SQL Managed Instance, Azure SQL Database (vCore, provisioned) |
| Minimum per VM | 8 core licenses; a processor license counts as 16 | 4 core licenses |
| Conversion | 1 core license = 1 vCore | Enterprise: 1 core = 4 General Purpose vCores or 1 Business Critical vCore; Standard: 1 core = 1 General Purpose vCore |
| Dual use | Standard: one-time 180 days; Datacenter VM licensing: simultaneous while migrating | 180-day migration allowance |
| Extras | Unlimited virtualization on a Dedicated Host with Datacenter | One passive HA replica and one DR replica without a license charge |
Key takeaways
- Azure Hybrid Benefit swaps license-included Azure rates for base compute; you need core licenses with active Software Assurance or a qualifying subscription, and you attest to it yourself.
- Perpetual licenses bought through CSP carry no Software Assurance and do not qualify; CSP subscription licenses do.
- Windows Server needs eight core licenses per VM, with a one-time 180-day dual-use window for Standard; SQL Server gets 180 days, and Enterprise cores convert four-to-one on Azure SQL General Purpose.
- Switching the benefit on is a metadata change with no restart, but availability-set changes and deleted SQL VM resources reset it.
- Keep a license inventory, a resource inventory and the arithmetic between them; Microsoft can audit at any time.
Count what you own with the Windows Server licensing calculator, price the Azure rows with the SQL Server licensing calculator, and if a migration is on the table, the Azure Migrate Datacenter Discovery and Assessment delivers a right-sized Azure cost model with the benefit and reservations priced in for a fixed $1,950. The Hyper-V and VMware migration services apply the benefit where your licensing qualifies as part of the move.
Questions this article didn’t answer?
Thirty minutes with Mike — our CEO, not a sales rep. Bring the hard version of the question.