Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device.
Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
/
Moving Agents to Another Environment using Pipelines
Moving Agents to Another Environment using Pipelines
If you are set up with multiple Power Platform environments or are needing to move an existing agent to a production environment from a developer environment, the simplest way is to package it in a solution and deploy it using a pipeline.
This article is not intended to cover large CI/CD deployments or version control in Power Platform or Power Apps. Simply moving an agent from one environment to another without exporting a solution.
If you have reached out to AI Studio or the M365 Team and received a Production or Sandbox environment for the purposes of collaboration and/or setting up PAYG and you’ve already created an agent in your personal development environment.
You want to migrate existing agents into a different Production or Sandbox environment.
Your agent will remain in the old environment, and a new version will be available in the new environment. This document guides you on doing an “Unmanaged” deployment, so the new agent can be edited in the new environment without continuing to use pipelines to update it, effectively migrating it.
If you can’t edit the agent in the new environment, it is because you have deployed it as “Managed” and it will rely on updating your agent in it’s original environment and pushing the updates through the pipeline. This document does not cover this.
First Step: Creating Solutions
In Copilot Studio using your source environment (the one with the agent), click on the ellipsis on the left toolbar and select “Solutions”
Once it loads, click on “+New solution” at the top of the page.
In the form:
Display Name: This is the Solution display name not the Agent name.
Name: This is the Solution name not the Agent name.
Publisher: You can use Default, or create a new publisher.
Version: Default
Set as preferred: No
Click Create
Once you have created the Solution, you can find it back in the Solutions tab from earlier.
Click on the new Solution you just created and open it, at the top of the page you should see “Add Existing”
Click on Agent > Agent
Click on the Agent in the list that you want to move, and click “Add”
This will take a few seconds, up to a minute to add.
Once it’s finished go back to your Solutions page.
Deploy (Move)
Within the Solutions page, click on the context menu for the solution that you wish to deploy. Click on Deploy.
If you don’t already have a pipeline that is appropriate for this solution, click on “+ Create new pipeline”
Give the new pipeline a name and a description. Choose your Target Environment for the pipeline and click save.
Chose the pipeline from the dropdown.
Click Deploy Here
Keep the defaults unless you want to deploy the solution later. You can chose the date and time of the deployment.
Edit your deployment notes if needed, and the version number if needed, though both of those things are auto generated.
Click Deploy - it will take a few minutes for the solution to show up in the other environment.