Single domain controller in Azure with multiple AD sites

Matt Wolfe 11 Reputation points
2025-01-13T20:06:00.6066667+00:00

We are in the process of collapsing multiple AD domains into a single AD domain. we have 5 locations. My plan was to have a multi-site setup with a DC at each site. However, I now need to pivot to a single Azure VM Domain Controller and no on-premises DCs. How do I implement this or is it even possible?

Thanks,

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
6,798 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Marcin Policht 31,400 Reputation points MVP
    2025-01-13T23:41:32.49+00:00

    You can consolidate multiple on-premises AD domains into a single domain with an Azure VM acting as the sole Domain Controller (DC). However, moving to a single cloud-hosted DC comes with considerations regarding connectivity, performance, and redundancy. Here is an approach you can use:

    1. Consolidate the AD domains Before moving to Azure, complete the domain consolidation:
      • Identify and migrate all objects (users, computers, groups) from the multiple domains into the target domain.
      • Resolve any conflicts (e.g., duplicate usernames or group names).
      • Update group policies, scripts, and applications to align with the new domain structure.
    2. Configure Azure networking Create an Azure virtual network:
      • Ensure the Azure VM is deployed in a VNet that allows communication with all your remote locations.
      • Establish a secure connection between your on-premises networks and Azure. This can be done by using either a site-to-site VPN or ExpressRoute.
      • Configure the virtual network to use on-premises DNS resolvers.
    3. Deploy the Azure VM Domain Controller Create an Azure VM:
      • Deploy a Windows Server VM in Azure that meets the requirements for a DC.
      • Install the Active Directory Domain Services (AD DS) role.
      • Promote the VM to a DC for the consolidated domain and configure it as a DNS server
      • Modify the DNS configuration of the VNet to point to the newly promoted VM as the DNS resolver
      • Set the Azure VM DC as the primary DNS server for all clients in your environment.
      • Configure DNS forwarding if needed.
    4. Decommission On-Premises DCs After verifying that all authentication and services work with the Azure-hosted DC:
      • Demote the on-premises DCs.
      • Remove them from the domain.

    Btw. you should deploy another Azure VM-hosted DC for redundancy reasons.


    If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    hth

    Marcin

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.