wip

gitName · gitName · commit 4cb0b6a42c21 · 2025-07-22T15:40:41.000-07:00
diff --git a/articles/api-management/export-rest-mcp-server.md b/articles/api-management/export-rest-mcp-server.md
@@ -4,7 +4,7 @@ description: Learn how to expose a REST API in Azure API Management as an MCP se
 author: dlepow
 ms.service: azure-api-management
 ms.topic: how-to
-ms.date: 07/18/2025
+ms.date: 07/22/2025
 ms.author: danlep
 ms.collection: ce-skilling-ai-copilot
 ms.custom:
@@ -15,7 +15,7 @@ ms.custom:
 
 [!INCLUDE [api-management-availability-premium-standard-basic-premiumv2-standardv2-basicv2](../../includes/api-management-availability-premium-standard-basic-premiumv2-standardv2-basicv2.md)]
 
-In API Management, you can expose a REST API managed in API Management as a remote [Model Context Protocol (MCP)](https://www.anthropic.com/news/model-context-protocol) server through its built-in [AI gateway](genai-gateway-capabilities.md). Expose one or more of the API operations as tools that MCP clients can call using the MCP protocol. 
+In API Management, you can expose a REST API managed in API Management as a remote [Model Context Protocol (MCP)](https://www.anthropic.com/news/model-context-protocol) server using its built-in [AI gateway](genai-gateway-capabilities.md). Expose one or more of the API operations as tools that MCP clients can call using the MCP protocol. 
 
 [!INCLUDE [preview-callout-mcp-servers](includes/preview/preview-callout-mcp-servers.md)]
 
@@ -30,11 +30,13 @@ Learn more about:
 ## Prerequisites
 
 + If you don't already have an API Management instance, complete the following quickstart: [Create an Azure API Management instance](get-started-create-service-instance.md). 
-    + Your API Management instance must be in one of the supported service tiers for preview: classic Basic, Standard, Premium, Basic v2, Standard v2, or Premium v2.
-    + If your instance is in the classic Basic, Standard, or Premium tier, you must join the **AI Gateway Early** [update group](configure-service-update-settings.md) to access MCP server features. It can take up to 2 hours for the update to be applied.
+    + The following service tiers are supported for preview: classic Basic, Standard, Premium, Basic v2, Standard v2, or Premium v2.
+    + In the classic Basic, Standard, or Premium tier, you must join the **AI Gateway Early** [update group](configure-service-update-settings.md) to access MCP server features. Allow up to 2 hours for the update to be applied.
+
 + Make sure that your instance manages an HTTP-compatible API (any API imported as a REST API, including APIs imported from Azure resources) that you'd like to expose as an MCP server. To import a sample API, see [Import and publish your first API](import-and-publish.md).
     > [!NOTE]
     > Only HTTP APIs managed in API Management can be exposed as MCP servers.
+
 + To test the MCP server, you can use Visual Studio Code with access to [GitHub Copilot](https://code.visualstudio.com/docs/copilot/setup).
 
 
diff --git a/articles/api-management/expose-existing-mcp-server.md b/articles/api-management/expose-existing-mcp-server.md
@@ -4,7 +4,7 @@ description: Learn how to expose and govern an existing Model Context Protocol (
 author: dlepow
 ms.service: azure-api-management
 ms.topic: how-to
-ms.date: 07/14/2025
+ms.date: 07/22/2025
 ms.author: danlep
 ms.collection: ce-skilling-ai-copilot
 ms.custom:
@@ -14,7 +14,7 @@ ms.custom:
 
 [!INCLUDE [api-management-availability-premium-standard-basic-premiumv2-standardv2-basicv2](../../includes/api-management-availability-premium-standard-basic-premiumv2-standardv2-basicv2.md)]
 
-This article shows how to use API Management to expose and govern an existing MCP-compatible server - a tool server hosted outside of API Management. Expose the server's tools through API Management so that MCP clients can call them using the MCP protocol. 
+This article shows how to use API Management to expose and govern an existing MCP-compatible server - a tool server hosted outside of API Management. Expose the server's tools through API Management using its built-in [AI gateway](genai-gateway-capabilities.md) capabilities so that MCP clients can call them using the MCP protocol. 
 
 [!INCLUDE [preview-callout-mcp-servers](includes/preview/preview-callout-mcp-servers.md)]
 
@@ -36,20 +36,23 @@ Learn more about:
 ## Prerequisites
 
 + If you don't already have an API Management instance, complete the following quickstart: [Create an Azure API Management instance](get-started-create-service-instance.md). 
-    + Your API Management instance must be in one of the supported service tiers for preview: classic Basic, Standard, Premium, Basic v2, Standard v2, or Premium v2.
-    + If your instance is in the classic Basic, Standard, or Premium tier, you must join the **AI Gateway Early** [update group](configure-service-update-settings.md) to access MCP server features. It can take up to 2 hours for the update to be applied.
+    + The following service tiers are supported for preview: classic Basic, Standard, Premium, Basic v2, Standard v2, or Premium v2.
+    + In the classic Basic, Standard, or Premium tier, you must join the **AI Gateway Early** [update group](configure-service-update-settings.md) to access MCP server features. Allow up to 2 hours for the update to be applied.
+
 + Access to an external MCP-compatible server (for example, hosted in Azure Logic Apps, Azure Functions, LangServe, or other platforms).
+
 + Appropriate credentials to the MCP server (OAuth 2.0 client credentials or API keys) for secure access.
+
 + To test the MCP server, you can use Visual Studio Code with access to [GitHub Copilot](https://code.visualstudio.com/docs/copilot/setup).
 
-## Expose an existing MCP Server
+## Expose an existing MCP server
 
-Follow these steps to expose an existing MCP server to API Management:
+Follow these steps to expose an existing MCP server is API Management:
 
 1. In the [Azure portal](https://portal.azure.com), navigate to your API Management instance.
     [!INCLUDE [preview-callout-mcp-feature-flag](includes/preview/preview-callout-mcp-feature-flag.md)]
 
-1. In the left-hand menu, select **MCP servers** > **+ Create MCP server**.
+1. In the left-hand menu, under **APIs**,select **MCP servers** > **+ Create MCP server**.
 1. Select **Connect existing MCP server**.
 1. In **Backend API**:
     1. Enter the existing **MCP server base URL**.
diff --git a/articles/api-management/includes/preview/preview-callout-mcp-servers.md b/articles/api-management/includes/preview/preview-callout-mcp-servers.md
@@ -7,4 +7,5 @@ ms.date: 07/16/2025
 ---
 
 > [!IMPORTANT]
-> This feature is in preview. Review the [prerequisites](#prerequisites) to access MCP server features. In preview, API Management supports MCP server tools, but doesn't currently support MCP resources or prompts.
+> * This feature is in preview. Review the [prerequisites](#prerequisites) to access MCP server features. 
+> * In preview, API Management supports MCP server tools, but doesn't currently support MCP resources or prompts.
diff --git a/articles/api-management/mcp-server-overview.md b/articles/api-management/mcp-server-overview.md
@@ -100,7 +100,15 @@ One option to secure inbound access is to configure a policy to validate a JSON
 
 ```
 
-> [!IMPORTANT]
+For more inbound authorization options and samples, see:
+
+* [MCP server authorization with Protected Resource Metadata (PRM) sample](https://github.com/blackchoey/remote-mcp-apim-oauth-prm)
+
+* [Secure Remote MCP Servers using Azure API Management (Experimental)](https://github.com/Azure-Samples/remote-mcp-apim-functions-python)
+
+* [MCP client authorization lab](https://github.com/Azure-Samples/AI-Gateway/tree/main/labs/mcp-client-authorization)
+
+> [!CAUTION]
 > When you use an MCP server in API Management, incoming headers like **Authorization** aren't automatically passed to your backend API. If your backend needs a token, you can add it as an input parameter in your API definition. Alternatively, use policies like `get-authorization-context` and `set-header` to generate and attach the token, as noted in the following section.
 
 
@@ -151,9 +159,7 @@ MCP servers in API Management are available in the following service tiers:
 
 ## Related content
 
-* [Python sample: Secure remote MCP servers using Azure API Management (experimental)](https://github.com/Azure-Samples/remote-mcp-apim-functions-python)
 
-* [MCP client authorization lab](https://github.com/Azure-Samples/AI-Gateway/tree/main/labs/mcp-client-authorization)
 
 * [Use the Azure API Management extension for VS Code to import and manage APIs](visual-studio-code-tutorial.md)
 
diff --git a/includes/api-management-configure-test-mcp-server.md b/includes/api-management-configure-test-mcp-server.md
@@ -28,7 +28,7 @@ To configure policies for the MCP server:
 
 ## Validate and use the MCP server
 
-Use a compliant LLM agent (such as GitHub Copilot, Semantic Kernel, or Copilot Studio) or a test client (such as `curl`) to call the API Management-hosted MCP endpoint, ensure the request includes appropriate headers and tokens, and confirm successful routing and response from the MCP server.
+Use a compliant LLM agent (such as GitHub Copilot, Semantic Kernel, or Copilot Studio) or a test client (such as `curl`) to call the API Management-hosted MCP endpoint. Ensure that the request includes appropriate headers or tokens, and confirm successful routing and response from the MCP server.
 
 > [!TIP]
 > If you use the [MCP Inspector](https://modelcontextprotocol.io/docs/tools/inspector) to test an MCP server managed by API Management, we recommend using version 0.9.0.
