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

AZCLI Recipe

Azure CLI workflow for imperative Azure deployments.

When to Use

  • Existing az scripts in project
  • Need imperative control over deployment
  • Custom deployment pipelines
  • AKS deployments
  • Direct resource manipulation

Before Generation

REQUIRED: Research best practices before generating any files.

| Artifact | Research Action | |----------|-----------------| | Bicep files | Call mcp_bicep_get_bicep_best_practices | | Bicep modules | Call mcp_bicep_list_avm_metadata and follow AVM module order | | Azure CLI commands | Call activate_azure_cli_management_tools | | Azure best practices | Call mcp_azure_mcp_get_azure_bestpractices |

Generation Steps

1. Generate Infrastructure (Bicep)

Create Bicep templates in ./infra/.

Structure:

infra/
├── main.bicep
├── main.parameters.json
└── modules/
    └── *.bicep

2. Generate Deployment Scripts

Create deployment scripts for provisioning.

→ scripts.md

3. Generate Dockerfiles (if containerized)

Manual Dockerfile creation required.

Output Checklist

| Artifact | Path | |----------|------| | Main Bicep | ./infra/main.bicep | | Parameters | ./infra/main.parameters.json | | Modules | ./infra/modules/*.bicep | | Deploy script | ./scripts/deploy.sh or deploy.ps1 | | Dockerfiles | src/<service>/Dockerfile |

Deployment Commands

See commands.md for common patterns.

Naming Convention

Resources: {prefix}{token}{instance}

  • Alphanumeric only, no special characters
  • Prefix ≤3 chars (e.g., kv for Key Vault)
  • Token = 5 char random string
  • Total ≤32 characters

References

Next

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