Last month we looked at how to set up nested VMs in Hyper-V on Windows Server 2016. Azure, of course, runs on Hyper-V and some regions already have some of their hosts upgraded to Windows Server 2016.

As Brien recently discovered, a glitch in Azure can cause a virtual machine to fail when it's manually configured to use a specific DNS server. Here's how the problem went down and how he fixed it.

Microsoft announced Azure VM Image Builder has reached general availability, providing a managed service that reduces the complexity of manually creating virtual machines images -- with associated ...