A little more on New-AzureVM and the -InstanceSize parameter

This trick is probably known by most of you, but it is poorly documented, therefore I wanted to put it in a little spotlight for those who aren’t aware of this!

When creating Azure VM’s using the Azure portal it’s possible to select an instance size from any of the wizards.

Choosing a VM size from the legacy portal
Choosing a VM size from the legacy portal

or from the Preview portal:

Choosing a VM size from the preview portal

However, when using the New-AzureVM cmdlet as described in the New-AzureVM cmdlet page on MSDN there is no speficiation of the instancesize parameter. Instead, it is only shown in the examples at the bottom of the page! This is a bit of a downside, but forunately Corey Sanders (Group Program Manager, Microsoft Azure) posted the following comment on feedback.azure.com:

We do support these BASIC sizes in the latest PowerShell cmdlets. They are simply a new set of sizes pass in the -InstanceSize parameter as part of the VM Configuration. Here are the supported sizes we now have, with the last four being the “Basic” tier sizes:




Hope this helps.

Well Corey, as a matter of fact it does help! However since it’s not yet documented on MSDN, there’s only one way to find out if it works: give it a whirl and see what happens.
The code I’m using is:

New-AzureVM -InstanceSize “Basic_A2” -ServiceName $ServiceName -Location $Location -VNetName $VNetName -VMs $vm5

The script starts without any errors and once it finishes, the machine is created in Azure. When looking at the (legacy) portal, the VM is created indeed and in its dashboard on the right, the following is shown:

size in UI

Well… that’s easy right? Not much to it. It would be nice to have all the pricing tiers available and documented on MSDN, but for now this will do!

Not particularly Office 365, but hey… it’s just another cloud!

Leave a reply

Your email address will not be published. Required fields are marked *