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/recipes/azd/README.md

AZD Recipe

Azure Developer CLI workflow for preparing Azure deployments.

When to Use

  • New projects, multi-service apps, want azd up
  • Need environment management, auto-generated CI/CD
  • Team prefers simplified deployment workflow

💡 Tip: azd supports both Bicep and Terraform as IaC providers. Choose based on your team's expertise and requirements.

IaC Provider Options

| Provider | Use When | |----------|----------| | Bicep (default) | Azure-only, no existing IaC, want simplest setup | | Terraform | Multi-cloud IaC, existing TF expertise, want azd simplicity |

For Terraform with azd: See terraform.md

Before Generation

REQUIRED: Research best practices before generating any files.

Check for Existing Codebase Patterns

⚠️ CRITICAL: For existing codebases with special patterns, use azd init --from-code -e <environment-name> instead of manual generation.

| Pattern | Detection | Action | |---------|-----------|--------| | .NET Aspire | *.AppHost.csproj or Aspire.Hosting package | Use azd init --from-code -e <environment-name> → aspire.md | | Existing azure.yaml | azure.yaml present | MODIFY mode - update existing config | | New project | No azure.yaml, no special patterns | Manual generation (steps below) |

💡 Note: The -e <environment-name> flag is required when running azd init --from-code in non-interactive environments (agents, CI/CD pipelines). Without it, the command will fail with a prompt error.

References for Manual Generation

| Artifact | Reference | |----------|-----------| | azure.yaml | Schema Guide | | .NET Aspire projects | Aspire Guide | | Terraform with azd | Terraform Guide | | AZD IAC rules | IAC Rules | | Azure Functions templates | Templates | | Bicep best practices | mcp_bicep_get_bicep_best_practices | | Bicep resource schema | mcp_bicep_get_az_resource_type_schema | | Azure Verified Modules | mcp_bicep_list_avm_metadata + AVM module order | | Terraform best practices | mcp_azure_mcp_azureterraformbestpractices | | Dockerfiles | Docker Guide |

Generation Steps

For Bicep (default)

| # | Artifact | Reference | |---|----------|-----------| | 1 | azure.yaml | Schema Guide | | 2 | Application code | Entry points, health endpoints, config | | 3 | Dockerfiles | Docker Guide (if containerized) | | 4 | Infrastructure | ./infra/main.bicep + modules per IAC Rules |

For Terraform

| # | Artifact | Reference | |---|----------|-----------| | 1 | azure.yaml with infra.provider: terraform | Terraform Guide | | 2 | Application code | Entry points, health endpoints, config | | 3 | Dockerfiles | Docker Guide (if containerized) | | 4 | Terraform files | ./infra/*.tf per Terraform Guide |

Outputs

For Bicep

| Artifact | Path | |----------|------| | azure.yaml | ./azure.yaml | | App Code | src/<service>/* | | Dockerfiles | src/<service>/Dockerfile (if containerized) | | Infrastructure | ./infra/ (Bicep files) |

For Terraform

| Artifact | Path | |----------|------| | azure.yaml | ./azure.yaml (with infra.provider: terraform) | | App Code | src/<service>/* | | Dockerfiles | src/<service>/Dockerfile (if containerized) | | Infrastructure | ./infra/ (Terraform files) |

References

Next

→ Update .azure/deployment-plan.md → azure-validate