Azure hyper-v nested virtualization with nested vms having bridged connection

Question

I am trying to run a custom hyper-v vhdx in Azure by first creating a virtual machine in azure, eg win10 or sever 2016, installing hyper-v on that vm and then installing the vhdx into hyper-v due to the issue trying to run custom vhdx files directly. The nested vm works fine by setting up a nat internal switch and can connect to the internet and ping other hosts in the virtual network, but i need to make the nested vm appear bridged so that other machines in the nework can ping the nested vm, and this is where I am unable to get it working. I have read some docs on creating a second nic on the host vm and enabling mac spoofing but this does not seem to work with azure. Can someone provide any guidance on how to make bridged nested vms in Azure, any help would be greatly appreciated.

Answer 1

I found the answer if anyone is also trying to work this one out. Just make sure you untick the checkbox that says "Allow management operating system to share this network adapter" when creating the virtual switch in Hyper-V.

1. Create the host machine in Azure, eg win10 / server2016 etc and install Hyper-V
2. Create a second nic in portal and assign it to the host machine
3. Create virtual switch in Hyper-v and assign it to the second nic and untick the above mentioned.
4. Enable mac address spoofing in Hyper-v for the vm

Now you should be able to get bridged networking on the nested vm's