This happens when the wrong generation is chosen when exporting a Virtual Machine to Azure.
The recovery point in the following image is from a Gen1 evidenced by the System Reserved Volume. Generation 2 will show a UEFI volume.
If Generation 2 option is selected, the task will continue without any errors or warnings.
Also, the deployment will succeed.
The deployed VM won't boot the Operating System. Running Azure Boot Diagnostics confirms the scenario.
The best approach in this situation is to follow the steps below to avoid running the export job again.
1. Delete the deployed VM from Azure.
2. Create a Managed Disk resource using source type blob storage and browse for the VHD file still located in the "deploy" container.
3. This time, make sure to select Generation 1. Also, select the size of your preference.
4. Go to your new Managed Disk Resource and use the Option Create VM.
5. Run again boot Diagnostics and the VM should load the OS correctly this time.
© ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz Cookie Preference Center