Azure Functions
Expert patterns for Azure Functions development including isolated worker model, Durable Functions orchestration, cold start optimization, and production patterns. Covers .NET, Python, and Node.js programming models.
When to Use
- User mentions or implies: azure function
- User mentions or implies: azure functions
- User mentions or implies: durable functions
- User mentions or implies: azure serverless
- User mentions or implies: function app
Core Workflow
- Confirm the request matches this skill's trigger, scope, and risk profile.
- Use the topic map to identify the relevant pattern, checklist, or example before writing detailed guidance or code.
- Load
references/full-guidance.md when implementation details, examples, anti-patterns, validation checks, or edge cases are needed.
- Apply only the relevant guidance instead of loading or repeating the entire reference by default.
- Verify the result against any validation checks, limitations, security notes, or platform constraints in the reference.
Topic Map
- Patterns
- Isolated Worker Model (.NET)
- Template
- Notes
- Node.js v4 Programming Model
- Python v2 Programming Model
- Durable Functions - Function Chaining
- Durable Functions - Fan-Out/Fan-In
- Cold Start Optimization
- Queue Trigger with Error Handling
- HTTP Trigger with Long-Running Pattern
- Sharp Edges
- HTTP Timeout is 230 Seconds Regardless of Plan
- Use async pattern with Durable Functions
- Use queue-based async pattern
- Use webhook callback pattern
- Socket Exhaustion from HttpClient Instantiation
- Use IHttpClientFactory (Recommended)
Reference Map
references/full-guidance.md preserves the complete original guidance, including examples and detailed edge cases.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Progressive Loading
Keep this SKILL.md as the compact routing and workflow entrypoint. Load the reference file only when the user task requires the deeper implementation material.
1---2name: azure-functions3description: Expert patterns for Azure Functions development including isolated4license: MIT5---67# Azure Functions89Expert patterns for Azure Functions development including isolated worker model, Durable Functions orchestration, cold start optimization, and production patterns. Covers .NET, Python, and Node.js programming models.1011## When to Use12- User mentions or implies: azure function13- User mentions or implies: azure functions14- User mentions or implies: durable functions15- User mentions or implies: azure serverless16- User mentions or implies: function app1718## Core Workflow191. Confirm the request matches this skill's trigger, scope, and risk profile.202. Use the topic map to identify the relevant pattern, checklist, or example before writing detailed guidance or code.213. Load `references/full-guidance.md` when implementation details, examples, anti-patterns, validation checks, or edge cases are needed.224. Apply only the relevant guidance instead of loading or repeating the entire reference by default.235. Verify the result against any validation checks, limitations, security notes, or platform constraints in the reference.2425## Topic Map26- Patterns27- Isolated Worker Model (.NET)28- Template29- Notes30- Node.js v4 Programming Model31- Python v2 Programming Model32- Durable Functions - Function Chaining33- Durable Functions - Fan-Out/Fan-In34- Cold Start Optimization35- Queue Trigger with Error Handling36- HTTP Trigger with Long-Running Pattern37- Sharp Edges38- HTTP Timeout is 230 Seconds Regardless of Plan39- Use async pattern with Durable Functions40- Use queue-based async pattern41- Use webhook callback pattern42- Socket Exhaustion from HttpClient Instantiation43- Use IHttpClientFactory (Recommended)4445## Reference Map46- `references/full-guidance.md` preserves the complete original guidance, including examples and detailed edge cases.4748## Limitations49- Use this skill only when the task clearly matches the scope described above.50- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.51- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.5253## Progressive Loading54Keep this `SKILL.md` as the compact routing and workflow entrypoint. Load the reference file only when the user task requires the deeper implementation material.