Azure Functions Connector Samples (.NET)

.NET samples for the Azure Functions Connector Samples repo, using the Azure Connectors .NET SDK and the Connector trigger extension to receive events from Microsoft 365, SharePoint, Teams, and other connectors.

Samples

Guide	Connector
Office 365	Office 365 Outlook
SharePoint	SharePoint Online
OneDrive	OneDrive for Business
Teams	Microsoft Teams
Dataverse	Microsoft Dataverse (Common Data Service)
Planner	Planner
Salesforce	Salesforce
Azure DevOps	Azure DevOps (VSTS)
Azure Blob	Azure Blob Storage
Generic	Any connector, using raw string payloads

Guides without links are work in progress. Each available sample is a self-contained Azure Functions app with its own azure.yaml, infra/, and source code. Navigate into a sample folder and run azd up to deploy.

More triggers and operations

See the full Operations to Azure Functions Signature Mapping for all supported connector triggers and their .NET, Python, and TypeScript signatures.

Prerequisites

• Azure Developer CLI (azd)

• Azure CLI (az) ≥ 2.75.0

• .NET 10 SDK

• connector-namespace Azure CLI extension — install with:

  # Bash
  curl -fsSL https://aka.ms/connector-namespace-cli-install | sh

  or

  # PowerShell
  irm https://aka.ms/connector-namespace-cli-install-ps | iex

• jq (for bash post-deploy scripts on macOS/Linux)

Related .NET samples

• Email → user lookup → Teams (end-to-end) — Trigger on new email, enrich via Office 365 Users connector, post adaptive card to Teams. Demonstrates multi-client DI and per-connection runtime URLs.
• Built-in authentication with managed identity — Replace the connector_extension system key with App Service built-in auth (Easy Auth) backed by Entra ID. Includes Bicep for federated credentials and authsettingsV2.

Related repos

• Azure Functions Connector Extension — The trigger binding that connects Connector Namespace events to Azure Functions.
• Azure Connectors .NET SDK — Typed clients for calling connector operations (Office 365, Teams, SharePoint, etc.).