Azure Hybrid Benefit: who qualifies and what it saves

An Azure Windows VM is billed in two parts: the compute, and the Windows Server license. With the benefit switched on, Microsoft states that you pay only the base compute rate, which equals the Linux rate for the same VM. The Software Assurance cost sits in your agreement, not on the Azure bill. The same logic applies to SQL: on Azure SQL Database and SQL Managed Instance the price has a compute component and a license component, and the benefit replaces the license component with a smaller Software Assurance charge.

The switch itself is a metadata flag on the resource. Microsoft notes that changing the license type does not restart the VM and does not interrupt service. That is why the benefit is easy to enable and easy to enable wrongly: nothing in Azure checks whether you hold the licenses behind the flag. The entitlement lives in your agreement, not in the portal.

Savings on the Azure side show up quickly, which makes this one of the first levers in any Azure cost optimization project. The question is never whether to use it. The question is whether you have enough qualifying licenses, for the right products, for the whole time the workload runs.

Microsoft's requirement is one sentence: on-premises core licenses for Windows Server from an applicable program with active Software Assurance, or qualifying subscription licenses. Software Assurance and subscription licenses are only sold within certain commercial agreements, so the first question for any estate is where the licenses came from and what the agreement says today.

Two points catch people. First, Microsoft says that the Product Terms for your program take precedence over its documentation, so the agreement you actually hold decides. Second, the benefit is tied to the licensing term: workloads that use it may run only while Software Assurance or the subscription is active. A lapsed renewal turns the saving into a compliance gap.

Microsoft's rule for Windows Server: a minimum of 8 core licenses per VM, Standard or Datacenter. A 4-core instance needs 8, a 12-core instance needs 12, and for customers with processor licenses, one processor license equals 16 core licenses. A fleet of 30 small VMs with 4 vCPUs and 20 larger VMs with 16 vCPUs therefore needs 30 x 8 + 20 x 16 = 560 core licenses. Counting vCPUs alone would give 440 and leave a hole of 120 licenses.

SQL Server is more generous for the right combination. Per Microsoft's table, one Enterprise Edition core with Software Assurance equals four vCores on the General Purpose tier of Azure SQL Database or Managed Instance, or one vCore on Business Critical. A Standard Edition core equals one vCore on General Purpose, and four Standard cores equal one vCore on Business Critical. Mixing up the tiers is the most common way a SQL estate ends up over or under licensed.

Source: Microsoft Learn, Azure Hybrid Benefit for Azure SQL Database and SQL Managed Instance.

The exact rule depends on the product and edition, and the differences matter for planning:

For planning, treat the 180 days as a project window and not as a permanent extra entitlement. Schedule the decommissioning of the on-premises host as part of the migration plan, and write the end date of the window next to each wave. Where Datacenter licenses with Software Assurance sit under both worlds indefinitely for VM licensing, the more common mistake runs the other way: customers forget that the Standard edition does not have that right.

Microsoft's partner documentation describes it directly: partners in the CSP program can acquire Server Subscriptions, subscriptions to Windows Server and SQL Server, on behalf of customers and the customers use them with Azure Hybrid Benefit. For Azure Local, Microsoft lists the same two routes: Windows Server Datacenter under an Enterprise Agreement with active Software Assurance, or a CSP subscription.

The practical difference between the agreements is in the evidence trail. Under an EA, entitlement follows the license quantities and Software Assurance dates in the enrollment, and the benefit usually continues for as long as the enrollment renews. Under CSP, a subscription runs for its term and has to be renewed, and a subscription that lapses ends the right to run workloads with the benefit. Software subscriptions in CSP autorenew by default when bought after October 14, 2021, and can be canceled within the first seven days of a term. After that the full term is payable. Anyone moving from an EA to CSP should check the Windows Server and SQL Server position before the move, because the licenses that carried Software Assurance in the old enrollment are not automatically replaced. Our comparison of EA, MCA-E and CSP covers the wider decision.

Checked against Microsoft Learn. Microsoft states that the Product Terms for your program take precedence, and the program-level wording for MPSA, Open Value or MOSA customers can differ in detail.

The 40% figure comes from Microsoft's partner documentation. The 80% and 85% figures come from the Azure Hybrid Benefit offer page, which carries Microsoft's footnote that actual savings may vary based on region, instance type or usage. Treat all of them as ceilings. The Azure SQL documentation itself is more modest and says you can save up to 30 percent or more on SQL Database and SQL Managed Instance. The mechanism tells you where your own number will land: the saving equals the Windows or SQL license line on your invoice. A VM series with a high license share of the total price saves more in percent than one dominated by expensive compute.

Our own cost model for an estate always starts with the license line, not the percentage. List every VM with Windows Server, count the licenses you can allocate, and price the same VMs with and without the flag in the Azure pricing calculator for your region and agreement. That gives a figure in your own currency per VM instead of a marketing range, and it shows quickly which VMs are worth the licenses. For a Swiss estate, remember that regional prices in Switzerland North and West differ from other European regions, which changes the base the percentage applies to.

Microsoft is explicit about the split for compute. For Windows virtual machines and SQL Database, the reservation discount does not apply to the software costs and you cover the license with Azure Hybrid Benefit. A savings plan for compute likewise covers infrastructure only and does not cover software, networking or storage. The two instruments therefore stack without competing.

The savings plan for databases works differently. Microsoft says it applies to infrastructure and software IP costs for Azure SQL Database, SQL Managed Instance and other database services, and to hourly SQL Server license charges on VMs, but those license hours consume the plan at the normal pay-as-you-go price, so without a discount. For SQL workloads it overlaps with what the license benefit removes, so model the stack for each database workload before you commit to both.

The order we recommend: remove waste first, then claim the license benefit, then commit to a baseline. A reservation on an oversized VM locks in the size you were about to reduce. The license benefit does not depend on commitment size, so it can go live right away and it shows which VMs are cheap enough to keep. Our comparison of reserved instances and savings plans explains which commitment fits which workload pattern.

For a worked picture: a VM that costs 100 at pay as you go splits into base compute and license, say 60 and 40 in a high-license-share case. The benefit moves the bill to 60. A reservation then discounts that 60. The commitment never touches the 40, which is why the benefit has to be switched on separately and why a reservation-only strategy leaves the license line at full price.

Microsoft's wording is direct: workloads that use Azure Hybrid Benefit can run only during the Software Assurance or subscription term. When the term approaches expiry you either renew, disable the benefit on the resources, or deprovision them. The same page adds that Microsoft reserves the right to audit eligibility at any time, and that you should inventory VMs with the benefit and compare the count with your Software Assurance or subscription licenses.

In practice, three events create the gap: an EA that is not renewed or replaced by MCA-E, a CSP subscription that nobody renewed, and a migration wave that raised the VM count past the license count. Each is visible in advance if somebody compares the licenses held against the VMs flagged. If you hold fewer licenses than flagged VMs, Microsoft lists three options: buy additional licenses with Software Assurance or subscription, disable the benefit on some VMs, or deallocate some VMs.

The control that works is a quarterly count. Take the number of VMs and vCores with the license type set, convert to core licenses with the 8-core minimum, and compare with the quantity in the agreement. For SQL, Microsoft also offers scope-level assignment, where you allocate a number of SQL core licenses to a subscription or billing account instead of ticking a box per resource. That turns the count into a number you can monitor.