A glowing cloud architecture diagram links a serverless code function to data, email, users, and security services.
Managed connectors in Azure Functions have reached general availability. That means the integration is now supported for production work, not just previews and demos. Microsoft's Apps on Azure blog announced it on November 17, 2026. The Azure Updates entry carries the "Launched" label. Microsoft's own scale defines that label as fully released, production-ready and available to all Azure customers.

The feature lets a function react to events in outside services and call those services from code. Microsoft's pitch is that developers can skip most of the OAuth, webhook and retry plumbing that SaaS integrations usually need.

A glowing cloud architecture diagram links a serverless code function to data, email, users, and security services. What actually shipped​

The integration has two parts.

  • Connector triggers start a function when something happens in a connected service. Examples are a new SharePoint file, an Outlook calendar event or a changed Dataverse row.
  • Connector SDKs are typed clients that let function code call operations in connected services.

Microsoft says the managed connector ecosystem covers 1,600+ services, including Microsoft 365, Salesforce, Dataverse, Jira, Slack and Dropbox. Earlier material used different counts. During the preview, the Azure SDK blog cited about 1,700 connectors. The Build 2026 update cited 1,400+ managed connectors. Treat the number as a marketing approximation. What matters is whether your specific service and operation are supported.

Azure Connector Namespace does the heavy lifting. Per Microsoft, it handles connections, authentication and service-specific integration logic. Azure Functions supplies the code-first execution model and scaling. Connector Namespace itself also reached GA on the same day. That is a separate announcement, but the two are meant to be used together.

The headline GA change: polling triggers​

Preview triggers relied on webhook delivery. GA adds polling mode, so developers now choose between two delivery models.

AspectWebhookPolling (new at GA)
DirectionConnector Namespace pushes events to the function appThe function app pulls queued events from Connector Namespace
NetworkNeeds an inbound endpoint on the function appOutbound HTTPS only
AuthenticationValidated with Entra ID or system keysSystem-assigned or user-assigned managed identity
StrengthLow latency, as Microsoft describes itNo public callback endpoint, and scaling follows pending events

Microsoft's Ignite post gives defaultTargetPendingEventThreshold: 16 and maxPollingInterval: "00:00:30" in host.json as example settings. The launch blog also describes a batching model. MaxBatchSize controls how many events a function can retrieve in one batch, TargetPendingEventThreshold influences scaling, and maxPollingInterval caps the gap between polls.

Polling matters most to security-minded teams. If your policy says function apps shouldn't expose public callback URLs, outbound-only polling with a managed identity is easier to defend. The trade-off is that Microsoft's materials don't quantify latency, polling cost or delivery guarantees. Test those against your own workload before you commit.

What the code looks like​

Microsoft's examples show the same shape in each language. A trigger attribute or decorator names a delivery mode, a connection called ConnectorNamespace, and a trigger configuration name read from an app setting.

  • C#: a ConnectorTrigger attribute with DeliveryMode = ConnectorTriggerDeliveryMode.Poll on a SharePoint new-file payload.
  • Python: @app.connector_trigger with delivery_mode=func.DeliveryMode.POLL for a new Outlook calendar event.
  • TypeScript: app.connectorTrigger with DeliveryMode.Poll for a Dataverse row-modified event.

These are programming-model illustrations, not deployment recipes. You still have to create the Connector Namespace, authorize the connection and configure the trigger resources.

Microsoft's sample is an RFP intake flow. A new SharePoint document triggers a function. The function uses the SharePoint Connector SDK to retrieve the document and Azure Content Understanding to extract its contents. It then uses the Teams Connector SDK to post an Adaptive Card to a channel. That is the pattern to copy: managed integration at the edges, your own logic in the middle.

A caveat on typed SDKs​

Microsoft draws a line here that is easy to miss. Generic trigger support doesn't mean SDK action support. Strongly typed trigger payloads and SDK clients exist for popular connectors such as Outlook, SharePoint and Teams. Other connectors in the catalog can deliver events as JSON payloads that you parse yourself. Typed SDK clients for actions exist only for supported connectors and operations.

Languages, hosting and availability​

The launch blog lists C#, Python and TypeScript. The Ignite post describes support as .NET isolated, Python and Node.js. The Microsoft Learn overview, updated on the GA date, adds version detail. It lists:

  • .NET 10 and .NET 11 isolated
  • Python 3.13+
  • Node.js 24+ for JavaScript and TypeScript
  • Java, PowerShell and Go are not supported

Learn names Flex Consumption as the recommended hosting plan. It also lists Premium, Dedicated and Container Apps. Linux-hosted function apps are supported in all regions, and Windows-hosted apps have limited availability. Check this before planning a Windows-hosted deployment.

The Learn page also carries a leftover banner that says Azure Connector Namespace integration for Azure Functions is currently in public preview. That text appears in the search index, while the fetched copy of the page is dated November 17. Some Learn pages and package instructions, such as --prerelease install commands, may lag the GA announcement. Verify package versions against current docs before pinning them in production. The Ignite post cites azure-connectors>=1.0.0 for Python.

Getting started​

Microsoft lists three routes.

  1. Azure Developer CLI. Clone a sample repository for C#, Python or TypeScript and follow its prerequisites. Then run azd up. The samples include Bicep templates that provision the Azure resources, connector connections and trigger configurations.
  2. Visual Studio Code. In the Azure Functions extension, go to Create New Project and open the Connectors tab. Choose a connector and event, then generate the project. When you debug with F5, VS Code walks you through creating or reusing the namespace, connection and trigger resources.
  3. Azure Functions Core Tools. It includes a selection of connector trigger templates. Microsoft points to aka.ms/connectortrigger for the setup steps.

Pricing​

Microsoft says there is no additional charge for the integration itself. Two normal costs still apply.

  • Azure Functions: standard pricing for your hosting plan. Learn also mentions related resources such as Azure Storage and Application Insights.
  • Managed connectors: billed per connector call, with rates that depend on whether the connector is Standard or Enterprise. Connector Namespace has its own consumption-based pricing.

A chatty polling trigger on a busy mailbox could add up, so model call volumes before rollout. That is general advice. Microsoft gives no figures in these materials.

Functions or Logic Apps?​

Microsoft calls this an additive option. Learn says Logic Apps Standard remains the simplest choice for pure orchestration across connectors with little custom code. Functions with connectors suits code-first work such as custom branching, existing libraries, other bindings and AI model calls between trigger and action. If no suitable connector exists, or you need protocol-level control, HTTP triggers with service SDKs remain an option.

Bottom line​

Functions teams that used to hand-roll webhook registration and token refresh can now use a supported path to the Microsoft 365 and SaaS ecosystem. Polling mode removes the need for a public inbound endpoint. Before adopting it, check four things:

  • the connector and operation you need
  • your runtime version
  • your hosting plan and OS
  • the connector-call costs

The launch materials don't establish full regional availability, service-level guarantees or detailed migration paths from the preview. Confirm those against current documentation.

 

References

  1. (Launched) Generally Available: Managed Connectors in Azure Functions Azure Updates 2026-11-17T20:00:32Z
  2. Connect Azure Functions to more services with managed connectors - Azure SDK Blog devblogs.microsoft.com
  3. Managed connectors in Azure Functions are now generally available | Microsoft Community Hub techcommunity.microsoft.com