Direct answer: at the Azure Retail Prices API on 10 November 2026 (eastus, USD, excluding tax and discounts), the gap between Windows and Linux pricing for the same SKU is the license portion AHB removes: D4s_v5 Windows $0.376/h vs Linux $0.192, so AHB bills Linux and saves $0.184/h = $134.32/month; D8s_v5 $0.752 vs $0.384, saving $268.64/month; D16s_v5 $1.504 vs $0.768, saving $537.28/month. Adding a Linux 1-year reservation puts D8s at about $172.92/month, 68.5% below Windows PAYG; 3-year is about $110.72/month, 79.8% below—close to Microsoft's "up to 80%". Requirements: Windows Server needs at least 8 core licenses (a 4-vCPU VM still needs 8), with active Software Assurance or a qualifying subscription; there is a 180-day dual-running window. SQL AHB applies to SQL Database vCore provisioned (not serverless/DTU), SQL Managed Instance, SQL Server on VMs, SSIS and Arc SQL MI; Enterprise 1 core = 4 GP vCores or 1 BC vCore; Standard 1 core = 1 GP vCore, or 4 cores = 1 BC vCore.

This guide is for teams responsible for Windows/SQL migration, license compliance, FinOps, procurement and finance. It separates official rules, editorial calculations and exclusions, covering Windows VM savings, AHB + reservations, SQL license ratios, the 8-core threshold, 180-day dual running, hidden risks and a 90-day checklist. Prices come from the Azure Retail Prices API, the Azure Hybrid Benefit FAQ and Microsoft Learn (10 November 2026). This is not licensing or legal advice.

Three rules to remember

(1) AHB is not a discount code: you need compliant licenses first, and the Azure bill only drops the license portion—SA/subscription cost is not on the bill. (2) Windows has an 8-core minimum: a 4-vCPU VM still needs 8 core licenses, so small VMs dilute the saving. (3) SQL is not 1 vCPU = 1 core: serverless/DTU are excluded, Enterprise and Standard convert differently, and after 180 days the license stays in Azure.

Scope: what qualifies and what doesn't

Windows Server AHB applies to Windows Server Standard/Datacenter core licenses with active Software Assurance or a qualifying subscription; each VM needs at least 8 core licenses, larger instances need licenses equal to their cores, and processor licenses count as 16 cores. SQL Server AHB applies to SQL Database vCore provisioned (not serverless, not DTU), SQL Managed Instance, SQL Server on Azure VMs, SSIS and Arc SQL MI. Windows and SQL can be combined; AHB also applies to AKS, Dedicated Host, Azure Local and Azure VMware Solution. Windows client (10/11) is not eligible.

ItemRuleNote
Windows ServerStandard/Datacenter core licenses + SA/subscriptionMinimum 8 cores per VM
SQL ServerEnterprise/Standard core licenses + SA/subscriptionvCore provisioned only; no serverless/DTU
LinuxActive RHEL/SLES subscriptionMicrosoft claims up to 76% savings
Dual running180-day migration windowAfter that, Azure or on-prem only
StackingWindows + SQL, AHB + reservationReservation should be Linux-based
ExcludedWindows client; SQL serverless/DTUConfirm in the bill/terms

Sources: Azure Hybrid Benefit FAQ and Learn "Azure Hybrid Benefit for Windows VMs" / "Azure Hybrid Benefit – Azure SQL Database & SQL Managed Instance" (10 November 2026). Rights follow the Microsoft Product Terms and your contract.

Windows VMs: the saving is the Windows-Linux gap

Windows PAYG minus Linux PAYG for the same SKU is the license portion AHB removes from the Azure bill: D4s_v5 $0.376−$0.192=$0.184/h, $134.32/month for 730 hours; D8s_v5 $0.752−$0.384=$0.368/h, $268.64/month; D16s_v5 $1.504−$0.768=$0.736/h, $537.28/month. The license threshold is 8 cores: D4s_v5 has only 4 vCPUs but still needs 8 core licenses; D8s needs 8, D16s 16. Small VMs dilute the per-core saving.

SKUWindows PAYG/monthLinux+AHB/monthSaving/monthLicenses
D4s_v5$274.48$140.16$134.328 cores
D8s_v5$548.96$280.32$268.648 cores
D16s_v5$1,097.92$560.64$537.2816 cores

Editorial calculation: Windows/Linux hourly × 730; D4s_v5 $0.376/$0.192, D8s_v5 $0.752/$0.384, D16s_v5 $1.504/$0.768 (eastus, 10 November 2026). Excludes SA/subscription, storage, network, tax and discounts.

AHB + reservations: close to 80% off

AHB can be stacked with Azure Reserved VM Instances; buy the Linux base and let AHB cover Windows. D8s_v5 Linux 1-year is $2,075/year, or $0.2369/h = $172.92/month; 3-year is $3,986, or $0.1517/h = $110.72/month. Against Windows PAYG at $548.96: 1-year saves $376.04 (68.5%), 3-year saves $438.24 (79.8%). D16s_v5 1-year is $4,151/year = $345.92/month, 3-year $7,972 = $221.44/month, saving 68.5%/79.8% vs $1,097.92 Windows PAYG.

SKU/optionMonthlyvs Windows PAYGNote
D8s Windows PAYG$548.96BaseNo AHB
D8s Linux + AHB$280.32Save $268.64 (48.9%)Linux billing
D8s Linux 1y + AHB$172.92Save $376.04 (68.5%)$2,075/year
D8s Linux 3y + AHB$110.72Save $438.24 (79.8%)$3,986/3 years
D16s Linux 1y + AHB$345.92Save $752.00 (68.5%)$4,151/year
D16s Linux 3y + AHB$221.44Save $876.48 (79.8%)$7,972/3 years

Editorial calculation: reservation total ÷ 8,760 (1y) or 26,280 (3y) × 730; D8s 1y $2,075, 3y $3,986; D16s 1y $4,151, 3y $7,972 (eastus). Excludes SA/subscription, storage, network and tax; stacking follows official terms.

Scale: annual savings for 10/50/100 D8s VMs

For D8s_v5, Linux + AHB vs Windows PAYG: 10 VMs save $32,236.80/year, 50 save $161,184, 100 save $322,368; licenses needed are 80/400/800 cores (8 per VM). With the 3-year reservation, 100 VMs save about $525,888/year ($438.24 × 12 × 100), but require a 3-year commitment and 800 core licenses. Confirm the licenses are owned/renewable, then compute net benefit as Azure savings minus SA/subscription, migration and operations.

D8s VMsAnnual saving (AHB)Annual saving (AHB+3y)Core licenses
10$32,236.80$52,588.8080
50$161,184.00$262,944.00400
100$322,368.00$525,888.00800

Editorial calculation: $268.64 × 12 × VMs (AHB), $438.24 × 12 × VMs (AHB+3y); 8 core licenses per VM; excludes SA/subscription, storage, network, tax and discounts. Actual savings vary by region/SKU/utilization.

SQL AHB: convert by edition, not 1 vCPU = 1 core

SQL AHB applies to SQL Database vCore provisioned (not serverless, not DTU), SQL Managed Instance, SQL Server on Azure VMs, SSIS and Arc SQL MI. License conversion: Enterprise 1 on-prem core = 4 GP vCores or 1 BC vCore; Standard 1 core = 1 GP vCore, or 4 cores = 1 BC vCore. Microsoft Learn says SQL DB/MI saves "30% or more"; the AHB FAQ says SQL overall saves up to 85%—different scopes, not interchangeable. The 180-day migration window allows on-prem and Azure simultaneously; after that the license stays in Azure.

Edition1 on-prem core buysNote
Enterprise + SA4 GP vCores or 1 BC vCoreVirtualization advantage
Standard + SA1 GP vCore; 4 cores = 1 BC vCoreConvert by GP/BC
SQL DBvCore provisioned onlyServerless/DTU excluded
SQL MI / SQL on VM / SSIS / Arc SQL MIEligiblePer product terms
Dual running180 daysAzure-only afterward

Sources: Learn "Azure Hybrid Benefit – Azure SQL Database & SQL Managed Instance" and AHB FAQ (10 November 2026). Official savings are "up to 30% or more" (SQL DB/MI) and "up to 85%" (SQL overall); scopes differ.

Risks and decision matrix

Good fit: existing Windows Server/SQL Server core SA or subscriptions, workloads staying in Azure, instances at 8+ cores (or accepting the threshold), and a migration plan that covers the 180-day window. Poor fit: no compliant licenses, SA expiring soon, only small VMs, SQL serverless/DTU, Windows client, or a migration that cannot finish within 180 days. Seven hidden risks: the 8-core minimum, SA/subscription expiry (renew, disable AHB or deprovision), no dual running after 180 days, wrong SQL edition conversion, serverless/DTU exclusion, buying a Windows reservation instead of Linux + AHB, and license audits/true-up. 90 days: weeks 1–2 inventory Windows/SQL versions, cores, SA expiry and the 180-day window; weeks 2–4 price AHB and AHB+reservation per SKU; weeks 4–6 verify SQL edition/GP/BC conversion; weeks 6–8 enable AHB in a test subscription and reconcile the bill; weeks 8–10 run a license true-up/compliance review; weeks 10–12 decide scope on net benefit.

ScenarioRecommendationCheck first
Own SA, staying in AzureEnable AHB8-core minimum, SA expiry
Stable 1–3 yearsLinux reservation + AHBTerm, commitment
SQL DB/MIConvert by editionServerless/DTU excluded
Small VM (2–4 vCPU)Model the 8-core dilutionLicense cost vs saving
Not migrated within 180 daysBudget dual runningDeadline, rollback
No SA/subscriptionFix licensing firstDon't invent eligibility

Editorial summary, not licensing/legal advice; eligibility, rights and audits follow Microsoft Product Terms, your contract and official docs.

FAQ

What is Azure Hybrid Benefit?

It applies existing Windows Server/SQL Server core licenses (with SA or a qualifying subscription) to Azure at Linux/base rates, removing the license portion; it also covers RHEL/SLES subscriptions. It is not a discount code—compliant licenses are required.

How much can a Windows VM save?

The Windows-Linux gap for the same SKU: D4s_v5 $134.32/month, D8s_v5 $268.64, D16s_v5 $537.28 (730h). With a Linux 3-year reservation, D8s is about $110.72/month, 79.8% below Windows PAYG.

How does the 8-core minimum work?

Each Windows Server VM needs at least 8 core licenses; a 4-vCPU VM still needs 8, larger instances need licenses equal to cores, and processor licenses count as 16 cores. Small VMs dilute the per-core saving.

What is the 180-day dual-running window?

Windows/SQL AHB allows 180 days of migration during which the license can be used on-premises and in Azure; after that it is Azure-only. Put the deadline in the migration plan.

How does SQL Server AHB work?

It applies to SQL DB vCore provisioned (not serverless/DTU), SQL MI, SQL on VMs, SSIS and Arc SQL MI. Enterprise 1 core = 4 GP vCores or 1 BC vCore; Standard 1 core = 1 GP vCore, or 4 cores = 1 BC vCore. Microsoft cites 30%+ for SQL DB/MI and up to 85% for SQL overall.

Can it stack with reservations?

Yes. Buy the Linux reservation base and use AHB for Windows; Microsoft says stacking saves up to 80% vs Windows PAYG. Don't buy a Windows reservation and then add AHB—avoid double coverage.

When doesn't it apply?

Windows client, SQL serverless/DTU, no SA/subscription, expired SA, migrations that cannot finish within 180 days, or small VMs where the license dilution makes it uneconomic. Follow the Product Terms.

How do I avoid compliance risk?

Five things: (1) inventory cores and SA expiry; (2) keep license proof and allocation records; (3) track AHB resources with Azure Policy/tags; (4) renew or disable AHB before expiry; (5) run a true-up/audit drill. Don't "enable first and fix later".

Research method and limitations

Official facts (Retail API, AHB FAQ, Learn): Windows/Linux hourly rates, 1/3-year reservation totals, the 8-core Windows minimum, SQL edition conversion, 30%+ for SQL DB/MI, up to 85% for SQL overall, 180-day dual running, AHB+reservation up to 80%. Editorial calculations: 730 hours/month, reservation total ÷ 8,760/26,280, scaled by VM count; excludes SA/subscription, storage, network and tax.

Seven limitations: (1) only eastus public list prices, excluding tax/contract discounts; (2) SA/subscription cost varies by agreement and is not on the Azure bill; (3) reservation prices/availability vary by region/SKU/term; (4) no real migration/performance/license audit; (5) SQL savings vary by edition, GP/BC and region; (6) AHB+reservation stacking follows official terms; (7) licensing rules change—recheck Product Terms and contracts before purchase.

Sources and basis

Data cut-off 10 November 2026; licensing eligibility, prices and terms follow Microsoft official pages, Product Terms and contracts; this is not licensing, procurement or legal advice.

Turn Windows/SQL licences, the 8-core minimum and reservations into a checkable budget

Bring Windows/SQL versions, core counts, SA expiry, reservation terms and the 180-day migration plan; we turn AHB net benefit into a checkable budget.

Book an AHB cost review