Copilot Studio

Create a gateway from Copilot Studio agent to an internal Azure-hosted MCP server

(1) Share

Report

Posted on by akb1985

We have created an agent in Copilot Studio.

The agent needs to connect to a server hosted in Azure on private network.

We have created a custom connector using a swagger file.

The custom connector is trying to invoke streamable HTTP transport to send JSON-RPC2.0 requests to internal MPC server over HTTPS.

But there is no connection, so we try to create a new connection.

On the next screen we see swagger spec for Copilot Studio custom connector to invoke MCP HTTP transport.

It asks for authentication type and gateway.

We will create the authentication but no gateways were found.

Please advise on next steps.

I am not an expert in this area as you can understand from the question but I am building my expertise.

Categories:

Copilot Studio skills development

Calling actions from Copilot Studio

Copilot Studio pre-built agents/templates

Building Copilot Studio chatbots in Microsoft Teams

All responses (3)

Answers (0)

Sort by

Suggested answer

11manish 4,644 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!

The "No gateways found" message indicates that your Power Platform environment currently does not have the required

gateway/connectivity path to the private Azure network. Resolve that network path first. After connectivity is established,

independently validate whether the custom connector approach supports the

MCP Streamable HTTP/JSON-RPC protocol you are using.
Suggested answer

Valantis 7,381 Super User 2026 Season 2 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @akb1985,

Confirming the core point, No gateways found means exactly that, the on-premises data gateway is a separate agent you install on a machine with network access to your private resource and register to your environment, it doesn't exist by default.

https://learn.microsoft.com/en-us/connectors/custom-connectors/

Worth flagging before you go further down that path though. On-prem gateway is really built for resources behind a corporate firewall or local network, not for something already sitting in Azure on a private VNet. Since your MCP server is Azure hosted, Copilot Studio has a more native path for exactly this, its own VNet integration and network isolation feature, connecting directly into your VNet via private endpoint, no gateway machine needed at all.https://learn.microsoft.com/en-us/microsoft-copilot-studio/admin-network-isolation-vnet

Also worth knowing if you do end up on the gateway route, there's a documented case where the Mcp-Session-Id header doesn't survive the round trip through custom connector, gateway, server, and back, breaking the MCP handshake after the initial connection succeeds. If you get connectivity working but then hit failures right after the handshake, check whether your MCP server supports running stateless.https://github.com/NetApp/ontap-mcp/issues/119

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
Suggested answer

Ashlesha-MSFT Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

The No gateways found message means there is no eligible on-premises data gateway available to the current user. Verify that a standard-mode gateway is online, registered in the correct tenant/region, and that the user has Admin permission because custom connectors require gateway Admin access.

Because the MCP server is hosted behind an Azure private endpoint, the recommended architecture is Power Platform VNet support with subnet delegation and an enterprise policy associated with the Copilot Studio environment. The Gateway selector does not discover Azure VNets or establish this connectivity automatically.

Copilot Studio supports MCP Streamable HTTP through a custom connector when its POST operation specifies x-ms-agentic-protocol: mcp-streamable-1.0. Therefore, first establish private connectivity, confirm DNS/TLS access, re-save the connector, and then test MCP initialization.