Connect Microsoft Foundry agents securely in Copilot Studio
Diesen Beitrag auf Deutsch lesen
A practical demo shows how to connect Azure AI Foundry agents to Copilot Studio with Entra ID authentication and traceable calls.
TL;DR
Copilot Studio connects an Azure AI Foundry agent by using its agent name and endpoint URL, selecting Connect to an external agent, choosing Microsoft Foundry, authenticating through Microsoft Entra ID, and submitting the endpoint. Foundry traces then expose inputs, outputs, IDs, and completion timestamps.
Original by Jay Padimiti, on The Custom Engine. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Use connected agents when one agent becomes difficult to manage, so domain specialists can handle focused tasks.
- Admins/CoE: Capture the Foundry agent name and endpoint, then configure the external connection through Microsoft Entra ID.
- Security/Compliance: Review authenticated cross-agent communication and Foundry trace data, including inputs, outputs, correlation IDs, and timestamps.
Frequently asked questions
How do I connect a Microsoft Foundry agent to Copilot Studio?
Select Connect to an external agent, choose Microsoft Foundry, authenticate through Entra ID, and enter the Foundry endpoint URL.
How does Copilot Studio choose between connected Foundry and Copilot agents?
It selects the appropriate agent from metadata, routing biology and algebra questions without custom routing logic.
What does the Foundry trace view show after Copilot Studio calls an agent?
It shows the received input, generated output, conversation or correlation IDs, and completion timestamps for debugging.