.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.
| Sample | Description |
|---|---|
| office365App | Office 365 email trigger secured with Managed Identity + built-in authentication — saves incoming emails to blob storage. |
Each 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.
See the full Operations to Azure Functions Signature Mapping for all supported connector triggers and their .NET, Python, and TypeScript signatures.
- Azure Developer CLI (
azd) - Azure CLI (
az) - .NET 10 SDK
jq(for bash post-deploy scripts on macOS/Linux)
- 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_extensionsystem key with App Service built-in auth (Easy Auth) backed by Entra ID. Includes Bicep for federated credentials andauthsettingsV2.
- 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.).