Microsoft floating a single workflow for Exchange, OneDrive, and Teams during M&A...

Microsoft floating a single workflow for Exchange, OneDrive, and Teams during M&A migrations is a nice headline. In practice, the workflow is the easy part. What actually holds up tenant-to-tenant work: Mailbox and OneDrive cutover sequencing rarely lines up cleanly with Teams. Chat history, private channels, and shared channels each have their own constraints, and if you move mail before you have a coexistence plan for Teams federation, users notice within a day. Source tenant hygiene decides your timeline. Shared mailboxes with no owner, OneDrive sites for offboarded users still holding active shares, Teams with guest access nobody documented. A unified workflow does not fix any of that. Address rewriting and directory coexistence still need to be designed up front. If you have not decided how mail flow behaves during the overlap window, or how free/busy resolves across tenants, the tool cannot save you. And wave planning is still a human exercise. Grouping users by mailbox size is lazy. Group them by collaboration graph, meaning who works with whom, or you will split active project teams across the cutover boundary. A single pane for the mechanics is welcome. It does not shorten the discovery, and discovery is where these projects actually live or die.