Skip to content
Home » How to Move Your Microsoft Copilot from Development to Production Using Solutions

How to Move Your Microsoft Copilot from Development to Production Using Solutions

If you’ve built a Copilot agent in a development or lower environment and are ready to move it to your production or live environment, this guide will walk you through the key steps. Thanks to Microsoft’s tools, moving Copilot components between environments using Power Apps solutions is straightforward — but there are some important details to keep in mind.

What Are Solutions in Power Apps?

In Microsoft Power Apps, a solution is essentially a container for all the components you build — like your Copilot agents, topics, connections, flows, and custom connectors. Packaging your Copilot into a solution allows you to export it from one environment (such as development) and import it into another (such as production).


Step-by-Step: Adding Your Copilot to a Solution

  1. Open the Power Apps Maker Portal
    Navigate to make.powerapps.com and go to the Solutions area.
  2. Create or Select a Solution
    If you haven’t already, create a new solution container — for example, “Weather Copilot Solution.” This will hold your Copilot and its related components.
  3. Add Your Copilot Agent to the Solution
    Click Add existing > Agent, then select the Copilot agent you want to move — for example, your “Weather Agent.”
    This action will automatically include all associated topics and any connection references your agent uses, such as connections to external APIs or Power Automate flows.
  4. Add Additional Components
    If your Copilot uses Power Automate flows or custom connectors, add those to the solution as well under the appropriate categories to ensure everything needed is packaged.

Exporting and Importing Your Solution

Once your solution is complete:

  • Click the three dots next to the solution name and select Export Solution.
  • You’ll be prompted to choose between a managed or unmanaged solution:
    • Managed: Components are locked and cannot be modified in the target environment (ideal for production).
    • Unmanaged: Components can be edited after import.
  • Choose Managed for production to prevent accidental edits.
  • Export the solution, which will generate a ZIP file.
  • Download the ZIP file when the export finishes.

To import the solution into your production environment:

  • Go to the Power Apps Maker Portal in the production environment.
  • Navigate to Solutions and select Import Solution.
  • Upload the exported ZIP file and follow the prompts.
  • After import, your Copilot agent and all components will be available in the new environment.
Copilot Studio Widget
Copilot Studio Logo

MASTER COPILOT STUDIO AGENTS

Get the 10 Commandments of Copilot Agents (Free)

Want to learn the Pro Tips of Copilot Agents? Get this free resource sent right to your inbox.


Important Tips

  • Always publish all customizations before exporting to ensure all your latest changes are included.
  • Dependencies between components will be checked during export; missing dependencies can block the process.
  • Using managed solutions in production helps maintain stability and prevents unintentional changes.
  • Copilot components are fully solution-aware, which means you can leverage Power Apps solution management best practices when deploying.

Happy Developing!