Skip to content

Commit

Permalink
Update move-environment-tenant.md
Browse files Browse the repository at this point in the history
  • Loading branch information
udmehta committed Oct 4, 2023
1 parent a7a22fd commit 5a0e895
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion power-platform/admin/move-environment-tenant.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ There are no user interface changes or version changes as part of this move. You

> [!IMPORTANT]
> - If moving individual environments from one tenant to another requires a geographical region change, your tenant becomes a multiregional tenant. Regional features are enabled in the Power Platform admin center by support team. More information: [Geo to geo migrations](geo-to-geo-migrations.md).
> - You might need to reconfigure some applications and settings after tenant-to-tenant migration, such as Microsoft Dynamics 365 for Outlook, server-side sync, or others.
> - You might need to reconfigure some applications and settings after tenant-to-tenant migration, such as Microsoft Dynamics 365 for Outlook, server-side sync, SharePoint or others.
> - Geographical region changes aren't supported into or out of US GCC, US GCC High, US DoD, OCE, IND, or China.
> - Existing source database backups won't be migrated to destination tenant.
> - A Dataverse organization linked to a finance and operations organization cannot be migrated to a different tenant.
Expand Down

0 comments on commit 5a0e895

Please sign in to comment.