All skills
microsoft avatar

/azure-prepare

@b8a1c66
by microsoftmicrosoft/skills3.1k stars
351

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

Use this Skill: https://skilld.dev/gh/microsoft/skills/azure-prepare

This session only. Nothing lands on disk.

referencesservicesdurable-task-schedulerREADME.md

≈1.2k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Durable Task Scheduler

Build reliable, fault-tolerant workflows using durable execution with Azure Durable Task Scheduler.

When to Use

  • Long-running workflows requiring state persistence
  • Distributed transactions with compensating actions (saga pattern)
  • Multi-step orchestrations with checkpointing
  • Fan-out/fan-in parallel processing
  • Workflows requiring human interaction or external events
  • Stateful entities (aggregators, counters, state machines)
  • Multi-agent AI orchestration
  • Data processing pipelines

Framework Selection

Framework Best For Hosting
Durable Functions Serverless event-driven apps Azure Functions
Durable Task SDKs Any compute (containers, VMs) Azure Container Apps, Azure Kubernetes Service, App Service, VMs

💡 TIP: Use Durable Functions for serverless with built-in triggers. Use Durable Task SDKs for hosting flexibility.

Quick Start - Local Emulator

# Start the emulator (see https://mcr.microsoft.com/v2/dts/dts-emulator/tags/list for available versions)
docker pull mcr.microsoft.com/dts/dts-emulator:latest
docker run -d -p 8080:8080 -p 8082:8082 --name dts-emulator mcr.microsoft.com/dts/dts-emulator:latest

# Dashboard available at http://localhost:8082

Workflow Patterns

Pattern Use When
Function Chaining Sequential steps, each depends on previous
Fan-Out/Fan-In Parallel processing with aggregated results
Async HTTP APIs Long-running operations with HTTP polling
Monitor Periodic polling with configurable timeouts
Human Interaction Workflow pauses for external input/approval
Saga Distributed transactions with compensation
Durable Entities Stateful objects (counters, accounts)

Connection & Authentication

Environment Connection String
Local Development (Emulator) Endpoint=http://localhost:8080;Authentication=None;TaskHub=default
Azure (System-Assigned MI) Endpoint=https://<scheduler>.durabletask.io;Authentication=ManagedIdentity;TaskHub=default
Azure (User-Assigned MI) Endpoint=https://<scheduler>.durabletask.io;Authentication=ManagedIdentity;ClientID=<uami-client-id>;TaskHub=default

⚠️ NOTE: Durable Task Scheduler uses identity-based authentication only — no connection strings with keys. When using a User-Assigned Managed Identity (UAMI), you must include the ClientID in the connection string.

Troubleshooting

Error Cause Fix
403 PermissionDenied on gRPC call (e.g., client.start_new()) Function App managed identity lacks RBAC on the Durable Task Scheduler resource, or IP allowlist blocks traffic 1. Assign Durable Task Data Contributor role (0ad04412-c4d5-4796-b79c-f76d14c8d402) to the identity (SAMI or UAMI) scoped to the Durable Task Scheduler resource. For UAMI, also ensure the connection string includes ClientID=<uami-client-id>. 2. Ensure the scheduler's ipAllowlist includes 0.0.0.0/0 (an empty list denies all traffic). 3. RBAC propagation can take up to 10 minutes — restart the Function App after assigning roles.
Connection refused to emulator Emulator container not running or wrong port Verify container is running: docker ps and confirm port 8080 is mapped
403 despite correct RBAC Scheduler IP allowlist is empty (denies all) Set ipAllowlist: ['0.0.0.0/0'] in Bicep or update via CLI: az durabletask scheduler update --ip-allowlist '0.0.0.0/0'
TaskHub not found Task hub not provisioned or name mismatch Ensure the TaskHub parameter in the DURABLE_TASK_SCHEDULER_CONNECTION_STRING matches the provisioned task hub name
403 Forbidden on DTS dashboard Deploying user lacks RBAC on the scheduler Assign Durable Task Data Contributor role to your own user identity (not just the Function App MI) scoped to the scheduler resource — see Bicep Patterns for the dashboard role assignment snippet

References

Source: SKILL.md on GitHub

2 warnings3d4 checks · Risk SAFE
  • Gen Agent Trust Hub3d

    This skill includes security considerations related to the processing of untrusted project files and the retrieval of external development templates. While these operations are essential for modernizing and preparing Azure applications, they represent a surface area for indirect prompt injection and depend on the integrity of external template repositories.

  • Socket3d

    5 alerts: gptAnomaly, gptSecurity

  • Snyk3d

    Risk: LOW · No issues

  • Runlayer7mo

    86/87 files flagged

Signed by skilld at b8a1c66. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated last week
metadata
{
  "author": "Microsoft",
  "version": "1.3.4"
}

README badge

README badge for microsoft/skills/azure-prepare