#Azure AD

1 messages · Page 1 of 1 (latest)

unreal silo
#

Guys, recently my company bought another one that also uses Azure AD, I wanted to understand the options to connect and unify the two, could someone help me?

unreal silo
# nova ruin Read here

I understand that cross-tenant sync will synchronize users, but it would still be 2 tenants correct? can you tell me if the users of the purchased company will still have the same domain? or would it be changed to my company's domain?

nova ruin
#

it will remain two tenants, and the domains will remain the same for all users

#

the main thing to look at here are those two parts

#

Who should use?

Organizations that own multiple Azure AD tenants and want to streamline intra-organization cross-tenant application access.
Cross-tenant synchronization is not currently suitable for use across organizational boundaries.

Benefits

With cross-tenant synchronization, you can do the following:

Automatically create B2B collaboration users within your organization and provide them access to the applications they need, without creating and maintaining custom scripts.
Improve the user experience and ensure that users can access resources, without receiving an invitation email and having to accept a consent prompt in each tenant.
Automatically update users and remove them when they leave the organization.
#

if you see your setup fits into those, then by all means, go for it

unreal silo
#

but what if we somehow want to make the tenant of the purchased company no longer exist, keeping only 1 tenant and moving the users from the old one to the new one?

nova ruin
#

if the users are synced from on prem to Azure using AAD Connect, just point them to the new tenant then

#

If the users are not sycned, you have to create them manually in the new tenant

#

there's no direct migration option you can use natively from azure for users from one tenant to another

unreal silo
#

using cross-tenant sync, what would happen to mailboxes, and other stuff from M365?