Currently, we are not aware of any plans from Windows Server for this capability. We’ll continue to work with Windows Server to revisit this in the near futureTom Hebert commented
@BenTheBuilder is spot on. For large organizations, maintaining AD is fine. But for many others, it's overkill. Imagine the scenario where you are supporting a small business having two servers. In order to use AD, you need to maintain an AD server and best practice says two. AD domains are fragile and must be carefully operated or you will be finding yourself researching and fixing very complex issues.
This hypothetical business really wants single sign on, two-factor authorization, and some basic things. Their one and only admin has full control anyway. Pushing complex group policies is just an unnecessary complication. Most other things associated with AD are an unnecessary costly distraction.
Finally, a simplified on-premise environment is much easier to move to Azure. When I do this, the first thing I do is provision a replicate domain server in Azure, mainly to ensure that authentication can occur should the site-to-site VPN go down.
417 votesunplanned · 52 comments · Azure portal » Resource management · Flag idea as inappropriate… · Admin →
IPv6 in Azure VNET is currently previewing globally- in ALL Azure Public cloud regions.
Announcement (Service Update): https://azure.microsoft.com/en-us/updates/public-preview-microsoft-adds-full-ipv6-support-for-azure-vnets/
Links to Documentation & Samples
Full documentation including sample scripts is available here: https://aka.ms/IPv6ForAzureVNETdoc
A sample JSON template is posted in the quickstart repository: https://azure.microsoft.com/en-us/resources/templates/ipv6-in-vnet/Tom Hebert commented
I am looking to remove IPV4 from our private infrastructure, limiting our use of IPV4 to access public servers that do not support IPV6. The lack of support for IPV6 in Azure Networks and IPSEC gateways is currently my only barrier.