Post-copy environment hardening and reconfiguration mini project

I handled a Production-to-PreProd refresh where the main challenge was not the copy itself, but the post-copy remediation. Since Production and PreProd were not identical and there were unmanaged solution layers, we had to control flows, app users, security groups, SharePoint integration, Synapse Link, environment variables, connection strings, configuration/master data GUID dependencies, and Canvas App references before the environment could be safely used.

Production → PreProd Copy: Key Activities

• Start point: environment copy from Production to PreProd using Power Platform Admin Center. Microsoft supports copying either full data or customizations/schema only.  
• Disable Power Automate flows immediately after copy to prevent accidental outbound integrations, emails, updates, or production-like processing.
• Review unmanaged solution layers because unmanaged customizations can sit above managed layers and override expected behavior. Microsoft also highlights unmanaged active layers as a common ALM issue.  
• Remove/change application users and service principals so PreProd does not use Production identities for integrations.
• Update security group mapping to restrict PreProd access to the correct users. Security groups are the recommended way to control environment access.  
• Disable or reconfigure SharePoint integration if document locations or site references still point to Production.
• Disable or reconfigure Mailboxes/sever-side synchronisation To prevent accidental email sending, synchronization issues, or connection to Production Exchange resources from the PreProd environment.
• Disable or reconfigure Azure Synapse Link / data export to avoid pushing PreProd copied data into Production analytics pipelines.
• Update connection references, connection strings, and environment variables so integrations point to PreProd endpoints, not Production. Environment variables are intended to hold configurable values across environments.  
• Retain master data GUIDs where needed if downstream integrations or configuration tables reference Dataverse record IDs.
• Update Canvas App links / embedded URLs if they reference Production app IDs, environment URLs, SharePoint links, or external services.

Hope it helps.

Original Post https://derivingdynamics.home.blog/2026/05/12/post-copy-environment-hardening-and-reconfiguration-mini-project/