AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

azure-prepare

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.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-prepare at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 164

references/services/functions/templates/recipes/durable/README.md

Durable Functions Recipe

Orchestration workflows with Durable Task Scheduler as the backend.

Template Selection

Resource filter: durable
Discover templates via MCP or CDN manifest where resource == "durable" and language matches user request.

Key Concept

Uses Durable Task Scheduler (DTS) — a fully managed backend for state persistence. Do NOT use Azure Storage queues/tables.

See Durable Task Scheduler reference for backend configuration details.

Troubleshooting

Orchestration Fails to Start

Cause: Durable Task Scheduler (DTS) backend not provisioned or connection misconfigured.
Solution: Verify the DTS resource exists and the function app has the Durable Task Scheduler Worker role. Do NOT use Azure Storage queues/tables as backend.

UAMI Connection Issues

Cause: Missing or incorrect Durable Task Scheduler connection string.
Solution: DTS uses a connection string format (not the __ suffix pattern). Set these app settings:

  • DURABLE_TASK_SCHEDULER_CONNECTION_STRING: Endpoint=<scheduler-endpoint>;Authentication=ManagedIdentity;ClientID=<client-id>
  • TASKHUB_NAME: name of the task hub

For system-assigned identity, omit ClientID: Endpoint=<scheduler-endpoint>;Authentication=ManagedIdentity

The identity must have the Durable Task Data Contributor role on the scheduler or task hub resource. See DTS identity auth for identity-based config — refer to the "Configure managed identity" section for connection string and role assignment details.

Eval

| Path | Description | |------|-------------| | eval/summary.md | Evaluation summary | | eval/python.md | Python evaluation results |