domains / families / devops / azure-functions

azure-functions

combined

Build serverless applications on Azure Functions. Configure triggers, bindings, and deployment. Use when implementing serverless workloads on Azure. Expert patterns for Azure Functions development including isolated

When to use

• You need event-driven compute that scales automatically to zero.
• You are building APIs, webhooks, or background processing pipelines.
• You want per-execution billing without managing servers.
• You need to respond to Azure service events (Blob Storage, Service Bus, Cosmos DB changes).
• You are implementing lightweight microservices or scheduled tasks.
• User mentions or implies: azure function
• User mentions or implies: azure functions
• User mentions or implies: durable functions

When not to use

• 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.

Skill page

Conflict

The two copies cover different aspects of Azure Functions. The first copy (BagelHole) is a practical, step-by-step guide for creating function apps, configuring triggers/bindings, and deploying using Azure CLI, with specific code examples in Python and Node.js. The second copy (sickn33) is a high-level wrapper that points to an external 'detailed guide' and focuses on expert patterns like Durable Functions, cold start optimization, and the isolated worker model, which are not covered in the first copy. Neither is a reproduction of the other; they are complementary. Combining them provides a complete skill covering both deployment mechanics and advanced architectural patterns.