Fix Solution Export Errors for Copilot Studio Agents
Ensure Custom Connectors are in your Dataverse solution before exporting.
To prevent export errors in Copilot Studio agents using MCP tools, manually add the necessary Custom Connectors to your Dataverse solution.
The Scenario
You are a developer trying to move a Copilot Studio agent containing a Confluence search tool from your dev environment to QA.
Before & after
Trying to deploy an agent to a new environment without proper solution mapping often results in export errors that can take 2–3 hours to troubleshoot.
Add the Custom Connector to a Dataverse solution before attempting the export. This configuration fix takes about 5 minutes once identified.
The Prompt
Explain the steps to add the [NAME_OF_CUSTOM_CONNECTOR] to my Dataverse solution called [SOLUTION_NAME] so I can export my Copilot agent without errors.
When working with Copilot Studio and external tools like Confluence, the underlying Custom Connectors must be explicitly added to the Dataverse solution to ensure a clean migration between environments.
Source
Microsoft 365 Copilot | Microsoft Community Hub"Exporting connection reference... for a custom connector requires the custom connector to be added to a Dataverse solution."