Two domains in one tenancy

[fredbayker]

Hi,

 

If I have two tenancies in office365 each with one domain and I wanted to consolidate by migrating one domain to the other tenancy, would anyone know how in terms of functionality it would work? Are the users in one domain still classed as ‘guests’ in the other domain if files in sharepoint are shared with them?

 

Cheers

[snagrat]

If it’s all one tenant then they will not classes as guests.

 

Guests are only when crossing tenancies, not domains.

[Roberto]

Hi,

 

If I have two tenancies in office365 each with one domain and I wanted to consolidate by migrating one domain to the other tenancy, would anyone know how in terms of functionality it would work? Are the users in one domain still classed as ‘guests’ in the other domain if files in sharepoint are shared with them?

 

Cheers

 

You’d be migrating them to the ‘new’/other tenancy, at which point they wouldn’t be guests, they’d be accounts in the tenant. You would need to set up things do that only one AD Connect server at a time was syncing both domains to Azure AD, multiple AD Connect servers syncing with the same tenant isn’t a supported scenario. This will work fine though, I currently have approx. 150 domains syncing with one tenant at the moment.

Edited June 24, 2020 by Roberto

[fredbayker]

Perfect. Thank guys.

The plan is to migrate the on-premise domain first and then do the same in the cloud. Luckily neither domain has ADconnect configured at the moment so should be more straightforward.

 

It will make my life so much easier!

[chaplic]

Sorry - a lot here is wrong or at best unclear.

 

If you've "guested" people from tennant A into tennant B, this will not happilly carry on when you migrate across. In fact a previous guest account and a 'real' account will likely clash on things like duplicate SMTP address.

 

To get rid of mytennantA.com domain from tennant A you need to move people to another domain, release the domain from the tenant and add the domain to tennant B. This could take 24 hours to free up (probably less).

[fredbayker]

Sorry - a lot here is wrong or at best unclear.

 

If you've "guested" people from tennant A into tennant B, this will not happilly carry on when you migrate across. In fact a previous guest account and a 'real' account will likely clash on things like duplicate SMTP address.

 

To get rid of mytennantA.com domain from tennant A you need to move people to another domain, release the domain from the tenant and add the domain to tennant B. This could take 24 hours to free up (probably less).

 

I’m outsourcing this so I hope this is the strategy they will take, good to know however because I will press them on this issue. [emoji106]

However, the original post was just in terms of going forwards when a userA from domainA shares to userB in domainB, is userB ‘guested’ in domainA even under the same tenancy?

[chaplic]

I’m outsourcing this so I hope this is the strategy they will take, good to know however because I will press them on this issue. [emoji106]

However, the original post was just in terms of going forwards when a userA from domainA shares to userB in domainB, is userB ‘guested’ in domainA even under the same tenancy?

 

No. Once you're all in the same tenant, it's all pretty smooth and the domain in question doesn't really matter - I have worked in environments with 50+ domains and everyone can share with each other with no drama.

[fredbayker]

[emoji106]

[fredbayker]

Thanks all