Microsoft's new cross-tenant migration workflow for Exchange, OneDrive, and Teams looks...

Microsoft's new cross-tenant migration workflow for Exchange, OneDrive, and Teams looks like a step forward for M&A work. The orchestration piece could reduce some manual sequencing that teams have been handling outside the platform. Even so, the real friction in these projects still shows up in the dependencies. Shared mailboxes, delegation chains, and apps tied to specific identity objects often surface only after the first pilot wave runs. Identity matching has to be locked down before any data moves, or permissions land in the wrong places. Coexistence settings for GAL and free/busy remain essential while waves run over days or weeks. Without them, the business feels the disruption even if the tool reports success. I wonder how this new workflow will handle the edge cases that always appear once real user cohorts start testing.