> ## 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.

# Use Azure Dev/Test Pricing for Non-Production Windows VMs

> Run non-production Windows VMs in an Azure Dev/Test subscription, where they are billed at Linux rates.

In an Azure Dev/Test subscription, Windows VMs do not pay the Windows Server license charge, so they cost the same as Linux VMs. nOps finds non-production Windows VMs that pay that license charge and shows it as the saving. It also shows how much of the VM's subscription is non-production, which tells you whether the whole subscription could move to the Dev/Test offer.

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

## Why it matters

The Windows license is a large part of a Windows VM's price, and it is not needed for development and test.

## How nOps finds it

nOps reads the last 14 days of Azure VM and scale set billing for Windows Server license lines. A VM is flagged when it paid the license on at least 7 of those days, was billed in the last 2 days, and at least 90% of its cost is non-production (from its environment tag, then the environment nOps assigns, then the resource group name). The saving is the license cost from the last 7 days, scaled to a month. Services mostly paid with credits and savings under \$25 a month are left out. When a VM also qualifies for Azure Hybrid Benefit, nOps shows only the larger of the two, and the saving is shown after any scheduling saving for the same VM.

## Before you start

An Azure Dev/Test offer (Enterprise Dev/Test or Pay-As-You-Go Dev/Test). Every person who uses the Dev/Test subscription needs an active Visual Studio subscription.

## How to implement

1. Check that everyone who uses the VM has a Visual Studio subscription, and that it runs only development or test work.
2. If the recommendation says the subscription is mostly non-production, ask your enterprise or billing admin about moving the subscription itself to the Dev/Test offer.
3. Otherwise, create a Dev/Test subscription and move the VM and its resources into it (portal: resource group → **Move → Move to another subscription**, or `az resource move`).
4. Update Terraform, Bicep or ARM templates and pipelines with the new subscription.

## Risks and considerations

* Dev/Test subscriptions have no financially backed SLA and may only run development and test workloads.
* Moving resources between subscriptions locks the source and target resource groups during the move, and some resource types cannot be moved.
* If the VM is also scheduled to run only during working hours, the license saving shrinks with its running hours.
* To roll back, move the resources back to the original subscription.

## FAQs

> [accordion] Can I use this and Azure Hybrid Benefit together?
>
> No. Both remove the same Windows license charge, so nOps shows only the larger one for a VM.

## Related

* [Apply Azure Hybrid Benefit for Windows Server](https://help.nops.io/inform/supported-recommendations/apply-azure-hybrid-benefit-for-windows-server)
* [Schedule Non-Production Azure VMs](https://help.nops.io/inform/supported-recommendations/schedule-non-production-azure-vms)
* [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.