An Azure service that provides a hybrid, multi-cloud management platform for APIs.
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:
- Secure MCP servers in API Management
- API Management authentication policies
- Microsoft identity platform OAuth 2.0 authorization code flow
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!