> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Apply Azure Hybrid Benefit for Windows Server

> Use Windows Server licenses you already own on Azure VMs instead of paying for the license in the VM price.

A Windows VM on Azure normally includes the Windows Server license in its price, billed as a separate license charge. With Azure Hybrid Benefit, you bring Windows Server licenses you already own (with Software Assurance or a qualifying subscription) and that license charge goes away. nOps finds VMs billed for a Windows Server license and shows that charge as the saving.

| | |
| - | - |
| **Cloud** | Microsoft Azure |
| **Category** | Compute |
| **Service** | Virtual Machines |
| **Action** | Modify |
| **Effort** | Low |
| **Restart needed** | No |
| **Can be rolled back** | Yes |
| **Analysis window** | Last 7 days |
| **Source** | nOps |

## Why it matters

If your organization already pays for Windows Server licenses with Software Assurance, paying again for the license in Azure is a double cost. Turning on Hybrid Benefit is a setting change with no restart.

## How nOps finds it

nOps reads the last 7 days of Azure Virtual Machines billing and looks for Windows Server license lines on each VM. The saving is the license cost from your bill (net of discounts), scaled to a month. A VM is left out when its license was not billed in the last 3 days of the window, when the service is mostly paid with credits (90% or more), or when the saving is under \$5 a month. When a VM also qualifies for Azure Dev/Test pricing, nOps shows only the larger of the two, because both remove the same license charge.

## Before you start

Enough Windows Server core licenses with active Software Assurance (or qualifying subscription licenses) to cover the VM's cores, and permission to update the VM (`Microsoft.Compute/virtualMachines/write`).

## How to implement

1. Confirm with your licensing team that you have eligible Windows Server licenses for the VM's cores.
2. In the Azure portal, open the VM, go to **Configuration**, and under **Licensing** confirm you have an eligible Windows Server license. Save.
3. Or use the Azure CLI: `az vm update --resource-group RESOURCE_GROUP --name VM_NAME --license-type Windows_Server`. For a scale set, use `az vmss update ... --license-type Windows_Server` and then update the instances.
4. If the VM is managed by Terraform, Bicep or ARM templates, set `license_type` (or `licenseType`) to `Windows_Server` there too, or the next deployment can turn it off.

## Risks and considerations

* You are responsible for having the licenses. Using Hybrid Benefit without enough eligible licenses is a licensing compliance risk.
* The change takes effect without a restart.
* To roll back, set the license type back to `None`; Azure bills the license again from then on.

## FAQs

> [accordion] Does applying Hybrid Benefit restart the VM?
>
> No. It only changes how the VM is billed.

> [accordion] What if the VM is non-production?
>
> nOps may also show "Use Azure Dev/Test Pricing for Non-Production Windows VMs" for it. Both remove the same license charge, so apply one or the other.

## Related

* [Use Azure Dev/Test Pricing for Non-Production Windows VMs](https://help.nops.io/inform/supported-recommendations/use-azure-dev-test-pricing-for-non-production-windows-vms)
* [Apply Azure Hybrid Benefit for Azure SQL](https://help.nops.io/inform/supported-recommendations/apply-azure-hybrid-benefit-for-azure-sql)
* [Supported recommendations](https://help.nops.io/inform/supported-recommendations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.