Azure Logic Apps connectors client library for .NET - version 0.13.0-preview.1

The Azure.Connectors.Sdk package provides typed .NET clients for Azure Logic Apps connectors, so you can call Office 365, SharePoint, Teams, Dataverse, and other managed connectors directly from Azure Functions and other .NET apps without running a workflow host. The public API is auto-generated from the managed connector contracts, which gives you strongly typed async methods, request and response models, and IntelliSense for each connector operation.

Caution

This package is an early preview and is under active development. Use it for evaluation and feedback only, not for production. Expect breaking changes across APIs, data models, and behavior in future releases. This package is released outside the Azure SDK engineering system.

Getting started

Install the package

Install the Azure Logic Apps connectors client library for .NET with NuGet:

dotnet add package Azure.Connectors.Sdk --prerelease

Prerequisites

  • You must have an Azure subscription.
  • You must have a Connector Namespace and a connection for the connector you want to call. The connection provides the runtime URL that the typed client targets.

Authenticate the client

The generated clients accept an Azure.Core TokenCredential, so any credential from the Azure Identity library works. Azure-hosted apps default to ManagedIdentityCredential. For local development, pass a credential such as AzureCliCredential explicitly.

Key concepts

  • Connector — A shared REST service hosted by Azure that wraps a specific SaaS or PaaS API, such as Office 365 or SharePoint. Each connector exposes actions and, optionally, triggers.
  • Connector Namespace — The Azure Resource Manager resource that groups your connections and holds the managed identity used for connector access.
  • Connection — An authorized link to a single connector. Each connection exposes a runtime URL that you pass to the typed client.
  • Generated client — A strongly typed class, such as Office365Client, with one async method per connector operation.

Examples

The following example constructs a connector client and calls a single operation. Replace the runtime URL with the connection runtime URL from your Connector Namespace.

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

// Get the connection runtime URL from your Connector Namespace connection.
var connectionRuntimeUrl = new Uri("https://...");

// For local development, pass AzureCliCredential explicitly.
// Azure-hosted apps can omit the credential to use a system-assigned managed identity.
using var client = new Office365Client(connectionRuntimeUrl, new AzureCliCredential());

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

Documentation

Troubleshooting

Next steps

  • Last updated on