Choosing the most appropiate Azure Virtual Machine Specification


Want to Understand Microsoft Azure Virtual Machine, specification offerings? Here a step by step guide of getting to grips with the Hardware offering available with Azure

So what are the current offering in terms of CPU, Memory and GPU vs the Hardware specification (details correct 12th Sept 2016)

The following is a high level view of Specification vs Virtual Machine Model Series


All VM sizes except the basic A-series have a temporary SSD scratch disk.

Number of Disks Supported

So what if you wanted the VM which could support the Maximum number of disks or simply wanted a machine which could supported 4 disk or 16 disks?


Or what if you wanted to Machine with the best level of IOPS for Storage do you want to compare the Uncached vs Cached?

Storage (Max IOPS)


What if you wanted to find a machine with specific RAM? Azure provides 0.768GB to 448GB

Machine Memory RAM



What if you wanted a machine with a specific number of cores? Azure supports from 1 – 32 Cores

Number of CPU Cores


So what model is best for what workload?

So as rule of thumb here a quick summary of the Azure Virtual Machine Options


Comments (4)

  1. Andy says:

    Great information, however this gets out of date very quickly.

    Is the Max IOPS available programmatically? The ‘Get-AzureRmVMSize’ cmdlet (or REST API) doesn’t report this back (only Cores, Memory, Max Disk count, OS Disk Size and Temp Disk Size).

      1. Andy Ellard says:

        I think this was misunderstood – Azure VMs are limited in total IOPS which is visible in the portal when choosing the size of your VM. It would be good to get this programmatically via PowerShell/REST.

        1. Lee Stott says:

          Hi Andy have you seen Diskspd Utility: A Robust Storage Testing Tool (superseding SQLIO) this could be useful solution

Skip to main content