preview limitations

Author: gitName

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/23/2025
+ms.date: 07/25/2025
 ms.author: danlep
 ms.collection: ce-skilling-ai-copilot
 ms.custom:
@@ -27,6 +27,13 @@ Learn more about:
 * [AI gateway capabilities](genai-gateway-capabilities.md)
 
 
+## Limitations
+
+The following limitations currently apply to this preview:
+
+* API Management supports MCP server tools, but doesn't support MCP resources or prompts.
+* MCP server capabilities aren't supported in API Management [workspaces](workspaces-overview.md).
+
 ## 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). 
@@ -45,8 +52,6 @@ Learn more about:
 Follow these steps to expose a managed REST API in API Management as an MCP server:
 
 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 menu, under **APIs**, select **MCP Servers** > **+ Create MCP server**.
 1. Select **Expose an API as an MCP server**.
 1. In **Backend MCP server**:

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/23/2025
+ms.date: 07/25/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 and govern 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 remote [Model Context Protocol (MCP)](https://www.anthropic.com/news/model-context-protocol) server - a tool server hosted outside of API Management. Expose and govern the server's tools through API Management so that MCP clients can call them using the MCP protocol. 
 
 [!INCLUDE [preview-callout-mcp-servers](includes/preview/preview-callout-mcp-servers.md)]
 
@@ -32,6 +32,19 @@ Learn more about:
 * [MCP server support in API Management](mcp-server-overview.md)
 * [AI gateway capabilities](genai-gateway-capabilities.md)
 
+## Limitations
+
+The following limitations currently apply to this preview:
+
+* The external MCP server must conform to MCP version `2025-06-18` or later. The server must support:
+    * Either no authorization or authorization protocols that comply with the following standards: [https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization#standards-compliance](https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization#standards-compliance) 
+    * Streamable HTTP transport
+
+    > [!IMPORTANT]
+    > Servers conforming to older MCP versions or using SSE transport only are not supported.
+
+* API Management supports MCP server tool capabilities, but not MCP resources or prompts.
+* MCP server capabilities aren't supported in API Management [workspaces](workspaces-overview.md).
 
 ## Prerequisites
 
@@ -50,8 +63,6 @@ Learn more about:
 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, under **APIs**, select **MCP servers** > **+ Create MCP server**.
 1. Select **Expose an existing MCP server**.
 1. In **Backend MCP server**:

articles/api-management/includes/preview/preview-callout-mcp-feature-flag.md

@@ -7,5 +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 and has some [limitations](#limitations)
+> * Review the [prerequisites](#prerequisites) to access MCP server features. 

articles/api-management/includes/preview/preview-callout-mcp-servers.md

@@ -129,6 +129,7 @@ The following constraints currently apply to workspace gateways:
 * Workspace gateways support only internal cache; external cache isn't supported 
 * Workspace gateways don't support synthetic GraphQL APIs
 * Workspace gateways don't support creating APIs directly from Azure resources such as Azure OpenAI Service, App Service, Function Apps, and so on
+* Workspace gateways don't support MCP servers
 * Request metrics can't be split by workspace in Azure Monitor; all workspace metrics are aggregated at the service level
 * Workspace gateways don't support CA certificates
 * Workspace gateways don't support managed identities, including related features like storing secrets in Azure Key Vault and using the `authentication-managed-identity` policy