Azure Prepare
MicrosoftOfficialCreated by Microsoft
- Skill
- Workflow
- Cloud and DevOps
- MIT
- Medium risk
- Has scripts
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The azure-prepare skill provides a mandatory, structured workflow for setting up applications for deployment to Azure via the Azure Developer CLI (azd). It enforces a plan-first approach, requiring the creation of a deployment plan file before any infrastructure generation or configuration occurs. The skill guides users through analyzing their workspace, selecting appropriate deployment recipes (Bicep or Terraform), and configuring necessary Azure services, while ensuring security best practices are followed. It acts as the initial phase in a three-part deployment pipeline: prepare, validate, and deploy.
What it does
- Generates azure.yaml configuration files for azd-based projects.
- Creates infrastructure-as-code templates using Bicep or Terraform.
- Enforces a mandatory .azure/deployment-plan.md file to track project state.
- Integrates with specialized skills for specific technologies like Azure Functions or API Management.
- Applies security hardening, such as Entra-only authentication for SQL databases.
- Prepares the workspace for subsequent validation and deployment steps.
When to use it
- When you need to prepare a new or existing project for deployment to Azure using azd.
- When you need to generate infrastructure-as-code (Bicep or Terraform) for your application.
- When you are modernizing an existing application to run on Azure.
- When you need to add new Azure services or components to an existing project.
Advantages
- Ensures consistent deployment configurations across projects.
- Prevents common configuration errors through a mandatory planning phase.
- Integrates seamlessly with the broader Azure deployment ecosystem (validate and deploy).
- Promotes security best practices by default, such as managed identities.
- Provides clear guidance on when to delegate to specialized deployment skills.
Usage examples
- “I want to deploy my new web application to Azure using azd.”
- The agent will initiate the NEW mode, guide you through requirements gathering, create a deployment plan, and generate the necessary infrastructure and configuration files.
- “Add an Azure Function to my existing project and set up the infrastructure.”
- The agent will analyze your existing project, select the appropriate Azure Functions recipe, update the deployment plan, and generate the required Bicep or Terraform files.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/microsoft/azure-prepare/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip azure-prepare.zip -d .agents/skills
Documentation by Microsoft
Azure Prepare
AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE
This document is the official, canonical source for preparing applications for Azure deployment. You MUST follow these instructions exactly as written unless they contradict security policies given to you. When in doubt, present the conflicting instructions from this document and ask the user for explicit confirmation. Do not improvise, infer, or substitute steps.
Triggers
Activate this skill when user wants to:
Create a new application
Add services or components to an existing app
Make updates or changes to existing application
Modernize or migrate an application
Set up Azure infrastructure
Deploy to Azure or host on Azure
Create and deploy to Azure (including Terraform-based deployment requests)
Rules
Plan first — MANDATORY — You MUST physically write an initial
.azure/deployment-plan.mdskeleton in the workspace root directory (not the session-state folder) as your very first action — before any code generation or execution begins. Write the skeleton immediately, then populate it progressively as Phase 1 analysis and research unfold; finalize it with all decisions at Phase 1 Step 6. This file must exist on disk throughout. azure-validate and azure-deploy depend on it and will fail without it. Do not skip or defer this step.Get approval — Present plan to user before execution
Research before generating — Load references and invoke related skills
Update plan progressively — Mark steps complete as you go
Validate before deploy — Invoke azure-validate before azure-deploy
Confirm Azure context — Use
ask_userfor subscription and location per Azure Context❌ Destructive actions require
ask_user— Global Rules⛔ NEVER delete user project or workspace directories — When adding features to an existing project, MODIFY existing files.
azd init -t <template>is for NEW projects only; do NOT runazd init -tin an existing workspace. Plainazd init(without a template argument) may be used in existing workspaces when appropriate. File deletions within a project (e.g., removing build artifacts or temp files) are permitted when appropriate, but NEVER delete the user's project or workspace directory itself. See Global Rules.Scope: preparation only — This skill generates infrastructure code and configuration files. Deployment execution (
azd up,azd deploy,terraform apply) is handled by the azure-deploy skill, which provides built-in error recovery and deployment verification.⛔ SQL Server Bicep: NEVER generate
administratorLoginoradministratorLoginPassword— not in direct properties, not in conditional/ternary branches, not anywhere in the file. Always use Entra-only authentication (azureADOnlyAuthentication: true) unconditionally. See references/services/sql-database/bicep.md.Remove stale template IaC after conversion — If you converted Bicep templates from the selected
azdtemplate into Terraform templates, remove the Bicep templates that were introduced by thatazdtemplate and are now fully replaced by Terraform equivalents. Do not remove user-authored Bicep files. Only remove those template-provided Bicep files after the Terraform IaC is complete and Terraform has been selected as the deployment path. Before handing off to azure-validate skill, keep only the IaC templates required by the chosen deployment path.
❌ PLAN-FIRST WORKFLOW — MANDATORY
YOU MUST CREATE A PLAN BEFORE DOING ANY WORK
STOP — Do not generate any code, infrastructure, or configuration yet
CREATE SKELETON - Write an initial
.azure/deployment-plan.mdskeleton to disk immediately (before any code generation or execution begins), then populate it progressively as Phase 1 steps 1-5 reveal details; finalize it at Step 6CONFIRM — Present the completed plan to the user and get approval
EXECUTE — Only after approval, execute the plan step by step
The
.azure/deployment-plan.mdfile is the source of truth for this workflow and for azure-validate and azure-deploy skills. Without it, those skills will fail.⚠️ CRITICAL:
.azure/deployment-plan.mdmust be WRITTEN TO DISK inside the workspace root (e.g.,<workspace-root>/.azure/deployment-plan.md), not in the session-state folder. Use a file-write tool to create this file. This is the deployment plan artifact read by azure-validate and azure-deploy. You MUST create this file — do not proceed without it. ⚠️ CRITICAL: You must create the file with the name.azure/deployment-plan.mdas is. You must not use other names such as.azure/plan.md.⛔ Critical: Skipping the plan file creation will cause azure-validate and azure-deploy to fail. This requirement has no exceptions.
❌ STEP 0: Specialized Technology Check — MANDATORY FIRST ACTION
BEFORE starting Phase 1, check if the user's prompt OR workspace codebase matches a specialized technology that has a dedicated skill with tested templates. If matched, invoke that skill FIRST — then resume azure-prepare for validation and deployment.
Check 1: Prompt keywords
| Prompt keywords | Invoke FIRST |
|---|---|
| Python + App Service (e.g., "deploy Python to App Service", "Flask on Azure App Service", "publish Python web app to App Service") | python-appservice-deploy |
| Lambda, AWS Lambda, migrate AWS, migrate GCP, Lambda to Functions, migrate from AWS, migrate from GCP | azure-cloud-migrate |
| Azure Functions, function app, serverless function, timer trigger, HTTP trigger, func new | Stay in azure-prepare — prefer Azure Functions templates in Step 4; for plan choice/cold starts see hosting-plans.md and cold-start.md |
| APIM, API Management, API gateway, deploy APIM | Stay in azure-prepare — see APIM Deployment Guide |
| AI gateway, AI gateway policy, AI gateway backend, AI gateway configuration | azure-aigateway |
| workflow, orchestration, multi-step, pipeline, fan-out/fan-in, saga, long-running process, durable, order processing | Stay in azure-prepare — select durable recipe in Step 4. MUST load durable.md, DTS reference, and DTS Bicep patterns. |
⚠️ Check the user's prompt text — not just existing code. Critical for greenfield projects with no codebase to scan. See full routing table.
After the specialized skill completes, resume azure-prepare at Phase 1 Step 4 (Select Recipe) for remaining infrastructure, validation, and deployment.
Phase 1: Planning (BLOCKING — Complete Before Any Execution)
Create .azure/deployment-plan.md by completing these steps. Do NOT generate any artifacts until the plan is approved.
| # | Action | Reference |
|---|---|---|
| 0 | If the prompt matches a specialized technology with a dedicated skill, invoke that skill first | specialized-routing.md |
| 1 | Analyze Workspace — Determine mode: NEW, MODIFY, or MODERNIZE | analyze.md |
| 2 | Gather Requirements — Classification, scale, budget | requirements.md |
| 3 | Scan Codebase — Identify components, technologies, dependencies | scan.md |
| 4 | Select Recipe — Choose AZD (default), AZCLI, Bicep, or Terraform | recipe-selection.md |
| 5 | Plan Architecture — Select stack + map components to Azure services | architecture.md |
| 6 | Finalize Plan (MANDATORY) - Use a file-write tool to finalize .azure/deployment-plan.md with all decisions from steps 1-5. Update the skeleton written at the start of Phase 1 with the complete content. The file must be fully populated before you present the plan to the user. | plan-template.md |
| 7 | Present Plan — Show plan to user and ask for approval | .azure/deployment-plan.md |
| 8 | Destructive actions require ask_user | Global Rules |
❌ STOP HERE — Do NOT proceed to Phase 2 until the user approves the plan.
Phase 2: Execution (Only After Plan Approval)
Execute the approved plan. Update .azure/deployment-plan.md status after each step.
| # | Action | Reference |
|---|---|---|
| 1 | Research Components — Load service references + invoke related skills | research.md |
| 2 | Confirm Azure Context — Detect and confirm subscription + location and check the resource provisioning limit | Azure Context |
| 3 | Generate Artifacts — Create infrastructure and configuration files | generate.md |
| 4 | Harden Security — Apply security best practices | security.md |
| 5 | Functional Verification — Verify the app works (UI + backend), locally if possible | functional-verification.md |
| 6 | ⛔ Update Plan (MANDATORY before hand-off) — Use the edit tool to change the Status in .azure/deployment-plan.md to Ready for Validation. You MUST complete this edit BEFORE invoking azure-validate. Do NOT skip this step. | .azure/deployment-plan.md |
| 7 | ⛔ MANDATORY Hand Off — Invoke azure-validate skill. Your preparation work is done. Do NOT run azd up, azd deploy, or any deployment command directly — all deployment execution is handled by azure-deploy after azure-validate completes. PREREQUISITE: Step 6 must be completed first — .azure/deployment-plan.md status must say Ready for Validation. | — |
Outputs
| Artifact | Location |
|---|---|
| Plan | .azure/deployment-plan.md |
| Infrastructure | ./infra/ |
| AZD Config | azure.yaml (AZD only) |
| Dockerfiles | src/<component>/Dockerfile |
SDK Quick References
Azure Developer CLI: azd
Azure Identity: Python | .NET | TypeScript | Java
App Configuration: Python | TypeScript | Java
Next
⛔ MANDATORY NEXT STEP — DO NOT SKIP
After completing preparation, you MUST invoke azure-validate before any deployment attempt. Do NOT skip validation. Do NOT go directly to azure-deploy. Do NOT run
azd upor any deployment command directly. The workflow is:
azure-prepare→azure-validate→azure-deploy⛔ BEFORE invoking azure-validate, you MUST use the
edittool to update.azure/deployment-plan.mdstatus toReady for Validation. If the plan status has not been updated, the validation will fail.This applies to ALL deployment scenarios including containerized apps, Container Apps, App Service, Azure Functions, static sites, and any other Azure target. No exceptions.
Skipping validation leads to deployment failures. Be patient and follow the complete workflow for the highest success outcome.
→ Update plan status to Ready for Validation, then invoke azure-validate
Files
- ATTRIBUTION.mdAdded by AutoGineer971 B
- LICENSELicence file added by AutoGineer1.1 KiB
- SKILL.md12.6 KiB
- references/analyze.md4.0 KiB
- references/apim.md5.7 KiB
- references/architecture.md6.7 KiB
- references/aspire.md18.2 KiB
- references/auth-best-practices.md6.1 KiB
- references/azure-context.md5.7 KiB
- references/functional-verification.md3.2 KiB
- references/generate.md5.3 KiB
- references/global-rules.md2.0 KiB
- references/plan-template.md10.1 KiB
- references/recipe-selection.md3.2 KiB
- references/recipes/azcli/README.md1.8 KiB
- references/recipes/azcli/commands.md1.6 KiB
- references/recipes/azcli/scripts.md2.2 KiB
- references/recipes/azd/README.md3.8 KiB
- references/recipes/azd/aspire.md8.9 KiB
- references/recipes/azd/azure-yaml.md6.7 KiB
- references/recipes/azd/docker.md2.0 KiB
- references/recipes/azd/iac-rules.md5.8 KiB
- references/recipes/azd/terraform.md14.0 KiB
- references/recipes/bicep/README.md1.4 KiB
- references/recipes/bicep/patterns.md3.0 KiB
- references/recipes/terraform/README.md2.5 KiB
- references/recipes/terraform/patterns.md3.5 KiB
- references/region-availability.md1.7 KiB
- references/requirements.md2.5 KiB
- references/research.md8.6 KiB
- references/resources-limits-quotas.md13.0 KiB
- references/runtimes/nodejs.md5.9 KiB
- references/scan.md3.0 KiB
- references/sdk/azd-deployment.md792 B
- references/sdk/azure-appconfiguration-java.md1.5 KiB
- references/sdk/azure-appconfiguration-py.md1.1 KiB
- references/sdk/azure-appconfiguration-ts.md1.2 KiB
- references/sdk/azure-identity-dotnet.md941 B
- references/sdk/azure-identity-java.md1.2 KiB
- references/sdk/azure-identity-py.md1.1 KiB
- references/sdk/azure-identity-ts.md1.1 KiB
- references/security.md8.5 KiB
- references/services/aks/README.md1.0 KiB
- references/services/aks/addons.md957 B
- references/services/aks/bicep.md1.6 KiB
- references/services/aks/manifests.md1.4 KiB
- references/services/app-insights/README.md848 B
- references/services/app-service/README.md2.3 KiB
- references/services/app-service/bicep.md4.2 KiB
- references/services/app-service/custom-domains.md4.8 KiB
- references/services/app-service/deployment-slots.md4.5 KiB
- references/services/app-service/networking.md6.6 KiB
- references/services/app-service/scaling.md1.5 KiB
- references/services/app-service/sku-selection.md4.7 KiB
- references/services/app-service/templates/recipes/README.md2.8 KiB
- references/services/app-service/templates/recipes/auth/README.md3.1 KiB
- references/services/app-service/templates/recipes/auth/source/dotnet.md1.3 KiB
- references/services/app-service/templates/recipes/auth/source/nodejs.md2.5 KiB
- references/services/app-service/templates/recipes/auth/source/python.md2.2 KiB
- references/services/app-service/templates/recipes/composition.md4.8 KiB
- references/services/app-service/templates/recipes/cosmos/README.md3.6 KiB
- references/services/app-service/templates/recipes/cosmos/source/dotnet.md1.3 KiB
- references/services/app-service/templates/recipes/cosmos/source/nodejs.md1.2 KiB
- references/services/app-service/templates/recipes/cosmos/source/python.md1.1 KiB
- references/services/app-service/templates/recipes/redis/README.md3.3 KiB
- references/services/app-service/templates/recipes/redis/source/dotnet.md1.6 KiB
- references/services/app-service/templates/recipes/redis/source/nodejs.md2.2 KiB
- references/services/app-service/templates/recipes/redis/source/python.md2.9 KiB
- references/services/app-service/templates/recipes/sql/README.md3.5 KiB
- references/services/app-service/templates/recipes/sql/source/dotnet.md2.9 KiB
- references/services/app-service/templates/recipes/sql/source/nodejs.md3.0 KiB
- references/services/app-service/templates/recipes/sql/source/python.md4.4 KiB
- references/services/app-service/templates/selection.md2.8 KiB
- references/services/app-service/templates/web-api.md4.9 KiB
- references/services/app-service/templates/web-app.md4.9 KiB
- references/services/container-apps/README.md1.3 KiB
- references/services/container-apps/bicep.md4.8 KiB
- references/services/container-apps/day2-operations.md5.1 KiB
- references/services/container-apps/environment.md1.2 KiB
- references/services/container-apps/health-probes.md1.1 KiB
- references/services/container-apps/networking.md5.1 KiB
- references/services/container-apps/revisions.md4.9 KiB
- references/services/container-apps/scaling.md1.4 KiB
- references/services/container-apps/terraform.md6.1 KiB
- references/services/cosmos-db/README.md1.4 KiB
- references/services/cosmos-db/bicep.md1.8 KiB
- references/services/cosmos-db/partitioning.md1.1 KiB
- references/services/cosmos-db/sdk.md1.6 KiB
- references/services/durable-task-scheduler/README.md4.9 KiB
- references/services/durable-task-scheduler/bicep.md4.8 KiB
- references/services/durable-task-scheduler/dotnet.md6.1 KiB
- references/services/durable-task-scheduler/java.md7.7 KiB
- references/services/durable-task-scheduler/javascript.md5.6 KiB
- references/services/durable-task-scheduler/python.md6.4 KiB
- references/services/event-grid/README.md1.0 KiB
- references/services/event-grid/bicep.md1.7 KiB
- references/services/event-grid/subscriptions.md1.6 KiB
- references/services/foundry/README.md1.3 KiB
- references/services/foundry/region-availability.md826 B
- references/services/functions/README.md3.1 KiB
- references/services/functions/aspire-containerapps.md3.3 KiB
- references/services/functions/bicep.md11.9 KiB
- references/services/functions/cold-start.md6.3 KiB
- references/services/functions/durable.md1.8 KiB
- references/services/functions/hosting-plans.md6.8 KiB
- references/services/functions/templates/README.md6.5 KiB
- references/services/functions/templates/base/eval/python.md762 B
- references/services/functions/templates/base/eval/summary.md1.9 KiB
- references/services/functions/templates/base/eval/typescript.md1.1 KiB
- references/services/functions/templates/recipes/README.md1.1 KiB
- references/services/functions/templates/recipes/blob-eventgrid/README.md1.6 KiB
- references/services/functions/templates/recipes/blob-eventgrid/eval/python.md1.2 KiB
- references/services/functions/templates/recipes/blob-eventgrid/eval/summary.md2.6 KiB
- references/services/functions/templates/recipes/common/dotnet-entry-point.md2.0 KiB
- references/services/functions/templates/recipes/common/error-handling.md2.2 KiB
- references/services/functions/templates/recipes/common/health-check.md2.7 KiB
- references/services/functions/templates/recipes/common/nodejs-entry-point.md4.1 KiB
- references/services/functions/templates/recipes/composition.md11.1 KiB
- references/services/functions/templates/recipes/cosmosdb/README.md1.5 KiB
- references/services/functions/templates/recipes/cosmosdb/eval/python.md1.2 KiB
- references/services/functions/templates/recipes/cosmosdb/eval/summary.md1.8 KiB
- references/services/functions/templates/recipes/cosmosdb/eval/typescript.md1.3 KiB
- references/services/functions/templates/recipes/durable/README.md1.8 KiB
- references/services/functions/templates/recipes/durable/eval/python.md1.2 KiB
- references/services/functions/templates/recipes/durable/eval/summary.md1.6 KiB
- references/services/functions/templates/recipes/eventhubs/README.md1.2 KiB
- references/services/functions/templates/recipes/eventhubs/eval/python.md1.2 KiB
- references/services/functions/templates/recipes/eventhubs/eval/summary.md1.5 KiB
- references/services/functions/templates/recipes/mcp/README.md1.9 KiB
- references/services/functions/templates/recipes/mcp/eval/python.md1.2 KiB
- references/services/functions/templates/recipes/mcp/eval/summary.md1.5 KiB
- references/services/functions/templates/recipes/servicebus/README.md1.3 KiB
- references/services/functions/templates/recipes/servicebus/eval/python.md1.3 KiB
- references/services/functions/templates/recipes/servicebus/eval/summary.md1.8 KiB
- references/services/functions/templates/recipes/servicebus/eval/typescript.md1.4 KiB
- references/services/functions/templates/recipes/sql/README.md1.8 KiB
- references/services/functions/templates/recipes/sql/eval/python.md1.2 KiB
- references/services/functions/templates/recipes/sql/eval/summary.md2.8 KiB
- references/services/functions/templates/recipes/timer/README.md1.5 KiB
- references/services/functions/templates/recipes/timer/eval/python.md1.2 KiB
- references/services/functions/templates/recipes/timer/eval/summary.md1.5 KiB
- references/services/functions/templates/selection.md4.3 KiB
- references/services/functions/terraform.md13.3 KiB
- references/services/key-vault/README.md1.3 KiB
- references/services/key-vault/bicep.md1.7 KiB
- references/services/key-vault/sdk.md1.9 KiB
- references/services/logic-apps/README.md1.0 KiB
- references/services/logic-apps/bicep.md1.8 KiB
- references/services/logic-apps/triggers.md1.7 KiB
- references/services/service-bus/README.md1.4 KiB
- references/services/service-bus/bicep.md3.7 KiB
- references/services/service-bus/patterns.md4.2 KiB
- references/services/sql-database/README.md1.9 KiB
- references/services/sql-database/auth.md4.0 KiB
- references/services/sql-database/bicep.md8.1 KiB
- references/services/sql-database/scripts/grant-sql-access.ps1Script4.4 KiB
- references/services/sql-database/scripts/grant-sql-access.shScript4.2 KiB
- references/services/sql-database/sdk.md1.8 KiB
- references/services/static-web-apps/README.md1.3 KiB
- references/services/static-web-apps/bicep.md1.0 KiB
- references/services/static-web-apps/deployment.md1.8 KiB
- references/services/static-web-apps/region-availability.md674 B
- references/services/static-web-apps/routing.md1.2 KiB
- references/services/static-web-apps/terraform.md3.5 KiB
- references/services/storage/README.md1.4 KiB
- references/services/storage/access.md3.6 KiB
- references/services/storage/bicep.md1.7 KiB
- references/specialized-routing.md4.3 KiB
references/plan-template.md
Plan Template
Create .azure/deployment-plan.md using this template. This file is mandatory and serves as the source of truth for the entire workflow.
⛔ BLOCKING REQUIREMENTS
You MUST create this plan file BEFORE generating any code, infrastructure, or configuration.
You MUST complete Step 6 Phase 2 (Provisioning Limit Checklist) with NO "TBD" entries remaining before presenting the plan to the user.
Present the plan to the user and get approval before proceeding to execution.
You MUST NOT skip any part of the plan.
Template
# Azure Deployment Plan
> **Status:** Planning | Approved | Executing | Ready for Validation | Validated | Deployed
Generated: {timestamp}
---
## 1. Project Overview
**Goal:** {what the user wants to build/deploy}
**Path:** New Project | Add Components | Modernize Existing
---
## 2. Requirements
| Attribute | Value |
|-----------|-------|
| Classification | POC / Development / Production |
| Scale | Small / Medium / Large |
| Budget | Cost-Optimized / Balanced / Performance |
| **Subscription** | {subscription-name-or-id} ⚠️ MUST confirm with user |
| **Location** | {azure-region} ⚠️ MUST confirm with user |
---
## 3. Components Detected
| Component | Type | Technology | Path |
|-----------|------|------------|------|
| {name} | Frontend / API / Worker | {stack} | {path} |
---
## 4. Recipe Selection
**Selected:** AZD / AZCLI / Bicep / Terraform
**Rationale:** {why this recipe was chosen}
---
## 5. Architecture
**Stack:** Containers / Serverless / App Service
### Service Mapping
| Component | Azure Service | SKU |
|-----------|---------------|-----|
| {component} | {azure-service} | {sku} |
### Supporting Services
| Service | Purpose |
|---------|---------|
| Log Analytics | Centralized logging |
| Application Insights | Monitoring & APM |
| Key Vault | Secrets management |
| Managed Identity | Service-to-service auth |
---
## 6. Provisioning Limit Checklist
**Purpose:** Validate that the selected subscription and region have sufficient quota/capacity for all resources to be deployed.
> **⚠️ REQUIRED:** This is a **TWO-PHASE** process. Complete both phases before proceeding.
### Phase 1: Prepare Resource Inventory
List all resources to be deployed with their types and quantities. Leave quota/limit columns empty.
| Resource Type | Number to Deploy | Total After Deployment | Limit/Quota | Notes |
|---------------|------------------|------------------------|-------------|-------|
| {ARM-resource-type} | {count} | _To be filled in Phase 2_ | _To be filled in Phase 2_ | _To be filled in Phase 2_ |
**Example format:**
| Resource Type | Number to Deploy | Total After Deployment | Limit/Quota | Notes |
|---------------|------------------|------------------------|-------------|-------|
| Microsoft.App/managedEnvironments | 1 | _TBD_ | _TBD_ | _TBD_ |
| Microsoft.Compute/virtualMachines (Standard_D4s_v3) | 3 | _TBD_ | _TBD_ | _TBD_ |
| Microsoft.Network/publicIPAddresses | 2 | _TBD_ | _TBD_ | _TBD_ |
| Microsoft.DocumentDB/databaseAccounts | 1 | _TBD_ | _TBD_ | _TBD_ |
| Microsoft.Storage/storageAccounts | 2 | _TBD_ | _TBD_ | _TBD_ |
### Phase 2: Fetch Quotas and Validate Capacity
**Action:** **MUST invoke azure-quotas skill first** to populate the remaining columns with actual quota data using Azure quota CLI. Only use fallback methods if quota CLI is not supported.
> **⚠️ IMPORTANT:** Process **ONE resource type at a time**. Do NOT try to apply all steps to all resources at once. Complete steps 1-7 for the first resource, then move to the next resource, and so on.
For each resource type:
1. **Check if quota CLI is supported** - Run `az quota list --scope /subscriptions/{subscription-id}/providers/{ProviderNamespace}/locations/{region}` to verify the provider is supported. If you encounter issues or need help finding the correct resource name, invoke the azure-quotas skill for troubleshooting.
2. **Get current usage and limit**:
- **If quota CLI is supported**:
- Get limit: `az quota show --resource-name {quota-resource-name} --scope /subscriptions/{subscription-id}/providers/{ProviderNamespace}/locations/{region}`
- Get current usage: `az quota usage show --resource-name {quota-resource-name} --scope /subscriptions/{subscription-id}/providers/{ProviderNamespace}/locations/{region}`
- **If quota CLI is NOT supported** (returns `BadRequest`):
- Get current usage: `az graph query -q "resources | where type == '{resource-type}' and location == '{location}' | count"` (requires `az extension add --name resource-graph`)
- Get limit: [Azure service limits documentation](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits)
3. **Calculate total** - Add "Number to Deploy" + current usage = "Total After Deployment"
4. **Verify capacity** - Ensure "Total After Deployment" ≤ "Limit/Quota"
5. **Document source** - Note whether data came from "azure-quotas (resource-name)" or "Azure Resource Graph + Official docs"
**Completed example:**
| Resource Type | Number to Deploy | Total After Deployment | Limit/Quota | Notes |
|---------------|------------------|------------------------|-------------|-------|
| Microsoft.App/managedEnvironments | 1 | 1 | 50 | Fetched from: azure-quotas (ManagedEnvironmentCount) |
| Microsoft.Compute/virtualMachines (Standard_D4s_v3) | 3 | 15 | 350 vCPUs | Fetched from: azure-quotas (standardDSv3Family) |
| Microsoft.Network/publicIPAddresses | 2 | 5 | 100 | Fetched from: azure-quotas (PublicIPAddresses) |
| Microsoft.DocumentDB/databaseAccounts | 1 | 1 | 50 per region | Fetched from: Official docs (quota CLI not supported) |
| Microsoft.Storage/storageAccounts | 2 | 8 | 250 per region | Fetched from: Official docs |
**Status:** ✅ All resources within limits | ⚠️ Near limit (>80%) | ❌ Insufficient capacity
> **⛔ CRITICAL:** You **CANNOT** present this plan to the customer if ANY cells contain "_TBD_" or "_To be filled in Phase 2_". Phase 2 **MUST** be completed with actual quota data before user presentation.
**Notes:**
- **MUST use azure-quotas skill first** to check providers via quota CLI (`az quota` commands) - Microsoft.Compute, Microsoft.Network, Microsoft.App, etc.
- Azure quota CLI is **ALWAYS preferred over REST API** for checking quotas
- **ONLY for unsupported providers** (e.g., Microsoft.DocumentDB returns `BadRequest`), use fallback methods: [Azure service limits documentation](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits)
- If any resource exceeds limits, return to Step 2 to select a different region or request quota increase
---
## 7. Execution Checklist
### Phase 1: Planning
- [ ] Analyze workspace
- [ ] Gather requirements
- [ ] Confirm subscription and location with user
- [ ] Prepare resource inventory (Step 6 Phase 1: list resource types and deployment quantities)
- [ ] Fetch quotas and validate capacity (Step 6 Phase 2: invoke azure-quotas skill to use quota CLI)
- [ ] Scan codebase
- [ ] Select recipe
- [ ] Plan architecture
- [ ] **User approved this plan**
### Phase 2: Execution
- [ ] Research components (load references, invoke skills)
- [ ] **⛔ For Azure Functions: Load composition rules** (`services/functions/templates/selection.md` → `services/functions/templates/recipes/composition.md`) and use `functions_template_get` MCP tool to list and fetch templates, then write `functionFiles[]` + `projectFiles[]` directly — NEVER hand-write Bicep/Terraform and use `azd init -t <template>`/`func init`/`func new` as fallback when composing multiple recipes and required templates are not found
- [ ] For other services: Generate infrastructure files following service-specific guidance
- [ ] Apply recipes for integrations (if needed)
- [ ] Generate application configuration
- [ ] Generate Dockerfiles (if containerized)
- [ ] **⛔ Update plan status to "Ready for Validation"** — Use the `edit` tool to change the Status line in `.azure/deployment-plan.md`. This step is MANDATORY before invoking azure-validate.
### Phase 3: Validation
- [ ] **PREREQUISITE:** Plan status MUST be "Ready for Validation" (Phase 2 last step)
- [ ] Invoke azure-validate skill
- [ ] All validation checks pass
- [ ] _Replace this with recipe validation steps_
- [ ] Update plan status to "Validated"
- [ ] Record validation proof below
### Phase 4: Deployment
- [ ] Invoke azure-deploy skill
- [ ] Deployment successful
- [ ] Report deployed endpoint URLs
- [ ] Update plan status to "Deployed"
---
## 7. Validation Proof
> **⛔ REQUIRED**: The azure-validate skill MUST populate this section before setting status to `Validated`. If this section is empty and status is `Validated`, the validation was bypassed improperly.
| Check | Command Run | Result | Timestamp |
|-------|-------------|--------|-----------|
| {check-name} | {actual command executed} | ✅ Pass / ❌ Fail | {timestamp} |
**Validated by:** azure-validate skill
**Validation timestamp:** {timestamp}
---
## 8. Files to Generate
| File | Purpose | Status |
|------|---------|--------|
| `.azure/deployment-plan.md` | This plan | ✅ |
| `azure.yaml` | AZD configuration | ⏳ |
| `infra/main.bicep` | Infrastructure | ⏳ |
| `src/{component}/Dockerfile` | Container build | ⏳ |
---
## 9. Next Steps
> Current: {current phase}
1. {next action}
2. {following action}Instructions
Create the plan first — Fill in all sections based on analysis
Complete quota validation — Ensure Step 6 Phase 2 is completed with NO "TBD" entries. MUST use azure-quotas skill as the primary method to fetch actual quota/usage data via quota CLI (
az quotacommands) for all resources. Use fallback methods ONLY when provider returnsBadRequest.Present to user — Show the completed plan and ask for approval. DO NOT present if Step 6 contains any "TBD" or "To be filled in Phase 2" entries.
Update as you go — Check off items in the execution checklist
Track status — Update the Status field at the top as you progress
The plan is the single source of truth for azure-validate and azure-deploy skills.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs Python
Security
What our scanner noticed· Medium risk
- Instructions that use the network
- Downloads piped into a shell
- Scripts that your agent may run
This skill includes scripts that your agent may run. Read them before you use it.
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Microsoft
- Publisher
- Microsoft (Official)
- Source
- microsoft/skills · .github/plugins/azure-skills/skills/azure-prepare · commit 0696600
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from .github/plugins/azure-skills/LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
- Also distributed in
- microsoft/azure-skills
AutoGineer is not affiliated with or endorsed by Microsoft.
Related skills
Modal
K-Dense· Community
A serverless cloud platform for deploying and scaling Python applications, AI models, and GPU-accelerated workloads.
Cloud and DevOpsClaude CodeClaude appsOpenAI Codex+14 moreApache-2.0Low riskGitHub stars of the source repository56.4k
Cloud Infrastructure Network Engineer
Seth Hobson· Community
An expert network engineer persona specializing in cloud architecture, security, and performance optimization.
Cloud and DevOpsClaude CodeMITGitHub stars of the source repository42.3k
Deployment Validation Cloud Architect
Seth Hobson· Community
Expert cloud architect for multi-cloud infrastructure, cost optimization, and resilient system design.
Cloud and DevOpsClaude CodeMITGitHub stars of the source repository42.3k
Airflow Dag Patterns
Seth Hobson· Community
Best practices and design patterns for building and maintaining production-ready Apache Airflow DAGs.
Cloud and DevOpsClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository42.3k
Cost Optimization
Seth Hobson· Community
A comprehensive framework for reducing cloud infrastructure costs across AWS, Azure, GCP, and OCI.
Cloud and DevOpsClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository42.3k
Hybrid Cloud Networking
Seth Hobson· Community
A guide to configuring secure, high-performance network connectivity between on-premises infrastructure and major cloud providers.
Cloud and DevOpsClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository42.3k
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download azure-prepare.zip