Skip to content

Update tenant migration details in documentation #2831

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sericks007 merged 2 commits into from
Dec 9, 2025
Merged

Update tenant migration details in documentation #2831

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2922001
Update tenant migration details in documentation
CarlFEngedal Nov 20, 2025
2d65205
Update move-environment-tenant.md
sericks007 Dec 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions power-platform/admin/move-environment-tenant.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -381,7 +381,7 @@ Only production and sandbox environments are supported. Default, developer, tria

#### Will the environment physically move to the new tenant?

No. The environment remains in place, but the Dataverse organization is moved to the destination tenant. It's no longer part of the source tenant and is managed under the new environment in the destination tenant.
No. The environment remains in place, but the Dataverse organization is moved to the destination tenant. It's no longer part of the source tenant and is managed under the new environment in the destination tenant. Data that is stored in dataverse will still be stored in the environment in your tenant. The orphan environment should therefore be deleted when the tenant-to-tenant move is completed and it it confirmed that the data is no longer needed in the source tenant.

#### Are there any components that aren't fully supported?

Expand All @@ -396,5 +396,4 @@ If the mapped user (mentioned in the user-mapping file) has a mailbox in the des
The source tenant’s Dynamics 365 or Power Platform admin must submit a request using PowerShell commands with the environment name, ID, and tenant ID. Refer to the commands above.

#### Is there a self-serve UI option?

No, currently we don't support the Power Platform admin center UI for tenant-to-tenant migration. It can only be done by PowerShell.
Yes. After the TenantToTenant-SubmitMigrationRequest –EnvironmentName {EnvironmentId} -TargetTenantID {TenantID} is approved in the target tenant, an UI option to move the environment will be available in the environment page..