Azure API Management Ships Unified Model API and MCP Content Safety at Build 2026 Microsoft announced at Build 2026 a Unified Model API in Azure API Management that lets clients standardize on a single API format while APIM transforms requests to different backend providers, including Anthropic and Google Vertex AI models. The company also extended content safety policies to cover MCP tool calls and Agent-to-Agent communication, enabling organizations to apply familiar API governance principles to emerging agent ecosystems without introducing separate governance platforms. Microsoft announced a major expansion of the AI gateway capabilities https://techcommunity.microsoft.com/blog/integrationsonazureblog/new-ai-gateway-capabilities-in-azure-api-management/4524604 in Azure API Management at Build 2026. The headline additions: a Unified Model API that lets clients speak one API format while APIM transforms requests to different backend providers, AI gateway support extended to Anthropic and Google Vertex AI models, and content safety policies that now cover MCP tool calls and Agent-to-Agent A2A communication alongside LLM traffic. The APIM team writes https://techcommunity.microsoft.com/blog/integrationsonazureblog/whats-new-in-azure-api-management-at-microsoft-build-2026/4524683 : Rather than introducing separate governance platforms for agents, Azure API Management enables organizations to extend familiar API governance principles to emerging agent ecosystems. The Unified Model API https://learn.microsoft.com/en-us/azure/api-management/genai-gateway-capabilities , now in public preview, addresses a growing operational pain point as enterprise teams increasingly mix models from OpenAI, Anthropic, Google, and other providers based on performance, cost, latency, or regional requirements. Moreover, each provider exposes a different API format. Yet the Unified Model API lets clients standardize on a single format, currently OpenAI Chat Completions, while APIM transparently transforms requests to the backend provider's native format, whether that is the Anthropic Messages API or another schema. Finally, teams can swap backend providers, add new models, or route traffic across providers without changing client code. This is not just a convenience layer. Centralizing model access behind a single API surface means that every governance policy, rate limit, content safety check, and token metric applies consistently, regardless of which provider handles inference. Organizations already using APIM for traditional API governance can extend the same patterns to their AI workloads without introducing a parallel governance stack. The content safety extension to MCP and A2A is the most architecturally significant change, where the existing llm-content-safety policy, which scans LLM request and response content against Azure Content Safety, now also covers MCP tool-call arguments, MCP response text, and A2A agent payloads. Furthermore, the policy provides two distinct safety layers: category-based filtering Hate, SelfHarm, Sexual, Violence with configurable severity thresholds from 0 most restrictive to 7 least restrictive , and a separate shield-prompt attribute that specifically checks for adversarial prompt-injection attacks. A typical configuration looks like: