Connect a Microsoft Foundry agent to Copilot Studio
Diesen Beitrag auf Deutsch lesen
Add an existing Microsoft Foundry agent to Copilot Studio as an external agent using the project endpoint and agent ID.
Original article from September 7, 2026: Connect a Microsoft Foundry agent to Copilot Studio, on reshmeeauckloo.com. Read the original
Source may be outdated. The original article is more than 60 days old. Dates and availability refer to the state of the source.
This is our own summary, not a republication or full translation.
TL;DR
Copilot Studio can add a Microsoft Foundry agent as an external agent by using the Foundry project endpoint, a trailing slash, and the target agent ID, then testing the connection. The source also lists an existing Foundry project and agent as prerequisites.
Why it matters
- Makers: Prepare the Foundry project endpoint and agent ID, add Microsoft Foundry as the external agent type, and test invocation in Copilot Studio.
- Admins/IT: Verify access to the Foundry agent and append a trailing slash to the project endpoint, because omitting it can cause a 400 error or other errors.
Frequently asked questions
What endpoint format does a Copilot Studio Foundry connection use?
The connection uses the Microsoft Foundry project endpoint, including the resource name and project name in the services.ai.azure.com address.
Why must the Microsoft Foundry project endpoint end with a slash in Copilot Studio?
The endpoint needs a trailing slash after it is pasted into the connection dialog. Without it, the connection can produce a 400 error or other errors.
Which Microsoft Foundry agent detail must be entered in Copilot Studio?
Copilot Studio requires the target agent ID from Microsoft Foundry, along with the project endpoint, before the external agent can be saved and tested.