Forum Discussion
Error Exporting Solution - Copilot Studio Agent with Confluence MCP “search” Tool
hi sohnash This one does smell like a product limitation / bug, not something you’re missing.
What’s happening (based on similar cases we’ve seen):
Copilot Studio agents export cleanly when they use standard MCP tools (like searchConfluenceUsingCql) because those tools are fully backed by a solution-aware custom connector.
The Rovo “search” tool is different. Under the hood, it’s treated more like a first party / preview capability, even though it shows up under the Confluence MCP.
Because of that, the connection reference gets created, but the underlying connector metadata is not properly solution-bound, so Dataverse can’t serialize it during export hence the error you’re seeing.
That explains why:
Adding the custom connector manually doesn’t help
The same pattern works fine with non-Rovo tools
Current reality (unfortunately)
Rovo “search” via Confluence MCP is not yet supported for ALM / solution export
This is a known gap, even if it’s not well-documented yet
Workarounds people are using
Avoid Rovo “search” for now
- Stick with searchConfluenceUsingCql for anything that needs to move across environments.
Environment-specific rebuild (not ideal)
- Recreate the agent manually in QA/Prod if Rovo search is a hard requirement.
Split the solution
- Keep the agent logic exportable and re-attach the Rovo-based capability post-import (manual step).
Recommendation
If this is production-bound, I’d:
- Raise this via Microsoft Support or Power Platform support ticket
- Reference: Copilot Studio agent + Confluence MCP + Rovo search failing solution export due to connector not being solution-aware
You’re not doing anything wrong , this is a maturity gap in the Rovo integration today. Hopefully Microsoft closes it soon, because this breaks standard ALM patterns badly.