Forum Discussion
Glenn V
Apr 06, 2017Brass Contributor
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...
- 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.
Would the answer change if the user count was under 50? Under 25? How about Microsoft allow a no cost vm if it's only used for one thing - Azure AD connect deployment?
amit kalia
May 22, 2018Copper Contributor
Hi,
Well actually according to best practices answer does not changes. However I have seen that if implement AAD connect on a DC for small organization which cannot afford a a dedicated server it works fine.
But still we would recommend keeping all on separate servers.
Thanks & Regards
Amit Kalia
Well actually according to best practices answer does not changes. However I have seen that if implement AAD connect on a DC for small organization which cannot afford a a dedicated server it works fine.
But still we would recommend keeping all on separate servers.
Thanks & Regards
Amit Kalia