This has been one of the most requested features for Hyper-V for many years. This is because Hyper-V did not support nested virtualization. In Windows 10 and Windows Server 2016, Microsoft added support for Nested Virtualization.
This feature has been around on other Type 1 hypervisors for a while now, but until recently, Microsoft showed little interest in providing the same functionality. This is because the only real use cases were home lab and training environments.
However, Microsoft went beyond the basic use of Nested Virtualization, and they have added containers into Windows Server 2016. This is the real reason why Microsoft took the time to enable nested virtualization. In the event this topic is new for you, think of a container as a type of mini VM, simply with applications in mind. Instead of virtualizing the entire OS, a container focuses on providing an isolated environment for an application to reside in without the overhead of a full VM. Microsoft...