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.

referencesscan.md

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

Codebase Scan

Analyze workspace to identify components, technologies, and dependencies.

Detection Patterns

Languages & Frameworks

File Indicates
package.json Node.js
requirements.txt, pyproject.toml Python
*.csproj, *.sln .NET
pom.xml, build.gradle Java
go.mod Go

Component Types

Pattern Component Type
React/Vue/Angular in package.json SPA Frontend
Only .html/.css/.js files, no package.json Pure Static Site
Express/Fastify/Koa API Service
Flask/FastAPI/Django API Service
Next.js/Nuxt SSR Web App
Celery/Bull/Agenda Background Worker
azure-functions SDK Azure Function
.AppHost.csproj or Aspire.Hosting package .NET Aspire App

Pure Static Site Detection:

  • No package.json, requirements.txt, or build configuration
  • Contains only HTML, CSS, JavaScript, and asset files
  • No framework dependencies (React, Vue, Angular, etc.)
  • ⚠️ For pure static sites, do NOT add language field to azure.yaml to avoid triggering build steps

Existing Tooling

Found Tooling
azure.yaml AZD configured
infra/*.bicep Bicep IaC
infra/*.tf Terraform IaC
Dockerfile Containerized
.github/workflows/ GitHub Actions CI/CD
azure-pipelines.yml Azure DevOps CI/CD

.NET Aspire Detection

.NET Aspire projects are identified by:

  • A project ending with .AppHost.csproj (e.g., OrleansVoting.AppHost.csproj)
  • Reference to Aspire.Hosting or Aspire.Hosting.AppHost package in .csproj files
  • Multiple .NET projects in a solution, typically including an AppHost orchestrator

When Aspire is detected:

  • Use azd init --from-code -e <environment-name> instead of manual azure.yaml creation
  • The --from-code flag automatically detects the AppHost and generates appropriate configuration
  • The -e flag is required for non-interactive environments (agents, CI/CD)
  • ⚠️ CRITICAL: If the AppHost contains AddAzureFunctionsProject, you MUST add .WithEnvironment("AzureWebJobsSecretStorageType", "Files") to the Functions builder chain BEFORE deployment. Without this, Functions will fail at startup with Secret initialization from Blob storage failed. See aspire.md Step 4b for the complete detection and fix procedure.
  • See aspire.md for detailed Aspire-specific guidance

Output

Document findings:

## Components

| Component | Type | Technology | Path |
|-----------|------|------------|------|
| api | API Service | Node.js/Express | src/api |
| web | SPA | React | src/web |
| worker | Background | Python | src/worker |

## Dependencies

| Component | Depends On | Type |
|-----------|-----------|------|
| api | PostgreSQL | Database |
| web | api | HTTP |
| worker | Service Bus | Queue |

## Existing Infrastructure

| Item | Status |
|------|--------|
| azure.yaml | Not found |
| infra/ | Not found |
| Dockerfiles | Found: src/api/Dockerfile |

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.