skilld
All skills
microsoft avatar

/azure-prepare

@7995851 official
by microsoftmicrosoft/github-copilot-for-azure253 stars
206

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.

Ask your Agent

Use this Skill: https://skilld.dev/gh/microsoft/github-copilot-for-azure/azure-prepare

This session only. Nothing lands on disk.

referencesrecipesazdREADME.md

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

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

Source: SKILL.md on GitHub

Third-party checks

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

Provenance

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

Capability

metadata
{
  "author": "Microsoft",
  "version": "0.0.0-placeholder"
}

Topics

  • Infrastructure
  • azure
  • bicep
  • terraform
  • deployment
  • docker
  • functions
  • app-service

README badge

README badge for microsoft/github-copilot-for-azure/azure-prepare

What it does

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.

Frequently asked

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.