Azure: unable to adjust virtual machine size beyond A0-A4

Question

I am trying to increase the size of a virtual machine on my Azure subscription from an A2 machine (2 cores, 3.5 GB) to a D3 machine (4 cores, 14 GB). The only parameters available for this virtual machine in the configuration tab> Virtual Machine Size are: - A0 - A1 - A2 - A3 - A4

I do not see the available sizes of the A5 or D3 virtual machine, although they are available for other virtual machines in my subscription. We had this and several other virtual machines with the same problem as for about a year and a half - new virtual machines in our subscription (as well as machines in the creation gallery) can be scaled in memory and processors with intensive versions (A5 or D3, D4 )

Is there any way that will allow me to upgrade this old virtual machine to a newer virtual machine specification?

Answer 1

According to the Azure MSDN article “ Virtual Machine and Cloud Service Sizes for Azure ” at: http://msdn.microsoft.com/en-us/library/azure/dn197896.aspx you cannot increase the size of the Basic Tier virtual machine to A4. Thus, it looks like you will need to use the "Standard Level".

If the option to switch to “Standard Level” is not available for this virtual machine, the explanation may be that virtual machines created before April 16, 2013 may not be able to upgrade to a size of more than A4 due to the older center the data in which they live. The article contains an explanation of this problem and a link to a troubleshooting guide for " Error:" Could not configure virtual machine "with virtual machine size A5, A6 or A7 " at: https://social.msdn.microsoft.com/Forums/ azure / en-US / 9693f56c-fcd3-4d42-850e-5e3b56c7d6be / error-failed-to-configure-virtual-machine-with-a5-a6-or-a7-vm-size? forum = WAVirtualMachinesforWindows

Answer 2

This blog article displays resized virtual machines in tables. Please note that the information on the blog may be old, but it shows that the sizes of virtual machines do not change, although they can be selected in the list.

From the blog below, the table gives an answer.

Note that the one above is “ASM” and the bottom is “ARM”.

Resizing a virtual machine is highly (or we can definitely say) dependent on the Azure infrastructure, so the only way to solve the problem is to simply create a new virtual machine.