The MCP 2026-07-28 spec is final: your Azure migration plan
The Model Context Protocol specification version 2026-07-28 shipped on 28 July with a stateless core, Multi Round-Trip Requests, required routing headers, cacheable list results and a hardened authorization model that deprecates Dynamic Client Registration in favour of Client ID Metadata Documents. All four Tier 1 SDKs shipped support on release day, so Azure teams running MCP servers on Container Apps, AKS or behind API Management can start migrating immediately.
MCP goes stateless: Azure MCP server migration checklist
MCP's 2026-07-28 release candidate removes the initialize handshake and the Mcp-Session-Id header, so every request is self-contained and Azure-hosted MCP servers can run behind plain load balancers without sticky sessions or Redis session stores. Tasks and MCP Apps land as formal extensions, six SEPs harden authorization around OAuth 2.0 and OpenID Connect, and Roots, Sampling and Logging enter a 12-month deprecation window.