Manage connected agents (Customer Conversation) (preview)

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

After you add a connected agent, you can review its details, update its name and description, or remove it from your primary agent.

View and edit connected agent details

  1. Sign in to Copilot Studio.

  2. Open the primary agent that has the connected agent you want to manage.

  3. On the Build tab, select the primary agent's card to open its configuration panel.

  4. In the components panel, under Connected agents, select the connected agent you want to review. This opens the Edit connected agent dialog.

  5. Review or update the following fields:

    • Name: The connected agent's display name.

    • Description: What the agent specializes in. The orchestrator uses this description to decide when to route requests to the connected agent.

    • Agent Id: The Microsoft Foundry agent identifier. This field isn't editable after the connected agent is added.

  6. Select Save to apply your changes.

Remove a connected agent

  1. On the Build tab, select the primary agent's card to open its configuration panel.

  2. In the components panel, under Connected agents, select the connected agent you want to remove. This opens the Edit connected agent dialog.

  3. Select Remove connected agent.

Note

Removing a connected agent doesn't delete the underlying Microsoft Foundry agent or its connection. It only removes the delegation relationship with your primary agent.

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 (or sub-agents) have similar descriptions, the orchestrator may have difficulty choosing the right one. Make descriptions distinct.
  • Test routing: Use Preview and test your agent 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.