Azure AD – You can now synch your AD with multiple tenants (preview)

This has been a long awaited capability.

As you know until then you were not able to synchronize your Active Directory with multiple Azure AD/Office 365 tenant.

Well, this is now possible and supported to do so; meaning you can synchronize your users, groups and contacts from your Active Directory to different tenant (aka duplicating them).

Before you start jumping to implement you need to know the following:

  • You need one different instance of Azure AD connect for each tenant you want to synchronize with; Azure AD Connect does not allow (yet?) to synchronize with multiple tenant
  • Only one Azure AD tenant sync can be configure for write-back (groups and/or devices) as well as hybrid Exchange. Password writeback can be enabled with the different tenant
  • You can not reuse the same custom domain(s) across each different tenant; unless you are using different Azure environments (commercial, government)
  • Devices can be synchronized with multiple tenants but only one can be configured to trust the devices
  • You can not enable hybrid experience like Seamless SSO and Hybrid AD Join to more than 1 tenant

The complete documentation cab found here Azure AD Connect: Supported topologies | Microsoft Docs


1 thought on “Azure AD – You can now synch your AD with multiple tenants (preview)”

  1. Hello,

    Had a question on this and wondered if you had the answer?

    We’re currently migrating one AD synced to Microsoft tenant to another Microsoft 365 tenant, and wondered if we would use this to pre-stage the users in the destination tenant instead of having to do it all in one cutover weekend?

    In this case, we would sync the user from AD to both Microsoft 365 tenants and then on cutover weekend, disassociate the users primary domain with the current Microsoft tenant and reassociate it with the new Microsoft tenant.

    Would this theory work?

Leave a Comment

Your email address will not be published. Required fields are marked *

The reCAPTCHA verification period has expired. Please reload the page.