NB: Connector Namespace is currently in preview
Azure Function Apps are great for building code-first applications. However, creating and maintaining custom integrations can add significant complexity, especially when the same functionality is already available through Azure Logic Apps.
One of Logic Apps’ greatest strengths is its extensive catalogue of pre-built connectors. These connectors simplify common integration scenarios by handling much of the underlying authentication, communication and error-handling logic.
Until now, developers often had to choose between the flexibility of a code-first Function App and the convenience of Logic Apps connectors.
Azure Connector Namespace brings these two approaches together.
What is Azure Connector Namespace?
Azure Connector Namespace is a new Azure service that makes Logic Apps connectors available to code-first Function Apps through a .NET SDK.
For example, imagine you are building a .NET application that needs to connect to SharePoint, Salesforce and Outlook. Traditionally, you may need to create and maintain a separate API client for each service.
With Azure Connector Namespace, you can use pre-built connectors instead. The service manages much of the operational complexity, including:
- Authentication and credentials
- Polling and webhook delivery
- Pagination
- Retry policies
- Throttling
- Error handling
This allows developers to spend less time maintaining integrations and more time building application functionality.
Key concepts
Connector Namespace
The Connector Namespace is the Azure resource that hosts the connector runtime.
It manages credentials, maintains connection states, polls external services, dispatches webhook events and applies resilience policies.
You can create a Connector Namespace as a standard Azure resource through the Azure portal or Azure CLI. Support for ARM templates and Bicep is not currently available.
Connector
A connector is a pre-built integration component for a service such as SharePoint, Salesforce or Outlook.
Each connector abstracts the underlying service’s API, authentication protocol, pagination and retry logic.
Connectors support two types of operations:
- Triggers: Event-based subscriptions, such as “when a new email arrives”
- Actions: Tasks called by your application, such as “send a message” or “read a row
Connection
A connection is an authenticated link to an external account.
Connections can be created once and reused across multiple applications. Depending on the external service, Azure Connector Namespace supports OAuth, API key and Basic authentication.
How it works
The following example shows how to convert Jira issues into Yammer messages without creating custom clients for either service.
1. Create a Connector Namespace
Create a Connector Namespace resource through the Azure portal.
Note: Bicep support is not currently available in this resource.
2. Create a Function App and install the SDK
Create an Azure Function App using your preferred code editor, then add the SDK package:
dotnet add package Azure.Connectors.Sdk --prerelease
3. Use the pre-built SDK clients in your code
The example below demonstrates converting issues in Jira to messages in Yammer without having to write custom clients for those third-party services.
using Azure.Connectors.Sdk.Jira;
using Azure.Connectors.Sdk.Yammer;
using Azure.Connectors.Sdk.Yammer.Models;
using Microsoft.Azure.Functions.Worker;
using System.Text.Json;
namespace AzureConnectorsDemo;
public class AzureConnectorsDemoFunction(
JiraClient jiraClient,
YammerClient yammerClient)
{
private readonly JiraClient _jiraClient = jiraClient;
private readonly YammerClient _yammerClient = yammerClient;
[Function(nameof(AzureConnectorsDemoFunction))]
public async Task Run(
[TimerTrigger("0 */5 * * * *")] TimerInfo myTimer,
CancellationToken cancellationToken)
{
var jiraIssues =
await _jiraClient.ListIssuesAsync(cancellationToken);
foreach (var jiraIssue in jiraIssues.Issues)
{
var jiraFields =
jiraIssue.Fields!.Value.Deserialize<JiraFields>()!;
var name = jiraFields.Name;
var description = jiraFields.Name;
var postOperationRequest = new PostOperationRequest
{
Title = name,
MessageText = description
};
await _yammerClient.PostMessageAsync(
postOperationRequest,
cancellationToken: cancellationToken);
}
}
}
Compared with a traditional custom integration, this implementation requires:
- No custom API clients
- No OAuth refresh logic
- No pagination boilerplate
- No application-level credential management
- No custom retry logic
The Logic Apps connectors and Azure Connector Namespace handle these responsibilities for you.
Current preview limitations
As of August 2026, Azure Connector Namespace remains in preview. Current limitations include:
- No service-level agreement for production workloads
- Limited regional availability
- Standard connectors available first, with enterprise connectors such as SAP, IBM MQ and Oracle planned for later
- Support for API key and OAuth authentication, with Managed Identity planned
- A pricing model that is still being finalised
These limitations should be considered before using the service for production workloads.
In summary
Azure Connector Namespace brings managed Logic Apps connectors into code-first Function Apps.
It can reduce development time, simplify ongoing maintenance and improve integration reliability by removing the need to build common capabilities from scratch.
While the service is still in preview and is not yet feature-complete, it represents an exciting direction for developers who want the flexibility of code with the integration capabilities of Logic Apps.
For further information and a quickstart, visit the official Connector Namespace documentation on Microsoft Learn.
