Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
[This article is prerelease documentation and is subject to change.]
Use connected agents to let your primary agent delegate specific tasks to specialized agents. This article shows you how to add a connected agent and verify that delegation works as expected.
Note
This article reflects the new experiences for creating agents and workflows in Microsoft Copilot Studio. The new agent experience is currently available as a production-ready preview. Learn about the two agent experiences in Classic vs. new agent experience. The new workflows experience is in public preview. Learn about the two workflows experiences in Workflows overview.
- Public preview features aren't meant for production use and might have restricted functionality.
- Production-ready and public previews are subject to supplemental terms of use.
- Some capabilities available in the classic experience aren't yet available in the new experience.
- Agents and workflows created in the new experience can't be converted to the classic experience.
Prerequisites
- An agent created in the new experience to be the primary agent. See Create an agent (preview).
- At least one other new experience Copilot Studio agent in the same environment. The other agent must be published and configured as available to connect.
- The maker for the primary agent must either be the owner of the connected agent or have the agent shared with them.
Add a connected agent
Sign in to Copilot Studio.
Choose and open the agent you want to use as the primary agent.
In the agent navigation bar, select the Build tab.
In the components panel, select Connected agents to open the Add a connected agent dialog.
From the Add a connected agent dialog, browse or search the available agents and select the agent you want to connect.
Review the agent's capabilities, then add a clear description of when the connected agent should be used.
Select Connect.
Confirm the connected agent appears in the components panel.
How the orchestrator routes to connected agents
After adding a connected agent, the orchestration runtime automatically determines when to delegate to it. The routing decision is based on:
- The connected agent's name and description
- The user's message and conversation context
- Your primary agent's instructions
Tip
Write a clear, specific description for each connected agent so the orchestrator can accurately determine when to route requests to it. Avoid overlapping descriptions between connected agents.
Test delegation
After adding a connected agent:
In the agent navigation bar, select the Preview tab.
Send a message that matches the connected agent's domain.
Verify that the response comes from the connected agent and is appropriate.
Send a message outside the connected agent's domain to confirm it's handled by your primary agent.