Hi everyone,
We’re currently building an orchestrator agent in Copilot Studio designed to delegate tasks to other specialized agents. However, we’re hitting a limitation we weren’t expecting — and I’d love to know if others have encountered (and solved) this
Scenario
We have:
-
A Commercial Orchestrator Agent that delegates to an Account Management Agent.
-
The Account Management Agent includes a Dataverse MCP Agent as a tool, which is responsible for handling actions like querying and creating accounts.
Behavior Observed
-
When interacting directly with the Account Management Agent, prompts like:
-
“What accounts do I have?”
-
“Can I create an account with the name 'X'?”
generally work — although with some occasional, expected instability
-
-
However, when performing the same queries through the Orchestrator Agent, we can see that the child agent is invoked, but it never progresses to execute the MCP Server calls
Issue
It seems that MCP calls/tools are not invoked when the child agent is called via orchestration. This is not explicitly documented as a limitation here:
🔗 Add other agents (preview) - Microsoft Copilot Studio | Microsoft Learn
Question
-
Has anyone else run into this behavior?
-
Is there a known workaround or a best practice to make this delegation work seamlessly?
Current Workaround
We’ve managed to work around it by calling agents via agent flows and leveraging native connector actions, manually passing parameters like the conversation ID to preserve context. But this approach feels quite messy and unscalable for complex orchestrations.

Report
All responses (
Answers (