Azure Hybrid Benefit explained in one sentence: you bring Windows Server, SQL Server, RHEL or SLES licences you already own to Azure and pay the base rate without the software component. Dev/Test pricing is something else: a discount for development and testing that depends on Visual Studio subscriptions. Both are licensing decisions. The Azure bill shows whether a discount was applied, not whether you are entitled to it.

What Azure Hybrid Benefit changes on the bill

A Windows VM in Azure costs compute plus a Windows licence. With Azure Hybrid Benefit (AHB) your own licence covers the Windows part, and you pay the base compute rate, which Microsoft states equals the Linux rate for the same VM. Technically AHB sets a metadata flag (licenseType); the VM does not restart. The change reaches billing with a delay of several hours.

For SQL Server, AHB replaces the licence component of the "License Included" price. For RHEL and SLES you switch from pay-as-you-go (PAYG), where Azure charges the distribution fee, to bring your own subscription (BYOS). AHB combines with Azure reservations: the reservation discounts compute, AHB the licence component.

an Azure reservation discounts itAzure Hybrid Benefit replaces itPrice of a Windows VM in AzureCompute componentWindows licence componentBase compute rate, the Linuxrate for the same VMYour own Windows Server licencewith active Software Assurance
Two components, two discounts: a reservation lowers the compute part, Azure Hybrid Benefit replaces the licence part with a licence you already own

Windows Server licensing rules

Windows Server Standard or Datacenter core licences with active Software Assurance qualify, as do qualifying subscription licences. Microsoft says both are available only through certain commercial licensing agreements. The counting rules:

  • Each VM needs at least 8 core licences, even a 4-core VM. Larger VMs need as many core licences as cores; one processor licence equals 16 core licences.
  • Standard: the licence runs either on-premises or in Azure. The exception is a one-time migration window of up to 180 days.
  • Datacenter: with per-VM licensing, simultaneous use on-premises and in Azure is allowed indefinitely; when licensing an Azure Dedicated Host, the window is 180 days.
  • AHB applies only during the Software Assurance or subscription term. When it ends, you renew, switch AHB off or deprovision the workloads.

Where anything conflicts, the Microsoft Product Terms for your licensing programme take precedence. Core licences required for your estate: the sum, over every Windows VM with AHB, of max(8, the VM's vCPU count).

SQL Server conversion by service

For Azure SQL Database, AHB applies only to the vCore model with provisioned compute, not to the DTU model and not to the serverless tier. The conversion from Microsoft's documentation:

Licence with Software AssuranceGeneral PurposeBusiness Critical
1 SQL Server Enterprise core4 vCores1 vCore
1 SQL Server Standard core1 vCore4 cores give 1 vCore

SQL Server on Azure VMs has three licence types: PAYG (licence in the price), AHUB (your licence) and DR for a free passive high-availability or disaster recovery replica. You can change the licence type only when the VM is registered with the SQL IaaS Agent extension, and only for Standard and Enterprise editions. A 180-day migration allowance applies here too.

Under an EA or a Microsoft Customer Agreement bought directly, billing administrators can manage AHB for SQL Server centrally: they assign a licence quantity to a subscription or the billing account under Cost Management + Billing, and Azure applies it hourly. Usage above the assigned quantity is billed at PAYG prices. Central management is currently not available for Windows Server or for customers buying through a CSP partner.

Linux: RHEL and SLES

Only images published by Red Hat or SUSE themselves qualify for the PAYG-to-BYOS switch. For Red Hat, your Azure account must be registered with the Red Hat Cloud Access programme. Setting licenseType to RHEL_BYOS or SLES_BYOS moves the VM to BYOS; afterwards you register it directly with the vendor so updates and licence evidence line up. If licenseType is empty, the billing model of the original image applies.

How to check whether AHB is applied

  1. Portal: the VM's Operating system page shows the AHB status. In the VM list, add the OS licensing benefit column.
  2. CLI: az vm list --query "[?licenseType=='Windows_Server']" -o table lists Windows VMs with AHB in the current subscription.
  3. Cost data: in cost details, Windows VMs with AHB carry "ImageType":"WindowsServerBYOL" in the AdditionalInfo field.
  4. Workbook: the Cost Optimization workbook in Azure Advisor shows AHB candidates for Windows, Linux and SQL under Rate optimization.

Across all subscriptions, Azure Resource Graph returns the inventory in one query, in Resource Graph Explorer or with az graph query:

Resources
| where type =~ 'microsoft.compute/virtualmachines'
| extend os = tostring(properties.storageProfile.osDisk.osType),
         size = tostring(properties.hardwareProfile.vmSize),
         licence = tostring(properties.licenseType)
| extend status = case(
    licence =~ 'Windows_Server', 'AHB Windows Server',
    licence in~ ('RHEL_BYOS', 'SLES_BYOS'), 'AHB Linux BYOS',
    licence =~ 'Windows_Client', 'Windows client licence',
    isempty(licence) or licence =~ 'None', 'no licence type set',
    'Linux PAYG via AHB')
| project subscriptionId, resourceGroup, name, os, size, licence, status
| order by os asc, status asc

For SQL Server VMs:

Resources
| where type =~ 'microsoft.sqlvirtualmachine/sqlvirtualmachines'
| project subscriptionId, resourceGroup, name,
          edition = tostring(properties.sqlImageSku),
          licence = tostring(properties.sqlServerLicenseType)

Map each VM size to its vCPU count and reconcile the result with your licence inventory.

Dev/Test pricing: development and testing, tied to Visual Studio

Microsoft offers three routes: Pay-As-You-Go Dev/Test for individuals and teams, Enterprise Dev/Test under an EA, and the Azure Plan for Dev/Test under an MCA. The offer is currently not available through CSP partners. You need an active Visual Studio Standard subscription; monthly cloud subscriptions do not qualify. User acceptance testers without a Visual Studio subscription may use Dev/Test environments. Individual subscribers also receive monthly Azure credits.

Discounts include Windows and SQL Server VMs billed at Linux rates, plus selected other services. Microsoft restricts use to developing and testing applications, with no uptime commitment; Dev/Test subscriptions carry no SLAs except for Azure DevOps and Azure Monitor. Microsoft frames the split as Dev/Test pricing for dev/test workloads and AHB for production. Keep Dev/Test in its own subscriptions so cost reports separate it from production; making non-production costs visible covers the reporting side.

productiondevelopment and testingWhat runs on the VM?Azure Hybrid BenefitDev/Test pricing, in itsown subscriptionEligible licences: at least 8 corelicences per VM, Software Assurance active,on-premises use ended or within 180 daysAn active Visual Studio Standardsubscription per user, no SLA,no productionThe bill shows the discount;the audit asks for the entitlement
Which discount for which workload: Azure Hybrid Benefit for production with eligible licences, Dev/Test pricing for development and testing with Visual Studio subscriptions; the bill shows the discount, the audit asks for the entitlement

The compliance risk: a discount without a licence

Microsoft reserves the right to audit AHB eligibility at any time. Ticking the confirmation box is your statement that you hold eligible licences; without them the Azure bill drops while the eligibility Microsoft can audit is missing. Failure points that follow from the rules above:

  • Small VMs counted at their vCPU count instead of at least 8 core licences.
  • Standard licences still running on-premises and in Azure after the 180 days.
  • Software Assurance ends while the flag stays set.
  • Templates or Terraform modules hard-code licenseType, so every new VM inherits the discount without a licence check.
  • A SQL VM recreated for an availability set falls back to PAYG, and the discount disappears unnoticed.
  • A production application runs in a Dev/Test subscription, without an SLA and outside the terms of use.

If licences are short, Microsoft lists three options: buy more, switch AHB off for some VMs, or deallocate VMs. Whether your agreements cover a deployment is for your licence management and Microsoft licensing partner to confirm; this guide is not licensing advice.

Checklist before you switch it on

CheckEvidenceOwner
Licensing programme and Software Assurance or subscription termAgreement, end date in the calendarLicence management
Core licences per VM, or vCore conversion per SQL serviceResource Graph export reconciled with the billPlatform team
On-premises use ended, or migration window with end dateDecommissioning recordPlatform team
Service and tier eligible (no serverless, no DTU)Service configurationEngineering
SQL VMs registered with the SQL IaaS Agent extensionLicence type visibleEngineering
Everyone using Dev/Test subscriptions holds an active Visual Studio subscription (acceptance testers excepted), no productionUser list, subscription purposeTeam lead
Before-and-after comparison on the same resource, region and runtimeCost reportFinance

Where Costfluent helps

Costfluent reads Azure cost data through a read-only billing connector. In cost reports you separate Dev/Test subscriptions from production and see Windows and SQL costs by subscription. A licence change you intend to make can be recorded as a savings opportunity with its estimate and tracked as open, accepted, implemented or rejected; the docs describe the workflow under Savings. Savings verification against actual cost (Custom) is Planned. Costfluent does not change licence types or check licence entitlement. See savings. Software Assurance end dates belong in the same calendar as commitments, which the monthly cloud cost review keeps.

Sources and method

Checked on 2026-10-10. Microsoft Learn: Azure Hybrid Benefit for Windows Server, Microsoft Learn: Explore Azure Hybrid Benefit for Windows VMs, Microsoft Learn: Azure Hybrid Benefit for Azure SQL Database and SQL Managed Instance, Microsoft Learn: change the licence model for a SQL VM, Microsoft Learn: centrally managed Azure Hybrid Benefit for SQL Server, Microsoft Learn: Azure Hybrid Benefit for Linux VMs, Azure Hybrid Benefit and FAQ, Azure Dev/Test pricing, Microsoft Learn: Azure Dev/Test offer, Microsoft Learn: Resource Graph starter queries, Microsoft Learn: SQL Virtual Machines REST API, Microsoft Learn: FinOps toolkit Optimization workbook. The checklist, queries and failure list are Costfluent recommendations, not licensing or legal advice; the Microsoft Product Terms for your licensing programme govern.