Can't connect to VM after migrating to azure

Hi @Chad Miller
It looks like you’ve got a Windows VM booting just fine from your Veeam-restored managed OS disk (now Gen2/GPT), but RDP, Run Command and the Azure VM Agent never come up. That usually means Azure never “provisioned” the VM agent or configured the guest for Azure’s fabric, and simply attaching a disk—especially a specialized one—doesn’t trigger that out-of-the-box.

Create the VM as a specialized VM so Azure doesn’t try to sysprep it but will still configure the platform hooks

With Azure CLI:

az vm create \
--resource-group MyRG \
--name MyVM \
--attach-os-disk MyOsDisk \
--os-type Windows \
--use-unmanaged-disk \
--location eastus

Or with PowerShell:

$osDisk = Get-AzDisk -ResourceGroupName MyRG -DiskName MyOsDisk
New-AzVM -ResourceGroupName MyRG `
  -Location eastus `
  -VMName MyVM `
  -AttachOsDisk $osDisk.Id `
  -OsType Windows `
  -Specialized

Verify/install the Azure VM Agent inside the guest

• If you haven’t already, mount the OS disk on a helper VM and run the WindowsGuestAgent MSI (you can grab it from the Azure VM agent release feed).
• Make sure the C:\WindowsAzure folder structure and registry entries under HKLM\SOFTWARE\Microsoft\Azure\ are present.
• When you re-attach and boot, check C:\WindowsAzure\Logs\WaAppAgent.log to confirm the agent starts without errors.

Check Windows networking and firewall

• Ensure the NIC inside Windows matches the Azure NIC (if Veeam renamed adapters, you may need to delete old virtual adapters or reset the interface name to “Ethernet”).
• Verify Windows Firewall allows port 3389 in the active profile.
• Confirm the NSG and Azure Firewall (if any) allow inbound RDP.

(Gen2-specific) Confirm UEFI boot settings

• Azure Gen2 requires GPT+UEFI—make sure secure boot is disabled (it isn’t yet supported in Azure Gen2).
• Your presence of \EFI\Boot\bootx64.efi is good; just double-check your VM’s Boot Diagnostics/Serial Console settings in the portal.

Once the VM agent boots and registers, you’ll regain Run Command/reset capabilities and be able to RDP in (assuming ports and NSGs are open). If you’d still run into issues, you can also push the VM agent extension post-boot:

Set-AzVMExtension -ResourceGroupName MyRG `
  -VMName MyVM `
  -Name "AzureVmAgent" `
  -Publisher "Microsoft.Azure.Extensions" `
  -ExtensionType "AzureAgent" `
  -TypeHandlerVersion "2.5" `
  -Location eastus

Hope that helps get your agent—and RDP—back online!
https://learn.microsoft.com/en-us/azure/virtual-machines/extensions/agent-windows

I ran the AZ CLI command as you directed and got this error.

The default value of '--size' will be changed to 'Standard_D2s_v5' from 'Standard_DS1_v2' in a future release.

Consider upgrading security for your workloads using Azure Trusted Launch VMs. To know more about Trusted Launch, please visit https://aka.ms/TrustedLaunch.

list index out of range

I also tried the powershell version and got all kinds of errors that I couldn't fix.

I have also already tried this step that you recommended.

mount the OS disk on a helper VM and run the WindowsGuestAgent MSI