LearnGlossary

What is an Azure VM series?

Updated 26 October 2026 · Published by Zoorik

An Azure VM series is a group of virtual machine (VM) sizes with similar hardware and features. Each size in a series sets its virtual CPUs (vCPUs) and memory. Standard_D4s_v5 is one size in the Dsv5 series.

Azure VM families sit one level up. Microsoft groups them into types, including:

  • General purpose (such as B and D): balanced CPU and memory.
  • Compute optimized (F family): more CPU for each GiB.
  • Memory optimized (such as E and M): more memory for each vCPU.
  • Storage optimized (L family): high disk throughput.

The Azure VM size naming convention

Read Standard_D4s_v5 left to right:

  • D is the family.
  • 4 is its vCPU count.
  • s means it can use any Premium SSD type.
  • v5 is the series version.

Other lowercase letters add features. An “a” means AMD, a “p” means Arm, and a “d” adds a local temporary disk.

No CPU letter usually means Intel x86-64, as on Dsv5. The HB series runs on AMD EPYC without one.

The memory optimized Standard_E4s_v5 has the same 4 vCPUs but 32 GiB of memory, not 16.

Same 4 vCPUs, twice the memory Microsoft's sizes, drawn as two bars on one shared memory scale from 0 to 32 GiB, with ticks at 0, 16 GiB and 32 GiB. Each bar has 4 segments, one per vCPU. Standard_D4s_v5, general purpose, 4 vCPUs, 16 GiB: its bar ends at 16 GiB, and a bracket under one segment reads 4 GiB per vCPU. Standard_E4s_v5, memory optimized, 4 vCPUs, 32 GiB: its bar ends at 32 GiB, and a bracket under one segment reads 8 GiB per vCPU. A dashed line at 16 GiB shows the Standard_D4s_v5 bar ends where the Standard_E4s_v5 bar is half full. Same 4 vCPUs, twice the memory 016 GiB32 GiBStandard_D4s_v5General purpose4 vCPUs, 16 GiB4 GiB per vCPUStandard_E4s_v5Memory optimized4 vCPUs, 32 GiB8 GiB per vCPU
Microsoft’s sizes, drawn to scale: each segment is one vCPU and the memory that comes with it, 4 GiB on Standard_D4s_v5 and 8 GiB on Standard_E4s_v5.

Why it matters for your cloud cost

  • Your VM series in Azure sets the memory you get with each vCPU.
  • If it doesn’t fit your workload, CPU or memory sits idle.
  • Esv5 has no temp disk, which Microsoft says reduces its entry price.
  • Disks are charged separately from VMs.
  • Check real use before you change a node pool’s VM size.

The free assessment works out what your clusters and disks could save.

Find your own number

One line in your cloud console. One PDF report with your estimated saving at list price.

Estimate your saving

Talk to the builders

Thirty minutes with the people who build Coral and Amoeba.

Book a demo (opens in a new tab)

Or write to founders@zoorik.com