Blog Post

Azure Integration Services Blog
3 MIN READ

Connector Namespace is generally available:

WSilveira's avatar
WSilveira
Icon for Microsoft rankMicrosoft
Nov 17, 2026

You want your code, your functions, and your agents to talk to SaaS systems without writing and running a client for each one. That's the job of Connector Namespace. As of Ignite 2026, it's generally available (GA).

A connector namespace is one Azure resource that hosts connections, triggers, connector operations, and MCP server configurations. You create a connection once, then use it from Azure Functions, Foundry agents, Azure Container Apps sandboxes, or your own app. Same 1,400+ connectors you know from Logic Apps and Power Platform.

This post is the index. The main GA features each get their own deep dive, and I'll link them here as they go live.

What's new

FeatureWhat you getDeep dive
On-behalf-of (OBO) authentication for MCP connectorsSet an MCP connector to Per-user authentication and every tool call runs as the signed-in user, not through a shared connection. The namespace creates one connection per user on first use, for any connector that supports OAuth sign-in. An agent that searches SharePoint for an employee sees only the files that employee can open, and the downstream system's audit trail shows the real user.Read the deep dive
Custom connectors and custom MCP serversBring your own APIs and MCP servers into the namespace, next to the managed catalog. Your internal order API or a partner's MCP server gets the same connection management and identity handling as Salesforce or ServiceNow, and your agents call it the same way.Read the deep dive
Polling triggersSet a trigger configuration's delivery mode to Polling and your code pulls events from the namespace when it has capacity, instead of the namespace pushing them to a callback endpoint. There's no inbound endpoint to open, and access comes from an access policy on the connection, not a key. A function that processes new SQL orders can sit behind private endpoints and work through a burst at its own pace without flooding the fulfilment system behind it. Azure Functions consumes polling triggers today, through the Connector trigger in public preview.Read the deep dive
Bring-your-own server image in Hosted MCP (public preview) Host your custom MCP servers without operational and management burden - just bring the container image, and let the namespace handle deployment, manage underlying compute, server lifecycle, authentication/authorization, scaling, and more. Read the deep dive

GA also includes two platform updates:

  • Managed identity end to end. Use an Azure managed identity as the authentication option for connectors that support it, configured the same way in Bicep and in the portal. For those connectors, your deployment pipeline stands up a namespace and its connections with no client secrets to store, rotate, or leak.
  • New public regions. Create namespaces in more Azure regions: [Add region list]. Run your namespace in the same region as your compute and your data, and meet data residency requirements. We'll keep adding regions after GA based on partner and customer demand.

What's next

GA doesn't cover everything. Here's what's still coming, so you can plan around it:

  • Observability. Diagnostic logs, Azure Monitor usage metrics, and an OpenTelemetry (OTel) export destination with shared correlation IDs for end-to-end tracing.
  • Virtual network (VNet) integration. Inbound Private Link, and outbound VNet integration with customer-controlled DNS and egress. This is what lets connectors reach private and on-premises systems.

Get started

If you built on the preview, try the GA features and tell me what still keeps you out of production. That list shapes what we build after observability and VNet. File issues and requests at GitHub Issues.

Updated Nov 14, 2026
Version 1.0
No CommentsBe the first to comment