Generally availablemicrosoft-foundryMCP & agent interoperabilityIdentity for agentsDay 1

Connector Namespace is generally available

Connector Namespace is generally available: one Azure resource that hosts connections, triggers and MCP server configurations, reusable from Azure Functions, Foundry agents or custom apps across more than 1,400 connectors. New at GA are on-behalf-of authentication for MCP connectors, custom connectors and MCP servers, polling triggers and managed identity end to end.

Recap by Jussi Roine · Updated 17 Nov 2026
status
Generally available
why it matters

On-behalf-of authentication is the security point: each tool call runs as the signed-in user, so an agent sees only what that person can open and audit trails show the real user. That fixes the shared-connection problem, where an agent quietly held more access than the person using it. Observability and private networking are not there yet, which will keep stricter clients out of production for now.

MCP & agent interoperabilityIdentity for agents

Official sources

Community deep dives

0 links · newest first
Written or recorded something about this?It goes to the moderators with this recap attached. No account needed, and you can get the credit.
Add a link to this recap