Update tenant migration details in documentation

Clarified the environment's physical location and added information about the UI option for tenant-to-tenant migration that was added during ignite nov 2025.

Author: CarlFEngedal

power-platform/admin/move-environment-tenant.md

@@ -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?
 
@@ -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..