Connect a Gateway to Copilot Studio
Add an Airia MCP Gateway to a Microsoft Copilot Studio agent so the agent can call the Gateway's tools.
You can add an Airia MCP Gateway to a Microsoft Copilot Studio agent as a Model Context Protocol (MCP) tool. Once it's connected, the agent can call every tool you selected for the Gateway, and the credentials and tool choices you set in Airia apply to those calls.
This page covers connecting a Gateway you've already created. If you haven't set one up yet, start with Gateway/Deployment Creation.
Before you start
- An Airia MCP Gateway that has at least one app and tool selected.
- A Copilot Studio agent that you can edit, and a Copilot Studio license or trial that lets you add tools to it.
- Generative orchestration turned on for the agent. Copilot Studio uses MCP tools through generative orchestration. New agents have it on by default. To check, open the agent, go to Settings → Generative AI, and confirm Use generative AI orchestration for your agent's responses? is set to Yes.
Copilot Studio connects to your Gateway from Microsoft's cloud, so it uses the same public Gateway URL that Client Setup shows you.
Get the values from Airia
Go to Secure → Gateway → MCP Gateway, find the Gateway you want to connect, and click Client Setup on its card.
Search for and select Microsoft Copilot Studio. Client Setup shows the server name, description, and URL for this Gateway, each with a copy button.
Keep Client Setup open. You'll copy from it in the next section.
Add the Gateway in Copilot Studio
In Copilot Studio, open your agent and go to Tools. Select Add a tool, then select Add new MCP.
Enter these values, copying the name and URL from Client Setup:
| Field | Value |
|---|---|
| Server name | The server name shown in Client Setup |
| Server description | At least 30 characters, for example Airia MCP Gateway tools for this agent |
| Server URL | The Gateway URL shown in Client Setup |
| Authentication | OAuth 2.0, type Dynamic discovery (the default type) |
With Dynamic discovery, Copilot Studio finds the Gateway's sign-in endpoints and registers itself automatically, so there's no client ID or secret to enter.
Select Create. Copilot Studio creates a custom connector for the Gateway. Open the Connection dropdown, select Create new connection, then Create, and complete the Airia sign-in in the window that opens. When the connection shows a green check, select Add.
Check the connection
The tool appears on the agent's Tools page with Enabled on, and opening it lists the Gateway's tools under Tools. To try it, ask the agent something in the Test your agent pane that needs one of the Gateway's tools. The pane's activity view shows each tool call and its result, and each tool call is recorded in Airia under the Gateway's MCP monitoring, with the signed-in user.
To inspect what the Gateway's tools return to the agent, apply a guardrail with the MCP Gateway traffic target. See Managing Policies.
Gateways with Radar enabled
If the Gateway has Radar turned on, Client Setup gives you the Radar URL, which ends in /radar instead of /mcp. Paste it into Server URL as shown. The agent then sees radar_search, radar_execute_tool, and radar_manage_cache, and uses them to find and run the Gateway's tools on demand. If the Gateway has instructions, get_tool_instructions appears as well.
Troubleshooting
Related Resources
How to Set Up a Gateway
Connect a Gateway you've already created to Cursor, Claude, Claude Code, or any other MCP-compatible client.
Connect a Gateway to Microsoft 365 Copilot
Use an Airia MCP Gateway from Microsoft 365 Copilot Chat through a declarative agent, with sign-in through Airia and no Copilot Studio license.