Skip to main content
Azure offers most general-purpose and memory-optimized VM sizes on both Intel and AMD processors. The AMD sizes (Das v5 and Eas v5, or Dads v5 and Eads v5 with a local temp disk) have the same vCPU and memory and a lower list price. nOps finds Intel D and E series v3, v4 and v5 VMs on pay-as-you-go and estimates the saving from resizing them to the AMD equivalent.

Why it matters

It is a same-size move with no change to the VM’s capacity, and the price difference applies to every hour it runs.

How nOps finds it

nOps reads the last 14 days of Azure VM and scale set billing. A VM is flagged when it ran on pay-as-you-go on at least 7 of those days, was billed in the last 2 days, and is not mostly covered by reservations. Its 7-day pay-as-you-go compute cost, scaled to a month, is multiplied by the difference between the current size’s list price and the AMD size’s list price in the same region and operating system. The AMD size must be at least 3% cheaper, the service must not be mostly paid with credits, and the saving must be at least $5 a month. When moving a v3 VM to the current Intel series would be cheaper, nOps shows that recommendation instead, and only one resize recommendation is shown for a VM.

Before you start

Permission to resize the VM, and a maintenance window: resizing restarts it.

How to implement

  1. Check the target size shown in the recommendation. Use the d variant (for example Dads v5) if the VM keeps data on its local temp disk.
  2. Check the target size is offered in the VM’s region and availability zone.
  3. Resize the VM (portal: VM → Size, or az vm resize --resource-group RESOURCE_GROUP --name VM_NAME --size Standard_D4as_v5). For a scale set, change its size and update the instances.
  4. Update Terraform, Bicep or ARM templates so a later deployment does not change it back.

Risks and considerations

  • Resizing restarts the VM. Data on the temporary disk is lost.
  • Software licensed or tuned for a specific processor may need checking on AMD.
  • Reservations for the Intel size may not cover the AMD size unless instance size flexibility applies to both.
  • To roll back, resize back to the original size.

FAQs

The AMD size has the same vCPU and memory. Most workloads behave the same; test anything sensitive to processor type first.