Run Python Azure Functions when events occur in Teams, Outlook, Salesforce, and other services. Events arrive through a Connector Namespace using managed connectors.
-
Azure CLI (
az) 2.75.0+ -
The
connector-namespaceAzure CLI extension:# Bash curl -fsSL https://aka.ms/connector-namespace-cli-install | sh
# PowerShell irm https://aka.ms/connector-namespace-cli-install-ps | iex
Each sample lists any additional requirements.
Most connectors have standalone polling and webhook apps. Follow the selected app's deployment steps and run azd up from its folder to provision and deploy. Rerun azd up for changes or retries. Templates deploy Python 3.14 on Flex Consumption.
The Generic samples use existing resources instead of azd; follow their setup instructions.
Install Functions Core Tools and Azurite. Follow the selected app's local development steps for dependencies, local settings, and webhook tunnels where needed.
Follow the selected app's test steps to generate source events and confirm function invocations in the logs.
For azd apps, run from the app's folder:
azd down --purgeFollow the app's additional cleanup instructions for source subscriptions or manually created resources.
See Connector trigger payloads for Azure Functions for all supported connector triggers and their Python signatures.
| Package | Minimum | Role |
|---|---|---|
azure-functions |
2.4.0 (Python 3.13+) |
Azure Functions Python SDK |
azurefunctions-extensions-connectors |
1.0.0 |
Connector trigger bindings (not needed by the generic raw-payload samples) |
Install azure-functions>=1.27.0b1 before the sample requirements and set PYTHON_ISOLATE_WORKER_DEPENDENCIES=1 locally and in the deployed app.
| Repo | Purpose |
|---|---|
| Azure/connectors-python-SDK | azure-connectors — Python SDK for Azure Connectors. |
| Azure/azure-functions-python-extensions | azurefunctions-extensions-connectors — the binding extension consumed by these samples. |