First off Hyper-V is a type 1 hypervisor. It runs underneath the OS as the host OS (in contrast to Vbox and VMware Workstation) is really another guest that runs on top of hyper-V.
Basically the hostOS is the parent with more control of the children guests. it is like this as the hypervisor runs at ring -1 underneath the kernal at the cpu.
I disagree as last weekend I cursed at VMware Workstation for being shitty in i/o and vowed never to run a type 2 hypervisor again. You need to create a switch as the parent guest (orginal host) needs to connect to the internet and have it shared with the other children or guests.
I am not saying I am a fan as I have not run KMS/Qemu or VMWare Sphere yet but Hyper-V is soo much better on my workstation with less bugs in my experience than with both workstation and virtualbox products. Just create a switch that is external and add that to yoru Vms and you should be good. It is not a bug but a feature as it is underneath everything and needs to share with your host or parent OS to your nic. It seems weird at first but makes sense from an architecture standpoint.
If this is automated running Edge as a container makes sense as Hyper-V supports shielded guests. As I type this I am already running under Hyper-V as I have this enabled on my 10 PC. I ran benchmarks.No difference in performance really besides 2 - 3 FPS in games. A container similiar to Docker makes sense and I hope Chrome follows!