Forum Discussion

Glenn V's avatar
Glenn V
Brass Contributor
Apr 06, 2017
Solved

Azure AD Connect on a DC

With the documentation I've found so far I'm a bit unclear whether or not it is best practice to install Azure AD Connect on a domain controller. In this particular scenario we are looking at a singl...
Azure Active Directory (AAD)
  • NunoAriasSilva's avatar
    NunoAriasSilva
    Apr 07, 2017

    Hi Glenn,

     

    In my opinion, the recommended installation is always in a separate server regarding to isolate points of failure.

     

    In past time e.g.. Dirsync it was not supported but Microsoft has expanded the support on installation on servers with other roles using Express Instalation.

     

    If you install AD Connect on a DC or other machine with other products, it would be harder to understand a problem if occurs in your environment either the problem is on the DC role or AD Connect. 

amit kalia's avatar
amit kalia
Copper Contributor
Aug 30, 2017

Well we have deployed AAD Connect on seprate servers as i dont want to disturb my DC to be overloaded. Also we have redudancy for AAD Connect servers as well to mitigate Risk.

 

In your case it seems we have only 100 users it seem to be ok to install AAD Connect on DC. Also article you reffered itself says the same "This server may be a domain controller or a member server when using express settings"

 

So in my opinion I guess there is no harm and later if you want to move AAD Connect to Different server you can do that by getting a server , keeping in staging mode synced and then remove first one and make new active.

 

But the Best approach is to keep it sweet and simple by keeping it separate.

Resources