Cost

Apply Azure Hybrid Benefit to VMs and SQL

One capability across Windows VMs, Linux VMs and Azure SQL: stop paying Azure a second time for licences you already own, by reusing your Software Assurance, RHEL and SUSE entitlements to drop the licence component out of compute you are already running.

14 min·10 sections·AZURE

Last reviewed 18 June 2026

Azure Hybrid Benefit: the basics

What are you actually paying twice for?

When you run a Windows or SQL Server workload in Azure at the pay-as-you-go rate, the meter bundles two things together: the compute you consume and a Microsoft licence baked into the hourly price. If your organisation already holds Windows Server, SQL Server or Red Hat and SUSE entitlements on the side, through Software Assurance, a qualifying subscription or a cloud-access programme, you are paying for that licence a second time inside the Azure bill. Azure Hybrid Benefit is the switch that says 'apply the licence I already own', so the meter drops to a base compute rate and stops charging you for software you have already bought.

It is the same capability expressed in three places. A Windows VM carries a 'licenseType' of 'Windows_Server' when the benefit is on, and 'None' or empty when it is not. A Linux VM carries 'RHEL_BYOS' or 'SLES_BYOS' to move from a pay-as-you-go image to bring-your-own-subscription billing. Azure SQL Database and SQL Managed Instance carry a 'licenseType' of 'BasePrice' when the benefit is on and 'LicenseIncluded' when Azure is selling you a fresh licence. Different resource types, different field values, one decision: am I renting a licence I already own?

Most of the missed saving here is drift, not a deliberate choice. A VM deployed from a marketplace image that defaulted to pay-as-you-go, a SQL database created with 'LicenseIncluded' because nobody set the flag, a Linux fleet still on metered images after the team bought Red Hat subscriptions. The work is to find every eligible resource still paying the licence-included rate, confirm you hold the underlying entitlements, and flip the switch, which Microsoft applies with no redeploy and no downtime.

In this lesson you will learn how Azure expresses the Hybrid Benefit across Windows VMs, Linux VMs, Azure SQL Database and SQL Managed Instance, how to find every eligible resource still paying the licence-included rate, and how to flip the benefit on safely without downtime or breaking licence rules. You will see the Azure Advisor signal, the az CLI to inventory and remediate, and a Bicep pattern that makes the benefit the default on new compute.

Fun fact

The discount most estates forget to claim

Azure Hybrid Benefit is widely described as one of the most under-used cost levers in Azure, precisely because nothing breaks when you ignore it. A pay-as-you-go Windows VM runs exactly the same whether the benefit is on or off; the only difference is the hourly rate. So a fleet can run for years quietly paying the licence-included price while the matching Software Assurance sits on a shelf in the procurement system. Microsoft now lets you apply the benefit with no redeploy and no restart, and even centrally manage it across a billing scope, which means the gap between 'eligible' and 'claimed' is usually just a setting nobody flipped.

Finding unclaimed Hybrid Benefit across a subscription

Priya runs the platform team at a company that recently signed an Enterprise Agreement with Software Assurance. Azure Advisor is flagging Hybrid Benefit opportunities, and the Windows and SQL lines on the bill look high for the size of the fleet.

Rather than guess, Priya starts by listing which Windows VMs are still running at the pay-as-you-go licence rate, so the eligible resources can be separated from the ones already on the benefit before anything changes.

Start by listing Windows VMs whose licence type is not yet 'Windows_Server'. These are still paying for a licence you may already own.

$ az vm list --query "[?storageProfile.osDisk.osType=='Windows'].{name:name, license:licenseType}" -o table

Name License

---------------- --------------

app-prod-01 None

app-prod-02 None

db-reporting-01 Windows_Server

# app-prod-01 and app-prod-02 still pay the licence-included rate. db-reporting-01 already claims the benefit.

A Windows VM with a licence type of 'None' is paying Azure for a Windows Server licence. If you hold Software Assurance, that is recoverable spend on the next billing cycle.

How Azure Hybrid Benefit changes what you are billeddeep dive

The benefit is a single field per resource that switches the meter from a licence-included rate to a base compute rate. On a Windows VM it is 'licenseType': set it to 'Windows_Server' and the hourly price drops to the rate that excludes the Windows Server licence. On a Linux VM the same field takes 'RHEL_BYOS' or 'SLES_BYOS', moving the VM from a pay-as-you-go image to bring-your-own-subscription billing so you pay only for infrastructure and bring your Red Hat or SUSE subscription. On Azure SQL Database and SQL Managed Instance the field is also 'licenseType', with 'BasePrice' meaning the Hybrid Benefit discount is applied and 'LicenseIncluded' meaning Azure is selling you a new SQL Server licence in the price.

Crucially, the change is metadata, not infrastructure. Microsoft documents that switching the licence type does not restart the VM and does not interrupt service, and that enabling the benefit on Azure SQL requires no downtime. The compute keeps running on exactly the same hardware; only the rate the meter applies changes. That is why the saving appears on the next billing cycle rather than after any migration, and why the change is fully reversible by setting the field back.

The constraints are licensing rules, not technical ones. Microsoft requires a minimum of eight core licences per VM for Windows Server even on smaller instances, the underlying entitlements must carry active Software Assurance or be qualifying subscriptions, and Linux bring-your-own-subscription requires the account to be registered with the relevant Red Hat or SUSE programme. SQL Server Hybrid Benefit maps core licences to vCores under documented ratios. The technical switch is trivial; the discipline is confirming you hold enough of the right licences before you claim the benefit against a given resource.

What is the impact of leaving Hybrid Benefit unclaimed?

The direct impact is paying for the same Microsoft licence twice. Every eligible Windows VM, Linux VM or Azure SQL resource left at the licence-included rate, while the organisation holds matching Software Assurance or subscriptions, is buying that licence both inside the Azure meter and through the agreement. Microsoft documents the gap as an average of 36 percent on Windows Server and up to 30 percent or more on Azure SQL Database and Managed Instance, so on a large fleet the unclaimed amount is substantial and it recurs every month it goes unclaimed.

The second-order impact is compounding waste. Because nothing breaks when the benefit is off, an unclaimed estate keeps overpaying quietly, and the overpayment grows as the fleet grows. New VMs deployed from default marketplace images and new databases created with 'LicenseIncluded' add to the gap unless someone remembers to set the flag, so the leak widens over time rather than holding steady.

The opportunity cost is the sharpest impact. Hybrid Benefit is reversible, downtime-free and requires no new purchase, so the money it recovers is the cheapest budget the platform team can find. Leaving it unclaimed means funding genuinely risky or genuinely new work out of new budget while a no-risk recovery sits unused on the bill.

How do you claim Hybrid Benefit safely?

Work the capability as one loop rather than chasing individual resources. The order matters: confirm what you own before you claim it, so you stay inside the licence rules.

1. Confirm entitlement coverage first

Before flipping any switch, establish how many Windows Server and SQL Server core licences with active Software Assurance the organisation holds, and which Red Hat or SUSE subscriptions are registered for cloud use. The benefit may only be applied to cores you are entitled to, with a minimum of eight core licences per Windows VM, so coverage is the real constraint, not the technical change.

2. Inventory every eligible resource still on the metered rate

List the Windows VMs with a licence type other than 'Windows_Server', the Linux VMs not yet on 'RHEL_BYOS' or 'SLES_BYOS', and the Azure SQL Database and Managed Instance resources still on 'LicenseIncluded'. Azure Advisor and the Cost Optimization workbook surface these opportunities directly; treat that list as the recoverable spend.

3. Claim the benefit, largest spend first

Set the licence type on each covered resource: 'Windows_Server' on Windows VMs, the matching BYOS value on Linux VMs, and 'BasePrice' on SQL Database and Managed Instance. The change takes effect with no restart and no downtime, and the saving appears on the next billing cycle. Prioritise the largest, longest-running resources, where the recovery is biggest.

4. Make the benefit the default on new compute

Bake 'licenseType' into your Bicep and Terraform modules so every new eligible VM and SQL resource claims the benefit at deployment, and consider centrally managed Hybrid Benefit at the billing-scope level for SQL so coverage is allocated automatically. This stops the gap reopening as the estate grows.

# Claim Hybrid Benefit on every Windows VM not yet on the benefit.
# No restart, no downtime: only the billed rate changes.
for vm in $(az vm list \
    --query "[?storageProfile.osDisk.osType=='Windows' && licenseType!='Windows_Server'].name" \
    -o tsv); do
  rg=$(az vm show --name "$vm" --query resourceGroup -o tsv 2>/dev/null \
       || az vm list --query "[?name=='$vm'].resourceGroup" -o tsv)
  az vm update --resource-group "$rg" --name "$vm" \
    --set licenseType=Windows_Server
  echo "$vm: Hybrid Benefit applied (Windows_Server)"
done

# Apply the SQL Server Hybrid Benefit to an Azure SQL Database.
az sql db update \
  --resource-group myResourceGroup \
  --server myServer \
  --name myDatabase \
  --license-type BasePrice

# Make it the default on new Windows compute (Bicep):
#   resource vm 'Microsoft.Compute/virtualMachines@2024-07-01' = {
#     name: vmName
#     location: location
#     properties: {
#       licenseType: 'Windows_Server'
#       // ...hardwareProfile, storageProfile, osProfile, networkProfile
#     }
#   }

Quick quiz

Question 1 of 5

A Windows VM in Azure shows a 'licenseType' of 'None' and the organisation holds Windows Server Software Assurance. What does that combination mean?

Keep learning

Go deeper on how Azure Hybrid Benefit applies across each compute type in this capability.

You can now treat Azure Hybrid Benefit as one capability rather than three separate flags: confirm what licences you own, inventory every eligible Windows VM, Linux VM and Azure SQL resource still on the metered rate, claim the benefit largest spend first with no downtime, and make it the default on new compute so the recovery sticks. It is the same decision everywhere: stop renting a licence you already own.

Back to the library

Azure Hybrid Benefit: the savings view

A no-risk discount you have already paid for, sitting unclaimed on the bill

This is the rare cost lever where the saving is large, the change is reversible, and the only prerequisite is an entitlement you already own. Microsoft documents that Windows Server customers save an average of 36 percent against pay-as-you-go, up to 76 percent when the benefit is combined with Linux, and up to 30 percent or more on Azure SQL Database and SQL Managed Instance. Stacked with a reservation, Windows Server can reach up to 80 percent off the standard pay-as-you-go rate. None of that requires buying anything new: it reuses licences your organisation has already purchased.

Frame it as recovering money the business is already spending twice. If you hold Software Assurance for SQL Server and also run SQL on Azure at the 'LicenseIncluded' rate, you are buying the same licence in two ledgers. The finance job is to size the unclaimed benefit across the eligible estate, confirm there are enough licences to cover the cores in use, and treat the gap as recoverable spend rather than a new project to fund.

The trade is one-sided in the direction finance likes. Turning the benefit on costs nothing, takes effect without downtime, and is reversible by flipping the field back. The only real constraints are entitlement coverage, you must own enough licences for the cores you apply it to, and a few licence rules such as the minimum core counts and dual-use windows. The payback is immediate: the saving lands on the next billing cycle, not after a migration.

This lesson is for the finance partner who can see Windows and SQL spend on the Azure bill and wants to know how much of it is licence cost the business is already paying for elsewhere. It covers how to size the unclaimed benefit, what entitlement coverage you have to confirm before claiming it, and why this is recoverable spend rather than a project to fund.

Fun fact

The discount most estates forget to claim

How a finance partner sizes the unclaimed benefit

Priya is the finance partner supporting a platform team that has just moved onto an Enterprise Agreement with Software Assurance. The Windows and SQL lines on the Azure bill look heavy, and Advisor is flagging Hybrid Benefit opportunities. The instinct is not to wave through a savings target; it is to size what is actually recoverable. Priya asks for two numbers: how many Windows and SQL cores are running at the licence-included rate, and how many matching licences the organisation already holds under Software Assurance.

The answer reframes the bill. A meaningful slice of the Windows VM spend and the Azure SQL spend turns out to be licence cost the business is also paying for through its EA. Microsoft's own figures, an average 36 percent saving on Windows Server and up to 30 percent or more on SQL Database and Managed Instance, give a defensible estimate for the finance pack: 'A double-digit percentage of our Windows and SQL spend is licence cost we already own elsewhere. Claiming Hybrid Benefit recovers it on the next cycle, at no cost, with no downtime, limited only by how many licences we hold.' The work becomes confirming entitlement coverage, not funding a project.

Why unclaimed Hybrid Benefit belongs on the savings register

The economics here are unusually clean. The saving is documented by Microsoft, the change costs nothing to make, it lands on the next billing cycle, and it is reversible. The only ceiling is entitlement coverage: you can apply the benefit to as many cores as you hold licences for. That makes the unclaimed amount a concrete, sizeable number rather than a speculative target, and it is recoverable spend, not a project to fund.

Set against that, the cost of inaction is simply continuing to pay the licence-included rate every month. There is no breach risk, no SLA exposure and no architectural debt being created, just money spent twice. The finance role is to size the gap against actual licence holdings, claim it on the fleet that is covered today, and then make sure new deployments default to the benefit so the gap does not quietly reopen as the estate grows.

What finance can do about unclaimed Hybrid Benefit

Finance cannot set a licence type, but it owns the framing that turns an Advisor flag into a sized, defensible recovery limited only by what the business already owns. Three levers.

1. Reconcile Azure licence spend against owned entitlements

Pull the Windows and SQL cores running at the licence-included rate and set them against the Software Assurance and subscription licences the organisation holds. The gap, cores running on Azure that are covered by an owned licence, is the recoverable amount. Using Microsoft's documented figures (around 36 percent on Windows Server, up to 30 percent or more on SQL PaaS), turn that gap into a credible monthly saving for the forecast.

2. Treat it as recovery, not a project to fund

Because the change costs nothing, needs no downtime and lands on the next billing cycle, this is not a capital request, it is money already being spent twice. Book the saving against the fleet that is covered today and make clear the only constraint is licence coverage, not budget or engineering capacity, so the recovery is not held up waiting for a programme to be approved.

3. Watch the entitlement ceiling and the dual-use rules

The benefit only applies to as many cores as you hold licences for, with minimum core counts per VM and documented vCore ratios for SQL. Track claimed cores against owned licences so the estate stays inside the rules, and note any dual-use windows where a licence covers both on-premises and Azure during a migration. The recovery is real, but it is bounded by entitlement, and finance owns keeping that ledger honest.

Quick quiz

Question 1 of 5

Advisor is flagging Hybrid Benefit opportunities and the Windows and SQL bill looks high. As the finance partner, what is the right way to size the recovery?

Keep learning

Go deeper on how Azure Hybrid Benefit applies across each compute type in this capability.

You have finished the finance view of Azure Hybrid Benefit. You know it is recovery, not a project: the saving is Microsoft-documented (around 36 percent on Windows Server, up to 30 percent or more on SQL PaaS), it costs nothing, it lands on the next billing cycle, and the only ceiling is the licences you already hold. Next time Advisor flags it, you will size the covered gap against owned entitlements, book it as recoverable spend, and keep a ledger of claimed cores so the estate stays within the rules.

Back to the library

Azure Hybrid Benefit: the headline

Whether the estate is paying for Microsoft licences twice

Azure Hybrid Benefit is one of the largest single discounts Microsoft offers, and unlike most cost work it carries no architectural risk. Every Windows or SQL workload running at the licence-included rate, while the organisation holds Software Assurance on the side, is a line where the business is paying for the same licence twice. Multiplied across an estate, that is a material and entirely recoverable number.

The leadership question is not 'should we run a cost-cutting programme?' It is 'are we already entitled to a discount we have not switched on?' For most organisations with an Enterprise Agreement or Software Assurance, the answer is yes, and the recovery is a configuration change rather than a re-platforming exercise. Azure Advisor and the Cost Optimization workbook surface exactly which resources qualify.

Because the change is reversible and downtime-free, this is a fast, low-controversy win that frees budget for work that does carry risk. The only governance need is to confirm licence coverage so the benefit is claimed within the rules, and to make claiming it the default on new deployments rather than something the team has to remember.

A short read for the leader who needs to know what Azure Hybrid Benefit is, why leaving it unclaimed means paying for Microsoft licences twice, and why switching it on is a fast, reversible, low-risk win rather than a budget request.

Fun fact

The discount most estates forget to claim

What it looks like when the benefit is claimed by default, not by luck

After a cost review showed the Azure bill climbing faster than the fleet was growing, the CFO asked the obvious question: are we getting the discounts we are entitled to? The honest answer at the time was that it depended on whether each team had remembered to set a flag when they deployed, because Hybrid Benefit across the estate was governed by habit rather than policy, and several large Windows and SQL workloads were still paying the licence-included rate while Software Assurance sat unused.

The team's response was to stop treating Hybrid Benefit as a per-resource afterthought and start treating it as a default. They listed every eligible Windows VM, Linux VM and Azure SQL resource still on the metered rate, confirmed licence coverage with procurement, flipped the benefit on across the fleet with no downtime, and then made 'Hybrid Benefit on' the default in their Bicep modules so new compute claims it automatically. The next time the CFO asked, the answer had changed from 'we think so' to 'yes, the licences we own are applied across the estate, it is the default on new compute, and we can show the recovered spend on the bill.' That shift, from leaving an owned discount on the table to claiming it by design, is the win this capability delivers, and it costs nothing to reach.

Why this is a board-level saving, not a board-level risk

Most cost work asks leadership to accept some risk in exchange for savings. This one does not. Azure Hybrid Benefit recovers spend the business is already committed to elsewhere, with no downtime, no re-platforming and no architectural trade-off, limited only by the licences the organisation already owns. On a Windows and SQL estate of any size, that is a fast and material recovery.

The leadership decision is therefore not whether to take a risk but whether to bother claiming an entitlement already paid for. The answer is plainly yes, and the only governance need is to confirm licence coverage and make the benefit the default on new compute so the recovery sticks. This is the rare case where the saving is large and the risk is essentially zero, which makes it the first lever to pull, not the last.

The leadership move on Hybrid Benefit

The executive handle is not to approve each switch individually; it is to require that owned entitlements are claimed across the estate and that new compute defaults to the benefit, on the record.

1. Set a deadline to claim what is already owned

Ask for a date by which every eligible Windows VM, Linux VM and Azure SQL resource covered by an owned licence is on the benefit, with the recovered spend visible on the bill. Because the change is downtime-free and reversible, there is no operational reason for it to be slow; the only gating item is confirming licence coverage with procurement.

2. Make the benefit the default, not a reminder

A one-off sweep recovers today's gap; defaulting the benefit in deployment templates and using centrally managed Hybrid Benefit for SQL stops it reopening as the estate grows. Ask for the saving to be locked in by design so new VMs and databases claim the benefit automatically rather than relying on each engineer to remember a flag.

3. Govern entitlement, not architecture

The only risk to manage here is claiming more benefit than the organisation is licensed for. Ask for a simple, maintained reconciliation between claimed cores and owned licences so the estate stays compliant. There is no architectural decision to make, just an entitlement ledger to keep honest, which is the price of a large, no-risk recovery.

Quick quiz

Question 1 of 5

At a cost review you ask whether the estate is claiming the discounts it is entitled to. What end state should you be looking for as the defensible answer?

Keep learning

Go deeper on how Azure Hybrid Benefit applies across each compute type in this capability.

Two takeaways. Hybrid Benefit is the rare cost lever with a large, documented saving and essentially zero risk, so it is the first budget to recover, not the last. And the defensible end state is not 'we turned it on for a few VMs'; it is owned entitlements claimed across the estate, the benefit defaulted on new compute, and a simple reconciliation between claimed cores and owned licences so the recovery is locked in and compliant.

Back to the library

Part of the learning path Lock in Azure commitments

Apply Azure Hybrid Benefit to VMs and SQL

Azure Hybrid Benefit: the basics

The discount most estates forget to claim

Finding unclaimed Hybrid Benefit across a subscription

How Azure Hybrid Benefit changes what you are billeddeep dive

What is the impact of leaving Hybrid Benefit unclaimed?

How do you claim Hybrid Benefit safely?

1. Confirm entitlement coverage first

2. Inventory every eligible resource still on the metered rate

3. Claim the benefit, largest spend first

4. Make the benefit the default on new compute

Quick quiz

Keep learning

Azure Hybrid Benefit: the savings view

The discount most estates forget to claim

How a finance partner sizes the unclaimed benefit

Why unclaimed Hybrid Benefit belongs on the savings register

What finance can do about unclaimed Hybrid Benefit

1. Reconcile Azure licence spend against owned entitlements

2. Treat it as recovery, not a project to fund

3. Watch the entitlement ceiling and the dual-use rules

Quick quiz

Keep learning

Azure Hybrid Benefit: the headline

The discount most estates forget to claim

What it looks like when the benefit is claimed by default, not by luck

Why this is a board-level saving, not a board-level risk

The leadership move on Hybrid Benefit

1. Set a deadline to claim what is already owned

2. Make the benefit the default, not a reminder

3. Govern entitlement, not architecture

Quick quiz

Keep learning

Related cost lessons