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/recipe-selection.md

Recipe Selection

Choose the deployment recipe based on project needs and existing tooling.

⛔ Special Cases: Detect First

Before selecting a recipe, check for these special project types:

| Project Type | Detection | Recipe Selection | |--------------|-----------|------------------| | .NET Aspire | *.AppHost.csproj or Aspire.Hosting package | AZD (auto via azd init --from-code) → aspire.md |

💡 Tip: .NET Aspire projects always use AZD recipe with auto-generated configuration. Do not manually select recipe or create artifacts.

Quick Decision

Default: AZD unless specific requirements indicate otherwise.

💡 Tip: azd supports both Bicep and Terraform as IaC providers. When Terraform is mentioned for Azure deployment, default to azd+Terraform for the best developer experience.

Decision Criteria

| Choose | When | |--------|------| | AZD (Bicep) | New projects, multi-service apps, want simplest deployment (azd up) | | AZD (Terraform) | DEFAULT for Terraform - Want Terraform IaC + azd simplicity, Azure deployment with Terraform | | AZCLI | Existing az scripts, need imperative control, custom pipelines, AKS | | Bicep | IaC-first approach, no CLI wrapper needed, direct ARM deployment | | Terraform | Multi-cloud deployments (non-Azure-first), complex TF workflows incompatible with azd, explicitly requested |

Auto-Detection

| Found in Workspace | Suggested Recipe | |--------------------|------------------| | azure.yaml with infra.provider: terraform | AZD (Terraform) | | azure.yaml (Bicep or no provider specified) | AZD (Bicep) | | *.tf files (no azure.yaml) | AZD (Terraform) - DEFAULT (unless multi-cloud) | | infra/*.bicep (no azure.yaml) | Bicep or AZCLI | | Existing az scripts | AZCLI | | None | AZD (Bicep) - default |

Recipe Comparison

| Feature | AZD (Bicep) | AZD (Terraform) | AZCLI | Bicep | Terraform | |---------|-------------|-----------------|-------|-------|-----------| | Config file | azure.yaml | azure.yaml + *.tf | scripts | *.bicep | *.tf | | IaC language | Bicep | Terraform | N/A | Bicep | Terraform | | Deploy command | azd up | azd up | az commands | az deployment | terraform apply | | Dockerfile gen | Auto | Auto | Manual | Manual | Manual | | Environment mgmt | Built-in | Built-in | Manual | Manual | Workspaces | | CI/CD gen | Built-in | Built-in | Manual | Manual | Manual | | Multi-cloud | No | Yes | No | No | Yes | | Learning curve | Low | Low-Medium | Medium | Medium | Medium |

Record Selection

Document in .azure/deployment-plan.md:

## Recipe: AZD (Terraform)

**Rationale:**
- Team has Terraform expertise
- Want multi-cloud IaC flexibility
- But prefer azd's simple deployment workflow
- Multi-service app (API + Web)

Or for pure Terraform:

## Recipe: Terraform

**Rationale:**
- Multi-cloud deployment (AWS + Azure)
- Complex Terraform modules incompatible with azd conventions
- Existing Terraform CI/CD pipeline

Recipe References