Split a team across two migration waves, and Teams treats the two halves as separate organizations for meetings and chat until the second wave completes.

In a phased BitTitan migration, users already moved to the destination tenant and users still in the source tenant sit in different tenants. Native cross-tenant federation can bridge them, but only when both tenant admins explicitly set it up. Without it, moved users can lose the ability to schedule meetings with the users who remain.

That has a direct consequence for wave planning: migrate groups that meet across teams frequently in the same wave.

Have you reviewed Teams meeting dependencies between user groups before finalizing your wave structure?

#BitTitan #MigrationWiz