Microsoft has announced MCP gateway support for Application Gateway for Containers, with public preview scheduled for November 30, 2026. The feature introduces an MCPRoute custom resource for routing Model Context Protocol traffic. Platform teams will be able to expose MCP servers through a governed hostname and path, while applying gateway-level TLS, JWT validation, Web Application Firewall protection, health monitoring, and routing policies. MCPRoute supports direct routing and aggregation of multiple MCP servers behind one endpoint. The feature is intended for non-production use and testing during preview.
Why it matters
A shared gateway endpoint can give teams a consistent way to expose MCP services and manage cross-cutting controls. Aggregation, session affinity, health checks, and centralized security policies may reduce duplicated configuration, though the feature should not be treated as production-ready during preview.
Key points
- Public preview is scheduled for November 30, 2026, for Application Gateway for Containers
- Adds Model Context Protocol routing through the MCPRoute custom resource
- Supports direct routing and aggregation of multiple MCP servers behind a logical endpoint
- Provides gateway-level TLS, JWT validation, Web Application Firewall protection, health monitoring, and routing policy
- Preview features are available for non-production use and testing; production readiness should not be assumed
Based on reporting by Azure Updates.
Join the conversation! Your thoughts help the community grow.