High availability support for AAD Connect
Please provide HA support for AAD Connect with automatic failover! The staging server process is hopeless, and it doesn't support a shared SQL DB. At the moment, the fastest way to do AAD Connect recovery in case the AAD Connect server is destroyed, is to have an default installed Win2016 server with the AAD Connect install files downloaded (and not installed). Due to the fact that both the production and staging server must have same version (or higher), there's a risk that some stuff will not work when you do a recovery to a second server and there's a version mismatch.
In case the primary AAD Connect server goes down, I need an automatic solution and not something that requires a poor sysadmin to be pulled out of sleep in the middle of the night. The AAD Connect server are becoming very critical.
Also looking into if there are any updates here?
It would be useful to not just support an Active-Standby but a N-Active HA topology. Conceptually this could be easily achieved by having a manager node(s) for the set of AAD Connect agents to distribute what agents would synchronize each element of the DB between on prem & Azure.
If you're interested in providing feedback on the feature in-development, please send a note to firstname.lastname@example.org.
Program Manager, Identity
We are currently working on a light weight agent based provisioning solution in Azure AD Connect that would enable high availability. We have no timelines to share at this moment.
Mark Ziesemer commented