Introduction
In Microsoft Copilot Studio, a solution often spans several agents that different teams own and maintain. After you decide which agents your solution needs, the next job is to make sure each request reaches the agent that owns it. A primary agent powered by the GitHub Copilot harness can delegate conversation requests to connected agents, and a Copilot Studio workflow can call a published agent from an agent node for a single step.
Suppose you maintain a front-door help agent for employees. The IT team owns an IT support agent that handles device and access requests, and the HR team owns an HR benefits agent that answers benefits questions. Employees ask your agent general questions, IT questions, and benefits questions, and you want the IT and benefits requests to reach the agents those teams maintain. Separately, an onboarding workflow runs when a new-hire record is created, and one of its steps needs the HR benefits agent to draft a benefits summary for the new employee.
In this module, you explore:
- How to prepare an agent for other agents to connect.
- How to add a connected agent with a routing description.
- How to test and troubleshoot delegation.
- How to call an agent from a workflow agent node.
By the end of this module, you'll be able to connect specialist agents to a primary agent powered by the GitHub Copilot harness, confirm that requests reach the right agent, and call a published agent from a workflow.