Azure.Connectors.Sdk

Azure Connectors .NET SDK

Type-safe .NET clients for Azure connectors — call Office 365, SharePoint, Teams, Dataverse, and 1,000+ connectors directly from Azure Functions and other .NET apps.

Early Preview — Not for Production Use

This SDK is currently in early preview and is under active development. It is intended for evaluation, experimentation, and feedback purposes only.

• Do not use this SDK in production environments.
• Breaking changes should be expected across APIs, data models, and behavior in future releases.
• Features may be added, modified, or removed without prior notice.

We welcome feedback and contributions — please open an issue with questions, suggestions, or bug reports.

Why This SDK?

Azure provides a rich ecosystem of managed connectors that bridge your code to SaaS services, PaaS resources, and on-premises systems. Originally powering Azure Logic Apps and Power Automate, these connectors are now available as standalone, strongly-typed C# clients for any .NET application — no workflow service required.

• Type-safe operations — Generated async methods with full IntelliSense and XML documentation
• Built-in authentication — Managed identity and connection string token providers for API Hub
• Resilient HTTP — Configurable retry policies for transient failures
• 1,000+ connectors — Any Azure managed connector available via API Hub can be generated

Note: This is the .NET SDK. Python, Node.js, and Java SDKs are planned in collaboration with the Azure Functions team.

How It Works

┌─────────────────────────────────────┐
│       Your Azure Function / App     │
│                                     │
│  using Office365Client;             │
│  await client.SendEmailAsync(...);  │
└──────────────┬──────────────────────┘
               │
               ▼
┌─────────────────────────────────────┐
│   Generated Connector Clients       │
│   (Office365Extensions.cs, etc.)    │
│                                     │
│  • Typed async methods per action   │
│  • Input/output models from Swagger │
│  • XML docs from connector metadata │
└──────────────┬──────────────────────┘
               │ depends on
               ▼
┌─────────────────────────────────────┐
│   Azure Connectors .NET SDK         │
│   Azure.Connectors.Sdk              │
│                                     │
│  • Azure.Core TokenCredential auth  │
│  • ConnectorHttpClient + retry      │
│  • ConnectorJsonSerializer          │
└─────────────────────────────────────┘

Installation

From NuGet.org

dotnet add package Azure.Connectors.Sdk --prerelease

Quick Start

1. Generate Connector Code

Use the LogicAppsCompiler CLI to generate typed clients from connector Swagger definitions:

LogicAppsCompiler.exe ./generated unused --directClient --connectors=office365

See GENERATION.md for detailed generation instructions.

2. Add Generated Code to Your Project

Copy the generated *Extensions.cs files to your project.

3. Use the Typed Client

using System;
using Azure.Connectors.Sdk;
using Azure.Connectors.Sdk.Office365;
using Azure.Identity;

// Get connection runtime URL from Azure Portal
var connectionRuntimeUrl = "https://...";

// Create client — defaults to ManagedIdentityCredential (system-assigned)
using var client = new Office365Client(connectionRuntimeUrl);

// For local development, pass AzureCliCredential explicitly
using var localClient = new Office365Client(
    new Uri(connectionRuntimeUrl),
    new AzureCliCredential());

// Or configure retry and diagnostics via ConnectorClientOptions
using var clientWithOptions = new Office365Client(
    new Uri(connectionRuntimeUrl),
    new AzureCliCredential(),
    new ConnectorClientOptions());

// Call typed operations
await client.SendEmailAsync(new SendEmailInput
{
    To = "[email protected]",
    Subject = "Hello from SDK",
    Body = "<p>Email body</p>"
});

var categories = await client.GetOutlookCategoryNamesAsync();

SDK Components

Client Base

Authentication

Authentication uses Azure.Core TokenCredential directly — any credential from Azure.Identity works:

HTTP

Serialization

Triggers

See docs/triggers.md for the trigger architecture, payload shapes, and end-to-end usage.

Documentation

• docs/concepts.md - Key concepts, terminology, and architecture
• docs/generated-contract.md - Language-neutral rules for generated actions, model and JSON property names, triggers, discovery helpers, and Swagger wire contracts
• GENERATION.md - How to generate connector code
• docs/connection-setup.md - Setting up connections for local testing
• docs/triggers.md - Trigger architecture, typed payloads, and the ConnectorTriggerPayload reader
• ROADMAP.md - Connector generation progress and lessons learned
• Azure/Connectors-NET-Samples - Full working samples (Azure Functions, triggers, etc.)

AI Agent Skills

• Connection Setup Skill - AI agent workflow for creating Connector Namespace connections, OAuth consent, access policies, and configuring app settings — all from within VS Code

Validated Connectors

Related Projects

Regenerating Connectors

Connectors should be regenerated periodically to incorporate Swagger updates:

LogicAppsCompiler.exe ./generated unused --directClient --connectors=office365,servicebus,teams

Releasing a New Version

The version is defined in eng/build/Version.props (VersionPrefix + VersionSuffix). Three ADO pipelines in azfunc/internal handle mirroring, building/signing, and publishing to nuget.org.

See the Releasing a New Version section in the copilot instructions for the full step-by-step procedure, pipeline IDs, version suffix behavior, and common pitfalls.

License

This project is licensed under the MIT License — see the LICENSE file for details.