All skills
microsoft avatar

/azure-prepare

@7995851 official

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/github-copilot-for-azure/azure-prepare

This session only. Nothing lands on disk.

referencesservicesfunctionstemplatesrecipesdurableREADME.md

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

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

Source: SKILL.md on GitHub

1 alert8d4 checks · Risk SAFE
  • Gen Agent Trust Hub8d

    The azure-prepare skill provides a comprehensive environment for preparing Azure applications for deployment. It focuses on generating infrastructure-as-code and deployment configuration while strictly enforcing security best practices like managed identity usage and secret management via Key Vault. No malicious patterns or security risks were identified.

  • Socket8d

    5 alerts: gptAnomaly, gptSecurity

  • Snyk8d

    Risk: LOW · No issues

  • Runlayer6mo

    68/196 files flagged

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

Last checked against GitHub yesterday.

Activeupdated 3 weeks ago
metadata
{
  "author": "Microsoft",
  "version": "0.0.0-placeholder"
}
  • Infrastructure
  • azure
  • bicep
  • terraform
  • deployment
  • docker
  • functions
  • app-service

README badge

README badge for microsoft/github-copilot-for-azure/azure-prepare

Prepares Azure applications for deployment by generating infrastructure templates (Bicep or Terraform), azure.yaml configuration, and Dockerfiles. Covers new app creation, modernization, and hosting on App Service, Container Apps, or Functions—but excludes Python App Service deployments, copilot SDK apps, and cross-cloud migrations which have dedicated skills.

Generated from the current SKILL.md.

Does this skill handle Python App Service deployments?
No. Use the python-appservice-deploy skill instead for Python code-only App Service deploys.
Can I use this skill for cross-cloud migration?
No. This skill is for Azure-native preparation. Use azure-cloud-migrate for migrations from AWS, GCP, or other clouds.
Does this skill support Copilot SDK apps?
No. Use azure-hosted-copilot-sdk for apps with @github/copilot-sdk or CopilotClient.
What infrastructure templates does this skill support?
Azure Developer CLI (azd), Bicep, Terraform, and Azure CLI. The skill creates infrastructure code, Dockerfiles, and configuration files—actual deployment execution is handled by the azure-deploy skill.
Does this skill delete existing project files?
No. When adding features to existing projects, it modifies files rather than deletes them. It never removes the project or workspace directory itself.

Generated from the current SKILL.md. These answers refresh after source changes.