Power Platform Community Forum Thread Details

This is Yokoo from KINTO Technologies Inc.
We are planning to migrate the Copilot Studio agent flows and Power Automate cloud flows that we have currently developed to a different tenant.

We would like to confirm the following points, and would appreciate your responses to each of them:

1.We have reviewed the following document, but is it possible to specify individual resources to be migrated rather than migrating the entire source flow?
https://learn.microsoft.com/en-us/power-platform/admin/move-environment-tenant
2.The document states, “Environments are not actually moved but linked to another tenant. The environment exists but is no longer part of the source tenant.” Is our understanding correct that this means the source resources are not fully migrated? Also, is there a way to fully migrate resources to the destination tenant?
3.If there is any documentation summarizing resources that are not migrated (such as connection resource credentials), could you please share it with us?

Thank you very much for your assistance.

Best regards,
Yokoo
KINTO Technologies Inc.

Categories:

General topics

Hi @HY-01080400-0

I am not 100% sure why you are looking at Environment migration, when your question is related to (Solution) migration that has components in it.

Can you please clarify if you want to move an environment or just components of a Solution

If you simply want to install stuff from one Tenant into another that is bread and butter basic. As long as you are using Environment Variables or some other Configurable components, you should export the Solution either as a Managed (you do not want people changing things) or Unmanaged (So that you can make the other tenant/environment) the owner of the stuff and changable.

Just think of your other environment as a Customer to your Solution. The only difference is usually with customers you give them Managed Solutions as they can only change values for Environment variables etc.

Where in your case, if you are moving the stuff, then export as Unmanaged and Import as Unmanaged. Then delete the solution from the older Tenant/Environment, then go into the Default Solution IN that environment and manually remove connection references etc you don't want to keep anymore)

now it will be all moved to the other tenant/environment and be seen as that new tenant/environment will be the Dev starting point.

If these suggestions help resolve your issue, Please consider Marking the answer as such and also maybe a like.

Thank you!
Sincerely, Michael Gernaey