I have setup an RDS Personal Virtual Desktop Collection using a nested Hyper-V server (Windows 2016) under Azure. Azure is using Azure Active Directory Domain Services, which can provide DHCP addresses to any Virtual network created within Azure. However, in the Hyper-V nested server, I have had to setup an internal virtual network for the RDS Desktop Collection (5 x Windows 10 Pro workstations). In an non-Azure AD Domain Services network, it would be simple to set up a DHCP server on the Hyper-V hosting server to provide IP Addresses to the virtual network. However Azure AD Domain Services will not allow a DHCP server to be activated as no AAD DC Administrator has Domain Admin privileges.
So has anybody achieved either setting up a DHCP server in Azure AD Domain Services or have you managed to link the nested Hyper-V virtual network back to an Azure virtual network/subnet so DHCP addresses can be provided to the nested virtual network and therefore the 5 workstations connected to it?
It does work using the Hyper-V virtual network switch configured with a static address and NAT'd with a Class-C subnet but each workstation has to be configured manually with an IP static address.
Any suggestions or solutions would be gratefully appreciated.