Skip to content

Commit 573a031

Browse files
author
gitName
committed
edits
1 parent 48bae19 commit 573a031

7 files changed

+25
-26
lines changed

‎articles/api-management/api-management-features.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,8 @@ Each API Management [pricing tier](api-management-key-concepts.md#api-management
5252
| Static IP | No | Yes | Yes | No |Yes | No | Yes | No |
5353
| Export API to Power Platform | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
5454
| Export API to Postman | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
55-
| Export API to MCP server (preview) | No | No | Yes | No | Yes | No | Yes | No |
55+
| Export API to MCP server (preview) | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
56+
| Expose existing MCP server (preview) | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
5657

5758
<sup>1</sup> Enables the use of Microsoft Entra ID (and Azure AD B2C or [Microsoft Entra External ID](/entra/external-id/customers/overview-customers-ciam)) as an identity provider for user sign in on the developer portal.<br/>
5859
<sup>2</sup> Including related functionality such as users, groups, issues, applications, and email templates and notifications.<br/>

‎articles/api-management/api-management-gateways-overview.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -77,12 +77,12 @@ The following tables compare features available in the following API Management
7777
| [Built-in cache](api-management-howto-cache.md) | ✔️ | ✔️ | ❌ | ❌ | ✔️ |
7878
| [External Redis-compatible cache](api-management-howto-cache-external.md) | ✔️ | ✔️ |✔️ | ✔️ | ❌ |
7979
| [Virtual network injection](virtual-network-concepts.md) | Developer, Premium | Premium v2 | ❌ | ✔️<sup>1,2</sup> | ✔️ |
80-
| [Inbound private endpoints](private-endpoint.md) | Developer, Basic, Standard, Premium | Standard v2 | ❌ | ❌ | ❌ |
80+
| [Inbound private endpoints](private-endpoint.md) | ✔️ | Standard v2 | ❌ | ❌ | ❌ |
8181
| [Outbound virtual network integration](integrate-vnet-outbound.md) | ❌ | Standard v2, Premium v2 | ❌ | ❌ | ✔️ |
8282
| [Availability zones](zone-redundancy.md) | Premium | ❌ | ❌ | ✔️<sup>1</sup> | ❌ |
8383
| [Multi-region deployment](api-management-howto-deploy-multi-region.md) | Premium | ❌ | ❌ | ✔️<sup>1</sup> | ❌ |
8484
| [CA root certificates](api-management-howto-ca-certificates.md) for certificate validation | ✔️ | ❌ | ❌ | ✔️<sup>3</sup> | ❌ |
85-
| [Managed domain certificates](configure-custom-domain.md?tabs=managed#domain-certificate-options) | Developer, Basic, Standard, Premium | ❌ | ✔️ | ❌ | ❌ |
85+
| [Managed domain certificates](configure-custom-domain.md?tabs=managed#domain-certificate-options) | ✔️ | ❌ | ✔️ | ❌ | ❌ |
8686
| [TLS settings](api-management-howto-manage-protocols-ciphers.md) | ✔️ | ✔️ | ✔️ | ✔️ | ❌ |
8787
| **HTTP/2** (Client-to-gateway) | ✔️<sup>4</sup> | ✔️<sup>4</sup> |❌ | ✔️ | ❌ |
8888
| **HTTP/2** (Gateway-to-backend) | ❌ | ✔️<sup>5</sup> | ❌ | ✔️<sup>5</sup> | ❌ |
@@ -114,8 +114,7 @@ The following tables compare features available in the following API Management
114114
| [Azure OpenAI and LLM](azure-openai-api-from-specification.md) | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
115115
| [Circuit breaker in backend](backends.md#circuit-breaker) | ✔️ | ✔️ | ❌ | ✔️ | ✔️ |
116116
| [Load-balanced backend pool](backends.md#load-balanced-pool) | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
117-
118-
<sup>1</sup> Synthetic GraphQL subscriptions (preview) aren't supported.
117+
| [Pass-through MCP server](expose-existing-mcp-server.md) (preview) | Basic, Standard, Premium | ✔️ | ❌ | ❌ | ❌ |
119118

120119
### Policies
121120

‎articles/api-management/export-rest-mcp-server.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to expose a REST API in Azure API Management as an MCP se
44
author: dlepow
55
ms.service: azure-api-management
66
ms.topic: how-to
7-
ms.date: 07/25/2025
7+
ms.date: 07/31/2025
88
ms.author: danlep
99
ms.collection: ce-skilling-ai-copilot
1010
ms.custom:
@@ -29,7 +29,7 @@ Learn more about:
2929

3030
## Limitations
3131

32-
The following limitations currently apply to this preview:
32+
The following limitations apply to this preview:
3333

3434
* API Management supports MCP server tools, but doesn't support MCP resources or prompts.
3535
* MCP server capabilities aren't supported in API Management [workspaces](workspaces-overview.md).

‎articles/api-management/expose-existing-mcp-server.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to expose and govern an existing Model Context Protocol (
44
author: dlepow
55
ms.service: azure-api-management
66
ms.topic: how-to
7-
ms.date: 07/25/2025
7+
ms.date: 07/31/2025
88
ms.author: danlep
99
ms.collection: ce-skilling-ai-copilot
1010
ms.custom:
@@ -34,10 +34,10 @@ Learn more about:
3434

3535
## Limitations
3636

37-
The following limitations currently apply to this preview:
37+
The following limitations apply to this preview:
3838

3939
* The external MCP server must conform to MCP version `2025-06-18` or later. The server must support:
40-
* 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)
40+
* 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)
4141
* Streamable HTTP transport
4242

4343
> [!IMPORTANT]

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,5 +7,5 @@ ms.date: 07/16/2025
77
---
88

99
> [!IMPORTANT]
10-
> * This feature is in preview and has some [limitations](#limitations)
10+
> * This feature is in preview and has some [limitations](#limitations).
1111
> * Review the [prerequisites](#prerequisites) to access MCP server features.

‎articles/api-management/mcp-server-overview.md

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ With the proliferation of AI agents and large language models (LLMs), management
2222
* Developers want to reuse existing APIs as agent tools
2323
* Enterprises need observability, control, and scaling
2424

25-
Use API Management to securely expose and govern API operations as tools for LLMs and AI agents like GitHub Copilot, ChatGPT, Claude, and more. API Management provides centralized control over MCP server authentication, authorization, and monitoring. It simplifies the management of MCP servers while helping to mitigate common security risks and ensuring observability, control, and scalability.
25+
Use API Management to securely expose and govern MCP servers and their backends for LLMs and AI agents like GitHub Copilot, ChatGPT, Claude, and more. API Management provides centralized control over MCP server authentication, authorization, and monitoring. It simplifies the management of MCP servers while helping to mitigate common security risks and ensuring observability, control, and scalability.
2626

2727
## MCP concepts and architecture
2828

@@ -65,32 +65,31 @@ MCP provides the following transport types and typical endpoints for remote serv
6565

6666
Azure API Management supports the remote MCP server mode, using native features of API Management and [capabilities of the AI gateway](./genai-gateway-capabilities.md) to manage MCP server endpoints.
6767

68-
> [!NOTE]
69-
> MCP server support in API Management is in preview. In preview, API Management supports MCP server tools, but doesn't currently support MCP resources or prompts.
70-
71-
API Management provides two built-in ways to expose MCP servers:
68+
In preview, API Management provides two built-in ways to expose MCP servers:
7269

7370
| Source | Description |
7471
|-------------------------------------------|-----------------------------------------------------------------------------------------------|
7572
| REST API as MCP server | Expose any REST API managed in API Management as an MCP server, including REST APIs imported from Azure resources. API operations become MCP tools. [Learn more](export-rest-mcp-server.md) |
7673
| Existing MCP server | Expose an MCP-compatible server (for example, LangChain, LangServe, Azure logic app, Azure function app) via API Management. [Learn more](expose-existing-mcp-server.md) |
7774

75+
See the linked articles for step-by-step instructions and preview limitations.
76+
7877

7978
## Govern MCP servers
8079

81-
Configure one or more API Management [policies](api-management-howto-policies.md) to help manage the MCP server. The policies are applied to all API operations exposed as tools in the MCP server and can be used to control access, authentication, and other aspects of the tools.
80+
Configure one or more API Management [policies](api-management-howto-policies.md) to help manage the MCP server. Currently, policies are applied to all API operations exposed as tools in the MCP server and can be used to control access, authentication, and other aspects of the tools.
8281

8382
Configure policies such as the following::
8483

8584
* **Rate limiting and quota enforcement** - Limit the number of requests per time period to the MCP server's tools, and set usage quotas for clients or subscriptions.
86-
* **Authentication and authorization** - Require and validate incoming requests using JSON web tokens (JWT) or Microsoft Entra ID tokens for secure access.
85+
* **Authentication and authorization** - Require and validate incoming requests using JSON web tokens (JWT) issued by Microsoft Entra ID or other idenity providers for secure access.
8786
* **IP filtering** - Restrict access to the MCP server's tools based on client IP addresses.
8887
* **Caching** - Cache responses from the MCP server's tools to improve performance and reduce backend load.
8988

9089

9190
## Secure access to the MCP server
9291

93-
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 backend). For more information and examples, see [Secure access to MCP servers](secure-mcp-servers.md).
92+
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 backend). Apply one or more security measures depending on your backends and your organization's security posture. For more information and examples, see [Secure access to MCP servers](secure-mcp-servers.md).
9493

9594
## Monitoring
9695

@@ -116,14 +115,14 @@ Use [Azure API Center](../api-center/register-discover-mcp-server.md) to registe
116115

117116
## Availability
118117

119-
MCP servers in API Management are available in the following service tiers:
118+
In preview, MCP servers in API Management are available in the following service tiers:
120119

121120
* **Classic tiers**: Basic, Standard, Premium
122121
* **v2 tiers**: Basic v2, Standard v2, Premium v2
123122

124123
> [!NOTE]
125124
> * In the classic tiers, you must join the [AI Gateway Early update group](configure-service-update-settings.md) to access MCP server features.
126-
> * MCP servers aren't currently supported in [workspaces](workspaces-overview.md).
125+
> * MCP servers aren't currently supported in [workspaces](workspaces-overview.md) or the self-hosted gateway.
127126
128127
## Related content
129128

‎includes/api-management-configure-test-mcp-server.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
author: dlepow
33
ms.service: azure-api-management
44
ms.topic: include
5-
ms.date: 07/15/2025
5+
ms.date: 07/31/2025
66
ms.author: danlep
77
---
88
## Configure policies for the MCP server
@@ -16,9 +16,9 @@ Learn more about configuring policies:
1616
* [Set and edit policies](../articles/api-management/set-edit-policies.md)
1717

1818
> [!IMPORTANT]
19-
> Do not access the response body using `context.Response.Body` within MCP server policies. Doing so triggers response buffering, which interferes with the streaming behavior required by MCP servers and may cause them to malfunction.
19+
> Do not access the response body using the `context.Response.Body` variable within MCP server policies. Doing so triggers response buffering, which interferes with the streaming behavior required by MCP servers and may cause them to malfunction.
2020
21-
To configure policies for the MCP server:
21+
To configure policies for the MCP server:
2222

2323
1. In the [Azure portal](https://portal.azure.com), navigate to your API Management instance.
2424
1. In the left-hand menu, under **APIs**, select **MCP Servers**.
@@ -41,7 +41,7 @@ Use a compliant LLM agent (such as GitHub Copilot, Semantic Kernel, or Copilot S
4141

4242
### Add the MCP server in Visual Studio Code
4343

44-
For example, in Visual Studio Code, use GitHub Copilot chat in agent mode (preview) to add the MCP server and use the tools. For background about MCP servers in Visual Studio Code, see [Use MCP Servers in VS Code (Preview)](https://code.visualstudio.com/docs/copilot/chat/mcp-servers).
44+
In Visual Studio Code, use GitHub Copilot chat in agent mode to add the MCP server and use the tools. For background about MCP servers in Visual Studio Code, see [Use MCP Servers in VS Code](https://code.visualstudio.com/docs/copilot/chat/mcp-servers).
4545

4646
To add the MCP server in Visual Studio Code:
4747

@@ -89,7 +89,7 @@ After adding an MCP server in Visual Studio Code, you can use tools in agent mod
8989
| `401 Unauthorized` error from backend | Authorization header not forwarded | Use `set-header` policy to manually attach token |
9090
| API call works in API Management but fails in agent | Incorrect base URL or missing token | Double-check security policies and endpoint |
9191
| Not able to create MCP server | MCP server capability is not available in Consumption or Developer tier, and must be enabled using [update group](../articles/api-management/configure-service-update-settings.md) in classic Basic, Standard, and Premium tiers | Use a supported classic or v2 tier - see [Prerequisites](#prerequisites) |
92-
| MCP server fails when diagnostic logs are enabled | Response body logging or access through policy interferes with MCP transport | Disable response body logging at all APIs scope - see [Prerequisites](#prerequisites) |
92+
| MCP server streaming fails when diagnostic logs are enabled | Logging of response body or access through policy interferes with MCP transport | Disable response body logging at the All APIs scope - see [Prerequisites](#prerequisites) |
9393

9494
## Related content
9595

0 commit comments

Comments
 (0)