Azure AD Connect in-place upgrade with separate SQL server

Question

We have a pretty new, not yet production, AD Connect setup. When reading through install requirements we understood that once our environment goes production we will probably hit the 100,000 synced objects and should probably deploy AD Connect with a dedicated SQL database an another system.

We are currently only syncing with the group filter options for testing. AD Connect is version 1.5.45.0. Could I still do an in-place upgrade to the new 1.6.4.0 build, or would I have to go through the hassle of deploying a second staging server and doing a cutover?

Answer 1

@KoNasl Thanks for reaching out and apologies for delay.

Considering this is yet pre-product and number of objects are less than 100,000 you can go for In-place update for Azure AD connect.
During the update process the synchronization is stopped anyway.

Do remember, If you've made changes to the out-of-box synchronization rules, then these rules are set back to the default configuration on upgrade. To make sure that your configuration is kept between upgrades, make sure that you make changes as they're described in Best practices for changing the default configuration.

-----------------------------------------------------------------------------------------------------------------

If the suggested response helped you resolve your issue, please do not forget to accept the response as Answer and "Up-Vote" for the answer that helped you for benefit of the c