Copilot Studio connects to APIM MCP Server

Amy Zhang 40 Reputation points
2025-09-18T10:49:35.2+00:00

We're trying to connect to APIM MCP server from Copilot Studio Tools, but we’re unsure how to configure the following fields:

(1) API Key (2) OAuth 2.0

The screenshot is below

User's image

Based on this page : Secure access to MCP servers in API Management

https://learn.microsoft.com/en-us/azure/api-management/secure-mcp-servers

It says ( My Notes )

You can secure either or both inbound access to the MCP server (from an MCP client to API Management) and outbound access (from API Management to the MCP server).

A) Secure inbound access

A1. Key-based authentication (APIM subscription key)

A2. Token-based authentication (OAuth 2.1 with Microsoft Entra ID)

B) Secure outbound access

B1. Steps to configure OAuth 2-based outbound access

Question

When Copilot connects to the APIM MCP server, how should I interpret the two authentication fields?

  • Is (1) API Key mapped to inbound access → A1 (subscription key)?
  • Is (2) OAuth 2.0 mapped to inbound access → A2, or is it meant for outbound access → B1?

In other words, does Copilot’s “API Key” strictly correspond to APIM’s subscription key for inbound calls, while “OAuth 2.0” is used for token-based inbound or outbound authentication?

Need your advice

Thank you

Azure API Management
Azure API Management

An Azure service that provides a hybrid, multi-cloud management platform for APIs.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Anurag Rohikar 3,190 Reputation points Microsoft External Staff Moderator
    2025-09-19T09:02:58.87+00:00

    Hello Amy Zhang,

    When you connect Copilot Studio Tools to an APIM-hosted MCP server, the two authentication choices in Copilot’s configuration apply only to inbound authentication on APIM—not outbound.

    • API Key corresponds to key-based inbound access (APIM subscription key). Use your APIM subscription key here Copilot will include it as the Ocp-Apim-Subscription-Key header when calling the MCP endpoint.
    • OAuth 2.0 corresponds to token-based inbound access using Microsoft Entra ID (Azure AD). Use this if your APIM instance is secured with OAuth. You’ll provide your Client ID, Client Secret, Authorization URL, and Token URL from your Entra app registration.

    Outbound authentication (APIM → backend MCP server) is configured within APIM itself, not in Copilot Studio. Choose either API Key or OAuth 2.0 based on how you secured your APIM endpoint don’t configure both unless APIM explicitly allows multiple methods.

    References:

    This setup ensures Copilot Studio authenticates properly with APIM while leaving outbound security entirely under APIM’s control.

    I hope the above information helps. Please let us know if you have any further questions. Thank you!

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.