Skip to the stories
Microsoft 365 & SharePoint

Merging Microsoft 365 Tenants Without Merging Their Risk

Tenant consolidation carries every identity weakness forward unless you set the standard, clean up the target and strip temporary access before the project closes.

Merging Microsoft 365 Tenants Without Merging Their Risk

 Merging Tenants - Identity Risk

A Microsoft 365 tenant consolidation can look finished well before it is. Mailboxes have moved, Teams and SharePoint are working, and the project lands on its scheduled date. That's the moment I'd start asking harder questions, because the identity side of the move often hasn't been settled at all.

Consolidation is a large change to identity, access and policy, and it's usually made under time pressure. The risk that survives the cutover tends to trace back to two things: what each source tenant brought with it, and the shortcuts the team took to hit the date.

Most of the risk comes in with the tenants

Every tenant you merge carries its own identity sources, authentication methods, Conditional Access policies and MFA enforcement. Layer on standing administrative access and a tangle of third-party applications and mail flow integrations, and it becomes easy to carry every weakness straight into the new environment. Three decisions help before anyone's account is touched.

  1. Pick the tenant that sets the standard. Choose the one that best reflects your long-term operating and security model, not the one that happens to be largest or most familiar.
  2. Review everything you're inheriting. Cover every tenant in scope, including Conditional Access, MFA enforcement, privileged roles and standing admin access.
  3. Name the decision-makers. Agree in advance who approves access changes, exceptions and rollbacks.

Skip these and the calls still get made. They just get made ad hoc, mid-project, by whoever is online at the time. That's where most of the avoidable exposure I've seen in this kind of work comes from.

The target tenant has to be better than what you're merging

Here's the thing: if the target isn't ready, everything you migrate inherits its gaps. Before the first user moves, set baseline Conditional Access and device compliance policies, confirm logging, auditing and alerting are switched on, and clear out unused accounts, stale guests and orphaned objects. Every account you retire now is one less identity to migrate and secure later, and cleanup is far cheaper before the move than after it.

The migration window is where risk peaks

Scale, deadlines and productivity pressure all push toward shortcuts. A broad permission granted "just for the weekend" has a habit of outliving the project by months. A few practices keep the move honest:

  • Avoid blanket temporary permissions. Grant what each step needs, not more.
  • Automate where you can. Repeatable moves reduce manual error and the ad hoc access grants that come with it.
  • Watch for privilege spikes and policy drift while the move is running, and audit access changes throughout rather than only at the end.

That last point matters more than it sounds. Drift during a migration is easy to miss because everyone's attention is on user impact, not on the admin plane.

The project isn't done until the temporary access is gone

Consolidation isn't complete until temporary admin roles, trusts and synchronization jobs have been removed, and unused tenants are archived and decommissioned. Leftover access is exactly the sort of exposure attackers look for, and it's often the last thing anyone remembers to revisit once the go-live celebration is over.

A useful sign-off test is whether you can honestly say all of the following:

  • Access is more consistent and easier to understand
  • Privileged access is reduced and better governed
  • Visibility across identity, access and activity has improved
  • The approach can be repeated safely for future consolidations

If any of those is a no, the consolidation isn't finished, whatever the project plan says. My read is that teams who treat this checklist as a gate, rather than a formality, end up with a tenant they can actually run.

Turning this into a change plan

The Quest tenant consolidation readiness checklist walks IT and security teams through each of these phases, from establishing a safe baseline to confirming the new tenant is in better shape than the ones it replaced. It's a practical starting point if you're about to schedule a merge and want the identity work written down before the cutover date arrives.

Download the Quest tenant consolidation readiness checklist →

For details on Quest's approach to this work, see the Secure Migration datasheet.

Source: Janet O'Malley · blog.quest.com

Same flag