I’ve already wrote about new Microsoft Azure Portal code named Ibiza. When you look this new portal, one of the first news in that now we have two menus for virtual machines:

• Virtual Machines
• Virtual Machines (classic)

You will see that all virtual machines you already created using old Azure Portal are placed in Virtual Machines (classic). I want to give you a small descriptions about difference between these two options.

The new Azure Resource Manager with a new API doesn’t uses resources as the old API. Because of that, the classic API stack is still operational, but you’ll see those resources showed up as (classic). You have not a reason to convert classic VM to the new VM. You just need to know that you cannot include classic VM in a virtual network deployed with Resource Manager and they don’t have to be included in a virtual network (unless new VMs must be included).

But if you want to migrate classic VM to the newer model, first you have to be sure you can afford a downtime for your VM. If you can afford it, than you can do it using ASM2ARM PowerShell script. You can find all details here.

I hope, I helped you. I have some more information about it and I’ll prepare a real interesting example soon.