M-series

Caution

This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly. For more information, see the CentOS End Of Life guidance.

Applies to: ✔️ Linux VMs ✔️ Windows VMs ✔️ Flexible scale sets ✔️ Uniform scale sets

The M-series offers a high vCPU count (up to 128 vCPUs) and a large amount of memory (up to 3.8 TiB). It's also ideal for extremely large databases or other applications that benefit from high vCPU counts and large amounts of memory. M-series sizes are supported both on the Intel® Xeon® CPU E7-8890 v3 @ 2.50GHz and on the Intel® Xeon® Platinum 8280M (Cascade Lake).

M-series VM's feature Intel® Hyper-Threading Technology.

ACU: 160-180
Premium Storage: Supported
Premium Storage caching: Supported
Live Migration: Restricted Support
Memory Preserving Updates: Not Supported
VM Generation Support: Generation 1 and 2
Write Accelerator: Supported
Accelerated Networking: Supported
Ephemeral OS Disks: Supported
Nested Virtualization: Supported

Size vCPU Memory: GiB Temp storage (SSD) GiB Max data disks Max cached and temp storage throughput: IOPS/MBps (cache size in GiB) Burst cached and temp storage throughput: IOPS/MBps4 Max uncached disk throughput: IOPS/MBps Burst uncached disk throughput: IOPS/MBps4 Max NICs Expected network bandwidth (Mbps)
Standard_M8ms 3 8 218.75 256 8 10000/100 (793) 10000/250 5000/125 10000/250 4 2000
Standard_M16ms 3 16 437.5 512 16 20000/200 (1587) 20000/500 10000/250 20000/500 8 4000
Standard_M32ts 32 192 1024 32 40000/400 (3174) 40000/1000 20000/500 40000/1000 8 8000
Standard_M32ls 32 256 1024 32 40000/400 (3174) 40000/1000 20000/500 40000/1000 8 8000
Standard_M32ms 3 32 875 1024 32 40000/400 (3174) 40000/1000 20000/500 40000/1000 8 8000
Standard_M64s 1 64 1024 2048 64 80000/800 (6348) 80000/2000 40000/1000 80000/2000 8 16000
Standard_M64ls 1 64 512 2048 64 80000/800 (6348) 80000/2000 40000/1000 80000/2000 8 16000
Standard_M64ms 1,3 64 1792 2048 64 80000/800 (6348) 80000/2000 40000/1000 80000/2000 8 16000
Standard_M128s 1 128 2048 4096 64 160000/1600 (12696) 250000/4000 80000/2000 80000/4000 8 30000
Standard_M128ms 1,2,3 128 3892 4096 64 160000/1600 (12696) 250000/4000 80000/2000 80000/4000 8 30000
Standard_M64 1 64 1024 7168 64 80000/800 (1228) 80000/2000 40000/1000 80000/2000 8 16000
Standard_M64m 1 64 1792 7168 64 80000/800 (1228) 80000/2000 40000/1000 80000/2000 8 16000
Standard_M128 1 128 2048 14336 64 250000/1600 (2456) 250000/4000 80000/2000 80000/4000 8 32000
Standard_M128m 1 128 3892 14336 64 250000/1600 (2456) 250000/4000 80000/2000 80000/4000 8 32000

1 More than 64 vCPU's require one of these supported guest versions: Windows Server 2016, Ubuntu 18.04+ LTS, SLES 12 SP2+, Red Hat Enterprise Linux 7/8/9, CentOS 7.3+ or Oracle Linux 7.3+ with LIS 4.2.1 or higher.

2 Instance is isolated to hardware dedicated to a single customer.

3 Constrained core sizes available.

4 M-series VMs can burst their disk performance for up to 30 minutes at a time.

Size table definitions

  • Storage capacity is shown in units of GiB or 1024^3 bytes. When you compare disks measured in GB (1000^3 bytes) to disks measured in GiB (1024^3) remember that capacity numbers given in GiB may appear smaller. For example, 1023 GiB = 1098.4 GB.

  • Disk throughput is measured in input/output operations per second (IOPS) and MBps where MBps = 10^6 bytes/sec.

  • Data disks can operate in cached or uncached modes. For cached data disk operation, the host cache mode is set to ReadOnly or ReadWrite. For uncached data disk operation, the host cache mode is set to None.

  • To learn how to get the best storage performance for your VMs, see Virtual machine and disk performance.

  • Expected network bandwidth is the maximum aggregated bandwidth allocated per VM type across all NICs, for all destinations. For more information, see Virtual machine network bandwidth.

    Upper limits aren't guaranteed. Limits offer guidance for selecting the right VM type for the intended application. Actual network performance will depend on several factors including network congestion, application loads, and network settings. For information on optimizing network throughput, see Optimize network throughput for Azure virtual machines. To achieve the expected network performance on Linux or Windows, you may need to select a specific version or optimize your VM. For more information, see Bandwidth/Throughput testing (NTTTCP).

Other sizes and information

Pricing Calculator: Pricing Calculator

More information on Disks Types : Disk Types

Next steps

Learn more about how Azure compute units (ACU) can help you compare compute performance across Azure SKUs.