Networking on a Hyper-V host is very similar to networking on an AHV host and an ESXi host. Naming of objects is again different, but functionality is the same:
Just like with AHV and ESXi, the hypervisor has a connection to both the InternalSwitch and the ExternalSwitch. The name of the hypervisor on a Hyper-V host is confusingly also Hyper-V, and this hypervisor attaches to virtual switches by way of a vEthernet port. All virtual network adapters are where the VLANs are defined, and also where the network names are defined.
Hyper-V doesn't have port groups, it has network names which don't work at all the same way that they do in AHV.
Verification Commands from Powershell
-
Get-netadaptervmq
-
Get-netadaptervmqQueue
Please refer to this link for detail explanation of Networking in hyper-v
https://portal.nutanix.com/page/documents/kbs/details?targetId=kA0600000008fOSCAY