SOLVED

User experience with Multi-Domain single Tenant.

Copper Contributor

I have a client that has 2 very small companies (4 people in each company). There really isn't a "parent company"...just 2 small companies that want to share resources, people and tech.

 

In order to save money on licensing, we are moving them from a multi tenant configuration to a single tenant 2 domain  configuration. company1.com company2.com

 

Most of the employees need to communicate across the 2 companies in teams and share documents. We plan on setting up aliases for most employees so they can send and receive email from either company. I've never set this type of configuration up and have some questions.

 

I'm wondering what their user experience will look like in Teams.

- will they have a single "main" login to teams from the "main" company? or will they need to have 2 accounts with "presense" in Teams?
- Will there be a single Teams backend for both companies? or will each company have a separate Teams backend? 

- How can we set up cross company Teams channels?

 

Thank you, in advance.

Matt

 

4 Replies

@Matt Suderman 

Hello,

If I understand correctly, you will only have one tenant with 2 custom domains representing each company, right?

 

The experience in Teams will be seamless, each user will be able to communicate with each other, with no silos.

The login experience will depend on the UPN selected.

I hope I understood correctly.

Thanks for the reply. Just a small followup question.

So, the way you describe it,
- It will function like a single environment (from a user perspective)
- the domains are basically for login and email in/out.
Do I have it right?

@Matt Suderman Hello Matt, yes, the way I also understood your scenario :smile: It'll be like that

best response confirmed by Matt Suderman (Copper Contributor)
Solution

@Matt Suderman Hello Matt, If I understand correctly, you will only have one tenant with 2 custom domains representing each company, right? The experience in Teams will be seamless - each user will be able to communicate with each other across companies, with no silos.

 

The login experience for users will depend on the UPN selected, but from a user perspective it will function like a single Teams environment. The custom domains are basically for login, email routing in/out, etc. But users will not notice divisions between companies in Teams.

1 best response

Accepted Solutions
best response confirmed by Matt Suderman (Copper Contributor)
Solution

@Matt Suderman Hello Matt, If I understand correctly, you will only have one tenant with 2 custom domains representing each company, right? The experience in Teams will be seamless - each user will be able to communicate with each other across companies, with no silos.

 

The login experience for users will depend on the UPN selected, but from a user perspective it will function like a single Teams environment. The custom domains are basically for login, email routing in/out, etc. But users will not notice divisions between companies in Teams.

View solution in original post