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

Terraform Recipe

Terraform workflow for Azure deployments.

⚠️ IMPORTANT: Consider azd+Terraform First

If you're deploying to Azure, you should default to azd with Terraform instead of pure Terraform. azd+Terraform gives you:

  • Terraform's IaC capabilities
  • Simple azd up deployment workflow
  • Built-in environment management
  • Automatic CI/CD pipeline generation
  • Service orchestration from azure.yaml

→ See azd+Terraform documentation ←

When to Use Pure Terraform (Without azd)

Only use pure Terraform workflow when you have specific requirements that prevent using azd:

  • Multi-cloud deployments where Azure is not the primary target
  • Complex Terraform modules/workspaces that are incompatible with azd conventions
  • Existing Terraform CI/CD pipelines that are hard to migrate
  • Organization mandate for pure Terraform workflow without any wrapper tools
  • Explicitly requested by the user to use Terraform without azd

When to Use azd+Terraform Instead

Use azd+Terraform (the default) when:

  • Azure-first deployment (even if you want multi-cloud IaC)
  • Want azd up simplicity with Terraform IaC
  • Multi-service apps needing orchestration
  • Team wants to learn Terraform with a simpler workflow

→ See azd+Terraform documentation

Before Generation

REQUIRED: Research best practices before generating any files.

| Artifact | Research Action | |----------|-----------------| | Terraform patterns | Call mcp_azure_mcp_azureterraformbestpractices | | Azure best practices | Call mcp_azure_mcp_get_azure_bestpractices |

Generation Steps

1. Generate Infrastructure

Create Terraform files in ./infra/.

→ patterns.md

Structure:

infra/
├── main.tf
├── variables.tf
├── outputs.tf
├── terraform.tfvars
├── backend.tf
└── modules/
    └── ...

2. Set Up State Backend

Azure Storage for remote state.

3. Generate Dockerfiles (if containerized)

Manual Dockerfile creation required.

Output Checklist

| Artifact | Path | |----------|------| | Main config | ./infra/main.tf | | Variables | ./infra/variables.tf | | Outputs | ./infra/outputs.tf | | Values | ./infra/terraform.tfvars | | Backend | ./infra/backend.tf | | Modules | ./infra/modules/ | | Dockerfiles | src/<service>/Dockerfile |

References

Next

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