Microsoft 365 after an acquisition

After an acquisition, the IT team inherits the question: what do we do with the two Microsoft 365 tenants? Both companies probably had their own. There's no single right answer; the options span coexistence to full merger, and the right choice depends on integration intent, regulatory constraints, and timeline.

The options

1. Coexistence (separate tenants long-term)

Both tenants remain separate, with minimal integration:

• B2B guests for specific cross-company collaboration.
• Exchange organisation relationships for free/busy sharing.
• Shared channels for project teams spanning both.

Right when:

• The two companies will continue operating largely independently.
• Regulatory or contractual requirements prevent merging.
• The acquisition is part of a portfolio strategy without operational integration.

2. Multi-Tenant Organisation (MTO)

Both tenants join an Entra ID Multi-Tenant Organisation:

• Cross-tenant user synchronisation auto-provisions guests.
• Unified people search across MTO members.
• Shared channels work cleanly between tenants.
• Cross-tenant Microsoft Search.

Right when:

• The companies will operate as a federation rather than a single entity.
• Long-term separation is intentional but rich collaboration is needed.
• Each retains its identity, regulatory compliance, and tenant-level governance.

3. Tenant-to-tenant migration (full merger)

Move all of one tenant into the other:

• Migrate users, mailboxes, OneDrives, SharePoint sites, Teams.
• Cut over the email domain.
• Decommission the source tenant.

Right when:

• The companies will operate as one entity going forward.
• A unified identity, brand, and operating model is the goal.
• The acquired business will adopt the acquirer's IT practices.

This is the most work — typically months — but produces the cleanest end state.

Timing considerations

The right path also depends on when:

• Day 1 — coexistence is the only realistic option. Even MTO setup takes weeks.
• Month 1–6 — set up MTO or coexistence patterns. Plan migration if going there.
• Year 1 — execute migration if that's the destination.
• Year 2+ — typically too long; if still separate, you've effectively chosen coexistence.

Practical integration in the early phase

Regardless of which long-term path, early-phase integration usually involves:

Identity bridge

• B2B guests invited into shared workspaces.
• Cross-Tenant Access Settings configured for trust between the tenants.
• Email forwarding for transitional periods if domains will eventually merge.

Communication

• Shared Teams channels for joint project work.
• Cross-tenant calendar visibility via Exchange organisation relationships.
• Cross-tenant directory search so people can find each other.

Files

• Shared SharePoint sites invited as guests.
• Specific file shares for collaborative documents.

Migration patterns

If you're going for full merger:

Wave-based migration

• Group users into waves by department / location / criticality.
• Migrate one wave at a time, validate, communicate, move on.
• 50–500 users per wave is manageable.

Identity-first migration

• Sync acquired-company users into the target tenant via cross-tenant sync.
• Cut over mailboxes, OneDrives, SharePoint sites.
• Decommission the source tenant once all artefacts moved.

Hybrid coexistence during migration

• During migration, both tenants are partially populated.
• Mail flow needs careful routing.
• Calendar sharing complicates around the boundary.

Cultural integration

The technical migration is only part. Cultural integration matters more:

• Different conventions for Teams use, file naming, meeting cadence.
• Different governance norms — what's allowed, what's not.
• Different toolsets users are accustomed to.

Plan for a change management workstream alongside the technical migration. Without it, "we migrated everyone but they hate the new tenant" is a real outcome.

Tooling

For large-scale tenant-to-tenant migrations:

• Microsoft first-party tools for Exchange and OneDrive cross-tenant migration.
• Third-party tools (Quest, AvePoint, BitTitan, ShareGate) for complex scenarios.
• Partner-led migration for very large or complex migrations.

For organisations facing an acquisition, decide the integration intent early — that drives the technical strategy. The biggest mistake is drifting through years of half-integrated coexistence because no one made the call.