Troubleshooting: Microsoft Azure

If the appliance is deployed but isn't behaving as expected, work through the issues below. If it boots but never connects, or the tunnel drops right after it establishes, the cause is usually firewall L7/TLS inspection or NAC, not this platform: see Connectivity troubleshooting.

cloud-init status reports error on first boot

This is a known, cosmetic issue on the current image. The only failing module is cc_mounts, which races on the Azure ephemeral resource disk (/mnt). Boot, networking, SSH, the admin user, and swap all work. To clear it, run sudo cloud-init clean --logs and reboot, or remove the /mnt line from /etc/fstab.

The VM boots to a black screen

The disk or VM was created as Gen1. Recreate both as Gen2 / V2 (--hyper-v-generation V2 on the disk and image; see the Azure CLI guide). Do not use Add-AzVhd.

The SAS URL has expired

These are read-only user-delegation SAS tokens with a 7-day maximum lifetime (48 h by default). Ask your engagement lead for a fresh URL.