How would you set up shared IT when a company splits into separate businesses?

November 17, 2026 5 answers
Asked by Vexo

We're splitting one company into four operating companies and a shared services company. Everyone currently uses one Microsoft 365 tenant for identity, with OneDrive and Egnyte for files. Each company will eventually have its own email domain, and some people will need access across companies.

Would you keep one tenant or create separate tenants? Management is also interested in whether separate tenants could each use the Microsoft 365 Business Premium user limit.

Answers

Cazrik

I'd start with one tenant unless there's a clear requirement for stronger separation. Shared services can still administer it, and you can add the company domains and assign people the appropriate email addresses. A sign-in name and a primary email address don't have to be identical, though keeping them aligned where practical may make things less confusing.

Use groups to control access by company, then grant cross-company access where it's needed. Review the actual permissions in Egnyte and Microsoft 365 rather than assuming different email domains provide isolation. One tenant makes collaboration easier, but it doesn't automatically give you a clean security boundary between businesses.

Vexo:

So the company domains can coexist without each business needing its own tenant?

_c45+orbitmarble.9:

Yes. Multiple verified domains can be used in one tenant. Plan the sign-in and email naming separately, and check how each SaaS app identifies users before changing existing accounts.

Reply to this answer
3v~gromlet_824

Separate tenants may make sense if the companies need independent administration or a stronger separation of identities and data. That decision has a cost beyond the migration.

Test the workflows before promising they'll work the same way across tenants. Shared mailboxes, Teams rooms and access to files across company boundaries can be more awkward than they are within one tenant. You'll also have more environments to administer and troubleshoot. Cross-tenant access helps, but it isn't the same as everyone sharing a directory.

Reply to this answer
4v!nexdrin_572

Don't make the tenant decision on the Business Premium limit alone. Get a current licensing review from Microsoft or your licensing provider, including how the rules apply to these entities and any shared users. Separate tenants do not by themselves prove that the proposed licensing arrangement is permitted.

Price the whole setup too. Compare the license costs with migration, ongoing administration, cross-company collaboration and any additional licenses the chosen design needs. E3 may also need additions to match particular Business Premium capabilities, so compare the features you actually use.

Reply to this answer
_v39!quibrel.6

For Egnyte, map out whether the companies will share one environment or have separate ones, then test SSO for each. A single Microsoft 365 tenant can contain users with different sign-in domains, but the app configuration has to send an identifier that matches what Egnyte expects.

If there are separate Egnyte instances, look into separate SAML application configurations and verify the supported setup with the vendor. Test provisioning, user matching and access changes as well as the initial login.

Reply to this answer
Varn

Get the operating model down on paper before building it. Who owns the tenant and contracts, who approves access across companies, and who pays for shared services? Those answers affect administration just as much as the technical layout.

Also ask what happens if one business is sold or wants to leave later. A single tenant can be simpler now, but separating its accounts and data later is a project worth planning for.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions