Azure Vm won't boot up after restore from local Hyper V

Azure Portal

1. Go to Azure Portal.
2. Navigate to Storage Accounts > your storage account.
3. Go to Containers and create or open a container (e.g., vhds).
4. Click Upload, choose your .vhd file, and upload it. You can also enable Upload as block blob.

AzCopy (faster for large files)

1. Download AzCopy.
2. Open terminal or CMD, then upload:

      azcopy copy "C:\path\to\YourDisk.vhd" "https://<storageaccount>.blob.core.windows.net/<container>/<YourDisk.vhd>?<SAS-token>" 
   

• Get the full SAS URL from the Azure Portal (select the file/container > Generate SAS).

That typically means the VM can't find a valid bootloader or OS to start from. When restoring a VM from Hyper-V to Azure, especially if it wasn’t done with a clean, Azure-friendly image, some things can break.

Option 1: Validate and Re-Attach OS Disk

Stop the VM in Azure.

1. Go to Disks, detach the current OS disk.
2. Re-attach the same disk, but make sure it’s assigned as "OS disk".
3. Restart the VM.

Option 2: Create a New VM from the VHD

If the VHD was uploaded manually:

1. Go to "Disks" > Create disk from your VHD in Azure Storage.
2. Then go to Virtual Machines > Create > From a custom image or disk.
3. Select your newly created disk as the OS disk.

Make sure to:

1. Pick the correct generation (Gen1 or Gen2).
2. Match the OS type (Windows/Linux).

Option 3: Use Azure Migrate or Azure Site Recovery

For future restores or migrations, tools like Azure Migrate handle compatibility issues automatically.