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.

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 method-safe retries 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.

┌─────────────────────────────────────┐
│       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          │
└─────────────────────────────────────┘

dotnet add package Azure.Connectors.Sdk --prerelease

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.

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

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
var options = new ConnectorClientOptions();
options.Retry.MaxRetries = 3;
options.Retry.Delay = TimeSpan.FromSeconds(1);

using var clientWithOptions = new Office365Client(
    new Uri(connectionRuntimeUrl),
    new AzureCliCredential(),
    options);

// Explicit opt-in: unsafe methods may repeat connector side effects
var unsafeRetryOptions = new ConnectorClientOptions
{
    RetryUnsafeHttpMethods = true,
};
using var clientWithUnsafeRetries = new Office365Client(
    new Uri(connectionRuntimeUrl),
    new AzureCliCredential(),
    unsafeRetryOptions);

// Call typed operations
await client.SendEmailAsync(new SendEmailInput
{
    To = "recipient@example.com",
    Subject = "Hello from SDK",
    Body = "<p>Email body</p>"
});

var categories = await client.GetOutlookCategoryNamesAsync();

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

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

• 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
• Azure/Connectors-NET-Samples - Full working samples (Azure Functions, triggers, etc.)

The connector inventory below records shipped SDK coverage. Use GitHub issues and focused design documents for proposed work and current planning status.

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

The SDK includes 103 generated typed connector clients. Catalog entries alone do not imply that a typed client is included. Rows marked SDK Generated have not been validated end-to-end.

Use VisualStudioTeamServicesClient from Azure.Connectors.Sdk.VisualStudioTeamServices for Azure DevOps (connector API ID visualstudioteamservices), and DataflowsClient from Azure.Connectors.Sdk.Dataflows for Power Query Dataflows (connector API ID dataflows). Models and model factories live in each connector's .Models namespace. Both clients accept a connection runtime URL, an Azure TokenCredential, and ConnectorClientOptions, like the other SDK clients.

These clients have mocked HTTP and serialization tests, not live connection validation. Triggers use Connector Namespace registration rather than ordinary action calls. Azure DevOps provides typed callback classes and a trigger registry; Dataflows callbacks can be read as TriggerCallbackPayload<RefreshModel>, with DataflowsTriggerOperations and DataflowsTriggerParameters for registration. Azure DevOps search fields preserve scalar and structured JSON values, and pull-request callbacks bind boolean truncation flags and string merge strategies. GetWorkItemDetailsAsync uses the production route; the explicitly Preview replacement is not exposed. See Connector triggers and generation provenance.

Use DataflowsSmsClient from Azure.Connectors.Sdk.DataflowsSms for DataFlows SMS (dataflowssms), not DataflowsClient, which is the separate Power Query connector. Use ServiceNowClient from Azure.Connectors.Sdk.ServiceNow for ServiceNow (service-now). Models and model factories live in each connector's .Models namespace. Both clients follow the existing connection runtime URL and TokenCredential constructors.

ServiceNow record fields are supplied through RecordBody.AdditionalProperties. Attachment-list and attachment-metadata responses preserve their full JSON body in AdditionalProperties; RetrieveAttachmentContentAsync returns raw byte[]. UploadAttachmentFileAsync sends raw bytes with application/octet-stream; the multipart attachment-upload operation is not generated. DataFlows SMS trigger registration uses DataflowsSmsTriggerOperations.OnRegisterWebhook. Sending SMS uses the POST action only; the GET send alternative is excluded because automatic retries could duplicate messages and charges. These additions have mocked HTTP and serialization coverage, not live connection validation. See generation provenance.

Connectors should be regenerated periodically to incorporate Swagger updates:

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

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.

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