Skip to main content
When Ultra Disk compatibility is turned on for a VM, Azure bills a reservation charge per vCPU for as long as no Ultra disk is attached. The setting is often turned on for testing or left behind after an Ultra disk is removed. nOps finds VMs paying this reservation charge and estimates the saving from turning the setting off.

Why it matters

The charge buys nothing while no Ultra disk is attached, and it scales with the size of the VM.

How nOps finds it

nOps reads your Azure VM billing. A VM is flagged when it was billed for the Ultra Disk vCPU reservation since at least the start of the last 7 days, and still in the last 2 days. Azure bills this charge only when Ultra Disk compatibility is on and no Ultra disk is attached. The saving is the reservation charge over the last 7 days, net of discounts and scaled to a month, and must be at least $2 a month.

Before you start

Permission to change the VM (for example Virtual Machine Contributor), and a time when it can be stopped.

How to implement

  1. Confirm no Ultra disk is planned for the VM.
  2. Stop (deallocate) the VM.
  3. In the Azure portal, open the VM, go to Disks → Additional settings and set Enable Ultra disk compatibility to No, or run az vm update --resource-group MY_RG --name MY_VM --ultra-ssd-enabled false.
  4. Start the VM.
  5. Update Terraform, Bicep or ARM templates so the setting is not turned back on.

Risks and considerations

  • The change needs the VM to be deallocated, so plan a short downtime.
  • To roll back, deallocate the VM again and turn the setting back on.