Copy an environment
You can use the Copy option in the Microsoft Power Platform admin center to copy data between environments. You can select two levels of copy: Everything or Customizations and schemas only.
- 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.
- You can only copy to an environment in the same tenant and region.
- 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.
- You can't copy from or to a default or trial type environment.
- Copy and restore operations can take up to 8 hours unless a lot of data, including audit data, needs to be copied or restored, in which case they could take up to 24 hours.
Copy over everything
An Everything copy includes all application data, users, and customizations, and schemas from the source environment and is suitable for:
- User acceptance testing
- Upgrade testing
- Preview in production (TAP/EA)
An example scenario
Isaac, a business application developer, has received a request from the sales department to configure and deploy a social media integration solution from another company vendor. Isaac has never installed a solution from this vendor and is unsure what impact this would have on the production application. Isaac would like to import the solution into an environment that is nearly identical to, but isolated from, production to learn about the solution and make the appropriate configuration changes. Isaac submits a request to Thomas, the IT Manager for Contoso, to create an Everything copy sandbox environment for Isaac.
After the Everything copy is complete, Isaac receives a mail from Thomas telling that the sandbox environment is ready. Isaac logs into the sandbox environment and makes the necessary changes to make sure that production external services won't be impacted by the sandbox environment. Once changes are complete, Isaac turns off administration mode and enables background services. Isaac is able to use the Everything copy sandbox environment to do the testing and later manually import the solution into production.
Copy over customizations and schemas only
Customizations and schemas copy only includes users, customizations, and schema from the source environment and is suitable for:
- Iterative team development
- Partner/ISV solutions
- Proof of concept
An example scenario
Isaac has a large development project starting next week for the sales department. Isaac has a team of developers ready to start on the project, some of whom are internal to Contoso and some are external vendors. The Contoso sales application contains Personally Identifiable Information (PII) that the sales manager has explicitly stated must not be made available to any external parties for privacy and legal liability reasons. Isaac requests customizations and schemas only copy sandbox environment that doesn't contain any production data or users. In addition, Isaac creates a Microsoft 365 security group to give the development team access to the sandbox environment.
After modifying and enabling some of the plug-ins, the developer sandbox environment functions the same and is isolated from the production application. The development team works on their modifications in this environment for several weeks. They package their changes into a solution and export/import to deploy to the Everything copy sandbox environment. After a successful round of testing and signoffs, the changes are manually deployed to production.
Tables truncated in customizations and schemas only copy
The following tables will be truncated when you do a customizations and schemas only copy:
Copy an environment
Go to the Power Platform admin center and sign in using Environment Admin or System Administrator role credentials.
Environment Admins or System Administrators can copy all available environments. System administrators can copy environments for which they have the Environment Admin or System Administrator role.
From the left-side menu, select Environments, and then select an environment to copy.
Select Copy from the top menu bar.
Select the desired copy over level.
If you selected Everything to copy, select whether to copy over audit logs. See the Copying audit logs section.
Select a target environment.
A target environment can be a sandbox or preview environment, not a production environment. If you're copying an environment of type Trial (subscription-based), you'll be able to see and select target environments of the same type, that is Trial (subscription-based).
The target environment will be deleted and replaced with a copy of the data and customizations from the source environment. You won’t be able to recover any deleted data.
To restrict environment access to people in a security group select Edit ().
Edit the details for the copied environment, and then select Copy.
Select Confirm to overwrite the target environment.
The overwrite process starts.
Once the copy process is complete, the target environment is placed in Administration mode and background operations are disabled. The next section describes recommended Administrator actions for the newly created copy (target) environment.
Copying audit logs
Copying audit logs can significantly add to the time it takes to copy an environment and by default isn't done. Do the following steps to include audit logs in the environment copy.
Complete steps 1-5 above.
Under Audit logs, select Click here.
Enable copying audit logs.
Continue with steps 6-9 above.
Next steps after copying an environment
To ensure the newly created copy (target) environment doesn't impact your production environment, once the copy operation is complete, two things happen:
The newly created copy environment is placed in administration mode. Only those with System Administrator security roles can sign in and manage the copy environment. Regular users can't sign in and use the copy environment.
Background operations are disabled in the copy environment. Disabled operations include workflows and synchronization with Microsoft Exchange.
You should review the status of application components in the copy environment with external connections such as Yammer, email, plug-ins, custom workflow activities, etc. Review these and consider what action to take:
Disable the component.
Redirect the component to another service environment such as one running Exchange or SharePoint.
Do nothing – leave the component as is in the copy environment. For example, you might decide to allow Yammer posting to both the copy and production environments.
Here are some possible application components in the copy environment that could have external connections and therefore could impact services with the same connections in your production environment.
Email - A mailbox can't be synced with two different environments. For an Everything copy environment, the user mailboxes in the copy environment must be disabled so the mailboxes don't attempt to send or receive email, or track appointments, contacts, or tasks. Set synchronization for the following to None.
- Incoming Email
- Outgoing Email
- Appointments, Contacts, Tasks
More information: Set the delivery method for incoming and outgoing email
SharePoint - Deactivate or redirect SharePoint to a sandbox SharePoint environment to prevent impacting documents managed by SharePoint. Go to Settings > Documentation Management > SharePoint Sites. Select your site, and then select Deactivate.
Yammer - Disable Yammer or redirect to a separate Yammer service to prevent posts made in the copy environment conflicting with posts made in the production environment. Go to Settings > Administration > Yammer Configuration.
After creating a new sandbox environment, workflows and system jobs might be pending execution. Apart from these jobs, if you've connected Yammer to customer engagement apps there will be Yammer activity streams posted from customer engagement apps to Yammer asynchronously. These activity streams aren't visible through the system jobs. If there were any pending Yammer activity streams before the Disable Background Process is turned on, these activity steams will be posted to the current Yammer configuration once the Disable Background Process is turned back off. In the sandbox environment, if you have your current Yammer configuration connected to the same Yammer network as your production environment, you might see duplicate activity streams. To avoid duplicate Yammer activity streams, redirect your sandbox environment to another Yammer network (possibly a test network) before turning background processes back on.
Platform extensibility - Consider disabling the following that could be running in the copy environment and impacting external service components.
- Server-side plug-ins.
- Workflow custom activity.
Client extensibility - Review the following.
- IFRAMES. Determine if the target of an IFRAME is a production environment.
Dataverse search - Confirm that search returns expected results. If results aren't accurate, you can turn off Dataverse search for 12 hours and then turn Dataverse search back on again to refresh the index. You may contact Microsoft support if you're still experiencing issues.
Flows - In the target environment, existing solution flows will be deleted but existing non-solution flows will remain. Review the flows in the target environment to ensure that triggers and actions are pointing at the correct locations. Solution flows will be disabled so enable flows as needed.
Connection References - Connection References will require new connections. Create and set connections on Connection References.
Custom Connectors - Custom connectors should be reviewed and, if needed, deleted and reinstalled.