Python Recipes¶
The Recipes section provides implementation-focused patterns for common Azure Functions integrations in Python.
Use these documents when you already understand the platform basics and need practical, reusable building blocks.
graph TD
A[Python Recipes] --> B[HTTP]
A --> C[Storage]
A --> D[Security]
A --> E[Advanced] Pair recipes with platform guidance
For architecture and plan behavior that applies across all languages, see Platform.
Recipe categories¶
HTTP¶
| Recipe | Description |
|---|---|
| HTTP API Patterns | Route design, request/response patterns, and API-friendly function composition. |
| HTTP Authentication | Function auth levels, app-level auth, and token validation integration patterns. |
Storage¶
| Recipe | Description |
|---|---|
| Cosmos DB | Input/output patterns for Cosmos DB-backed APIs and event processing workloads. |
| Blob Storage | Blob trigger and blob binding patterns, including production-oriented processing flow. |
| Queue Storage | Queue trigger consumer patterns, retries, and output binding usage. |
Security¶
| Recipe | Description |
|---|---|
| Key Vault | Secret and configuration retrieval patterns using Key Vault integration. |
| Managed Identity | Passwordless authentication from Functions to Azure services via Entra identities. |
| Custom Domains & Certificates | TLS and custom hostname setup considerations for HTTP-facing workloads. |
Advanced¶
| Recipe | Description |
|---|---|
| Timer Trigger | Scheduled jobs, cron semantics, and idempotent batch execution patterns. |
| Durable Functions | Orchestration, fan-out/fan-in, and stateful workflow coordination. |
| Event Grid | Event-driven designs and event routing patterns for reactive systems. |
How to consume recipes effectively¶
- Start from your trigger pattern (HTTP, timer, queue, blob, Event Grid).
- Apply security baseline patterns first (Managed Identity and Key Vault).
- Validate hosting-plan constraints in Platform: Hosting.
- Add monitoring/alerts using Operations guidance.