From f45336986889447984640144dbc958389fdee8c7 Mon Sep 17 00:00:00 2001 From: Grayson Bishop Date: Tue, 3 Feb 2026 12:37:31 -0500 Subject: [PATCH] Clarify that target environment cannot be managed Added a note that the target environment cannot be a managed environment. --- power-platform/admin/copy-environment.md | 1 + 1 file changed, 1 insertion(+) diff --git a/power-platform/admin/copy-environment.md b/power-platform/admin/copy-environment.md index c214ff65e5..33c9175a51 100644 --- a/power-platform/admin/copy-environment.md +++ b/power-platform/admin/copy-environment.md @@ -25,6 +25,7 @@ You can use the **Copy** option in the Microsoft Power Platform admin center to > - The target environment will be listed in the **Select environment to overwrite** drop-down. If you don't see an environment, that means you can't overwrite it. For example, you can't overwrite production environments so you won't see any environments of type production. > :::image type="content" source="media/copy-environment/copy-environment-no-target.png" alt-text="No target for copying environment."::: > - You can only copy to an environment in the same tenant and region. +> - The target environment cannot be a managed environment > - If an environment is [enabled for Virtual Network support](vnet-support-overview.md), you can only copy to an environment in the same enterprise policy. > - Components that have not been added to a solution (including canvas apps, flows, custom connectors, and connections) might not be part of the copy. You should validate your apps post copy. > - For each canvas App only up to 20 of the most recent revisions will be copied over.