Manage connected agents in an agent (GitHub Copilot)

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

Note

The harness used to build this agent uses usage-based billing. Using, building, testing, and evaluating agents might consume Copilot Credits. Learn more in Overview of usage-based billing.

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 action 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. You can edit the Name and Description fields.

    • Name: The connected agent's display name.

    • Description: What the agent specializes in.

    • Type: The type of agent, such as a Copilot Studio agent, a Foundry agent, an A2A agent, or a Microsoft 365 Agents SDK agent.

    For an A2A agent that uses OAuth 2.0, the dialog also shows a read-only Redirect URL field. Copy this value if you need to register it with your identity provider. Learn more in Add an A2A agent as a connected agent.

  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 might 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. Ensure they don't conflict with the connected agent's domain.

Note

Connected-agent conversations can take longer than single-agent conversations because the connected agent runs in its own orchestration context and any external actions add their processing time. When response time is important, simplify delegated work and optimize external operations.

  • Last updated on