calling another env co pilot studio agent

(0) Share

Report

Posted on by PS-11060041-0 Microsoft Employee

I have a Copilot Studio knowledge agent and would like it to call another Copilot Studio agent when it cannot find an answer. What is the best and easiest way to implement this?
For business reasons we cannot move both the agents to same environment.

Thanks

Categories:

General topics

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Suggested answer

chiaraalina 2,318 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @PS-11060041-0

Here it is recommended to use the Agent-to-Agent (A2A) Protocol. The sandard exposes the second agent as an external agent accessible via HTTPS endpoint with OAuth authentication. This is required because native multi-agent orchestration only works within the same environment.

Let me know if you want to implement this and need help!

Was this reply helpful? Yes No
Suggested answer

Sunil Kumar Pashikanti 2,111 Moderator on at

Like (1)

Report
Copy link

Link copied!
Hi @PS-11060041-0,

If you want one Copilot Studio agent to call another in a different environment, using a fallback is the right approach. The catch is there’s no built-in way to do this, so you need a small workaround.
Also, Direct Line (what you’ll use under the hood) isn’t a simple API call. It’s a multi-step process, so you usually wrap it to keep things clean.

Two practical options:
Option 1: Custom Connector + API wrapper (recommended)

Treat the second agent like an external service.

Put a small wrapper (Azure Function, etc.) in front of Agent B

Create a Custom Connector in Agent A

Call it from your fallback topic

This keeps things clean and easier to maintain.

Option 2: Power Automate + HTTP
Use a flow as a bridge.

Agent A triggers a flow

Flow calls Agent B via Direct Line

Returns the response

Works fine, but adds some delay since every call runs a flow.

Key points

No native “call another Copilot” feature yet
Direct Line is required (and a wrapper helps a lot)
Keep both environments in the same tenant and check DLP policies

Recommendation
Go with the Custom Connector + wrapper if this is more than a quick POC. It’s cleaner and scales better.

✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
👍 Feel free to Like the post if you found it useful.

Sunil Kumar Pashikanti, Moderator
Blog: https://sunilpashikanti.com/posts/

Was this reply helpful? Yes No
Suggested answer

11manish 2,837 on at

Like (0)

Report
Copy link

Link copied!

For agents that must remain in separate environments, the easiest and most supportable approach is:

Use a Power Automate flow as an intermediary. Configure Agent A to call the flow when no answer is found, have the flow query Agent B, and return the response back to the user.

This provides the cleanest cross-environment solution while maintaining your business and governance requirements.

Was this reply helpful? Yes No
Suggested answer

Valantis 6,290 on at

Like (0)

Report
Copy link

Link copied!

Hi @PS-11060041-0,

The answers above cover it well. One thing to add on the A2A Protocol chiaraalina mentioned: Microsoft is rolling out native Agent-to-Agent (A2A) support in Copilot Studio which will eventually handle cross-environment agent calls more cleanly. It's currently in preview so for production today, Sunil's Custom Connector + wrapper approach is the most reliable.

For your specific scenario (fallback when no answer found), the Power Automate approach is actually the simplest to implement quickly:

1. Create a fallback topic in Agent A that triggers when confidence is low
2. Call a Power Automate flow that queries Agent B via Direct Line API
3. Return Agent B's response back to the user

The Direct Line token endpoint for Agent B is in Copilot Studio > Channels > Custom website > Token endpoint. Keep that secured and don't expose it in client-side code.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
Suggested answer

Sayali-MSFT Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hello @PS-11060041-0,

Use the Fallback topic + Power Automate flow to call another agent when no answer is found, and invoke the second agent via Direct Line API or custom connector since cross‑environment agent calling isn’t natively supported.
Reference Document-
1.Use the Fallback topic - Microsoft Copilot Studio | Microsoft Learn
2.Publish agents to channels and clients - Microsoft Copilot Studio | Microsoft Learn

Was this reply helpful? Yes No