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.

referencesrecipesterraformREADME.md

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

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

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.