Tenant Migration Can Break Power Platform Connections and Permissions
Diesen Beitrag auf Deutsch lesen
Tenant-to-tenant moves can sever Teams chat history, permissions, Power Automate connections and Power Apps dependencies unless they are rebuilt deliberately.
TL;DR
Power Automate flows and Power Apps are tied to originating user accounts and SharePoint site IDs. After a tenant move, connection references break, so developers must re-authenticate every trigger and action against the destination tenant. Permissions for Teams channels, SharePoint sites and collaborative documents also require deliberate remapping.
Original on M365 FM Podcast. Read the original · suggested by Mirko Peters
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Reconnect every Power Automate trigger and action after migration because transported flow definitions can still fail when their connection references point to the old tenant.
- Admins/CoE: Map destination permissions and rebuild access for Teams channels, SharePoint sites and collaborative documents because tenant boundaries do not copy the surrounding wiring automatically.
- Security/Compliance: Treat chat history, shared links and permissions as migration risks because tenant isolation can sever historical context and restrict access to corporate assets.
- Leadership/Business: Require a planned freeze and cutover process because data drift and broken automations can disrupt business continuity after a merger or divestiture.
Frequently asked questions
What happens to Power Automate connection references after a tenant migration?
Power Automate connection references point to the old tenant and break after migration. Developers must sign in again and reconnect each trigger and action.
Why do Teams channel permissions need rebuilding after a tenant move?
Teams channel permissions do not automatically copy across tenant boundaries. Administrators must deliberately map and rebuild access in the destination environment.
Do native Microsoft tools migrate complete Teams chat histories?
Native tools handle core workloads such as mailboxes and basic OneDrive content, but complex Teams chat histories generally require specialized third-party migration solutions.