In the latest Windows 10 build 10586 (Threshold 2) and Windows Server 2016 Technical Preview 4, Microsoft included a great new feature which is NAT mode for the Hyper-V Virtual Switch. This was mostly build for Windows Containers scenarios, but also has great value for Client Hyper-V. As of today Hyper-V had 3 different VMSwitch types called, Internal, Private and External. With the latest releases of the Windows 10 and Windows Server 2016 Technical Preview 4, Microsoft included a new VM Switch Type called NAT, which allows Virtual Machines to have a Internal Network and connect to the external world and internet using NAT. This feature right now is not included in the UI but you can use PowerShell to create the NAT Virtual Switch.
Create a new Virtual Switch using NAT:
New-VMSwitch -Name "NATSwitch" -SwitchType NAT -NATSubnetAddress 220.127.116.11/24
Setup the NAT configuration:
New-NetNat -Name VMSwitchNat -InternalIPInterfaceAddressPrefix "18.104.22.168/24"
This will create a new VM Network Adapter on the host using the 22.214.171.124 IP Address. You can now use the NATSwitch to connect Virtual Machines. You can now set IP Addresses inside Virtual Machines to the 126.96.36.199/24 subnet and add 188.8.131.52 as the default gateway and you are good to go.
Have fun and enjoy! Thanks to Ben Armstrong (Microsoft VirtualPCGuy) for the info.