← Back to the wire22 Nov 2026
The AI WireDispatch No. 092
azure ▸ azure· filed 7 Nov 2026 · 2 min read

Agent 365 and Azure API Management integration enters public preview for MCP governance

Microsoft has made the Agent 365 and Azure API Management integration available in public preview, allowing organizations to manage MCP server and tool governance centrally while enforcing policies through Azure API Management gateways. The integration provides centralized inventory and server-level access control on standard v2 tiers, with additional tool-level blocking, observability, and threat protection on the still-preview AI Gateway tier. It leaves policy-conflict resolution and security-operations data integration as open operational questions.

Machine-drafted illustration · reviewed by a humanFIG. 01

Listen to this dispatch

Narrated by an AI-generated voice.

Microsoft has made the integration between Agent 365 and Azure API Management available in public preview. The pairing is designed to let organizations manage governance for MCP servers and tools in one place—Agent 365—while enforcement happens through Azure API Management gateways in the customer's Azure environment.

The integration covers several distinct functions:

  • Organizations can discover Azure API Management gateways and MCP servers in Agent 365, producing a centralized inventory of gateway-managed tools.
  • Access to MCP servers can be controlled from Agent 365, with Azure API Management applying the resulting policies at runtime.
  • The AI Gateway tier extends this to individual tool-level access controls, allowing administrators to block a single tool without disabling the entire MCP server.
  • Tool activity can be monitored for audit, operational visibility, and incident investigation.
  • Microsoft Defender and Microsoft Purview capabilities can evaluate tool requests and responses for security threats and sensitive-information risks.

The split in feature availability matters. Standard Azure API Management v2 tiers support centralized MCP inventory and server-level blocking and unblocking. The AI Gateway tier, itself still in preview, is where tool-level blocking, tool activity observability, and tool threat protection become available. Organizations that want the finer-grained controls will need to use that tier.

The division of responsibilities is straightforward: AI administrators set governance centrally in Agent 365, and platform teams enforce those policies through Azure API Management in their own Azure environment. This is a workflow split rather than a single product change—one interface for policy decisions, another for runtime enforcement.

The integration is in public preview, and the AI Gateway tier is also in preview, so the most granular capabilities should not be treated as production-grade yet. Organizations evaluating the integration will need to consider whether their existing Azure API Management deployment is on a v2 tier, whether they are willing to adopt the AI Gateway preview for tool-level controls, and how the centralized inventory in Agent 365 stays synchronized with gateways as tools and servers are added or removed.

The integration does not address how policy conflicts are resolved when multiple teams manage the same MCP servers, or how the audit and threat-protection data flows back into existing security operations workflows. It establishes the plumbing for governance, but the practical details of operationalizing it remain open questions.

For now, the concrete takeaway is that Microsoft is positioning Agent 365 as a governance plane for AI-connected tools, with Azure API Management as the enforcement layer. Whether that division holds up in practice—particularly with the tool-level controls still in preview—will depend on how the two systems behave under real workloads.

Read the original at azure.microsoft.com →

End of dispatch
More on the wire
99foundry-techcommunity ▸ tooling · filed 19 Nov 2026Deployment Pattern for Foundry Toolboxes with Independent Lifecycles98foundry-devblog ▸ product · filed 10 Nov 2026Microsoft adds agentic mode to Azure Content Understanding for multi-pass document analysis97agent-framework ▸ product · filed 10 Nov 2026Microsoft ships Agent Framework builder skills for coding agents96foundry-techcommunity ▸ product · filed 9 Nov 2026Microsoft Foundry Documents Production Agent Tuning Pipeline Using Agent Optimizer