AAD Connect multi-tenant sync now available

Couple of months ago I wrote about multi-tenant sync when it was still in public preview. So what has changed after it’s globally available?

Before the documentation was stating:

It is not supported to use the same custom domain name in more than one Azure AD tenant, with one exception: it is supported to use a custom domain name in the Azure Commercial environment and use that same domain name in the Azure GCCH environment. Note that the custom domain name MUST exist in Commercial before it can be verified in the GCCH environment.

And now.

It is not supported to add and verify the same custom domain name in more than one Azure AD tenant, even if these tenants are in different Azure environments.

So not much difference feature wise, all that was supported in the preview is supported in GA version.

Basically You can:

• Sync users and groups from your Active Directory to multiple tenants but You cannot use the same custom domain in them.
• Sync passwords across multiple tenants but Password writeback has to be enabled.
• Sync the same users to different Azure clouds.

Azure AD Connect: Supported topologies

This topic details supported and unsupported topologies for Azure AD Connect