Manage connected agents in an agent (preview)

[This article is prerelease documentation and is subject to change.]

After you add connected agents to your agent, you can view their details and remove agents you no longer need.

Note

This article reflects the new agent experience in Microsoft Copilot Studio, which is currently available as a production-ready preview. Learn about the two experiences in Classic vs. new agent experience.

  • Production-ready previews are subject to supplemental terms of use.
  • Some capabilities available in the classic experience aren't yet available in the new experience.
  • Agents created in the new experience can't be converted to the classic experience.

View and edit connected agent details

  1. Sign in to Copilot Studio.

  2. Open your primary agent.

  3. In the agent navigation bar, select the Build tab.

  4. In the components panel on the right, Select any agent under the Connected agents button to view more details. This opens the Edit connected agent dialog.

  5. The Edit connected agent dialog shows the connected agent's name, description, and details.

  6. Review the agent configuration to ensure it aligns with your primary agent's goals. The Name and Description fields are editable.

    • Name: The connected agent's display name.

    • Description: What the agent specializes in.

    • Type: The type of agent. Currently, only Copilot Studio agents can be connected.

  7. Select Save to apply changes to the connected agent.

Remove a connected agent

  1. On the Build tab, locate the connected agent in the components panel under the Connected agents button.

  2. Select the X next to the connected agent.

  3. When prompted, select Remove to confirm your choice.

Note

Removing a connected agent from your agent doesn't delete the connected agent itself. It only removes the delegation relationship.

Troubleshoot routing issues

If a connected agent isn't being invoked when expected:

  • Check the description: The connected agent's description must clearly describe its domain so the orchestrator can route to it.
  • Avoid overlap: If multiple connected agents have similar descriptions, the orchestrator may have difficulty choosing the right one. Make descriptions distinct.
  • Test in Preview: Use the Preview tab to send test messages and verify routing behavior.
  • Review primary instructions: Your primary agent's instructions can influence routing decisions. Make sure they don't conflict with the connected agent's domain.