Hi, just a brief post for those of you that are wondering why Azure backup (at time of publishing this post, Feb 2016!) cannot discovery your IaaS (Infrastructure as a Service) virtual machines you may have created within the same region but on the V2 portal – https://portal.azure.com/
Over the last few months I have been spending a bit of time setting up some labs in Azure both in the “classic” portal and the “v2” portal as Microsoft calls it. The difference being the classic portal is the old fashion (and in my opinion easy to use) portal, while the v2 portal is where all the new development and features are. Microsoft’s best practise is to try and ensure you are using the new v2 portal for all you IaaS build outs but the issue here is backwards compatibility.
So the use case – I have created a new IaaS environment within the v2 portal using Resource Manager and would like to use Azure’s VM Backup service, i.e. adding a new Recovery service and backup fault (which of course has to be in the same region) and discovery the virtual machines to carry out the backup – NOTE: this is different to the file level backup where you download the Azure Backup agent and carry our file level backups and restores.
It turns out that you will be presented with the below error, the reason for this (and confirmed with Microsoft support) is this functionality is not currently supported!!!
Yes I know, no notifications or advisory notes when you create these virtual machines nothing it simply does not work. THE ONLY way to backup virtual machines in Azure with the Azure backup / recovery services is to carry on building your IaaS environment in the classic portal, end of – check this for more details – https://feedback.azure.com/forums/258995-azure-backup-and-scdpm/suggestions/8369907-azure-backup-to-support-iaas-vm-v2