Azure App Onboard
MicrosoftOfficialCreated by Microsoft
- Skill
- Workflow
- Cloud and DevOps
- MIT
- Low risk
- Has scripts
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
Azure App Onboard is a comprehensive workflow agent designed to take a business idea or an existing codebase and transition it to a running Azure deployment. It automates the entire lifecycle from initial discovery and architecture planning to infrastructure scaffolding and final deployment. The skill is built to be intelligent and tailored, analyzing the specific requirements of your application rather than relying on generic templates. It includes built-in approval gates for both the architecture plan and the final deployment, ensuring you maintain control over costs and resource configuration throughout the process.
What it does
- Analyzes your application code or business idea to determine the optimal Azure service stack.
- Generates custom infrastructure-as-code (IaC) files tailored to your specific application needs.
- Provides detailed cost estimates for the proposed Azure infrastructure before deployment.
- Executes the deployment of resources directly to your Azure subscription.
- Handles the migration of existing applications to Azure with minimal code changes.
- Provides a structured, step-by-step onboarding experience for developers of all experience levels.
When to use it
- When you have an application and want to deploy it to Azure but are unsure which services to use.
- When you need to migrate an existing application to the cloud without a complete rewrite.
- When you require a cost estimate for your infrastructure before committing to a deployment.
- When you need guided, end-to-end assistance for setting up a new Azure project.
- When you want to verify if your current codebase is ready for a cloud deployment.
Advantages
- Eliminates guesswork by auto-detecting the right Azure services for your specific stack.
- Reduces manual effort by automating the scaffolding of infrastructure-as-code.
- Ensures transparency with mandatory approval gates for architecture and deployment.
- Provides cost visibility early in the planning phase.
- Supports a wide range of scenarios from greenfield projects to existing app migrations.
Usage examples
- “I have a Python web app and want to deploy it to Azure. Can you help me get started?”
- The agent will initiate the discovery phase, scan your codebase, propose an architecture, and guide you through the deployment process.
- “I need to move my existing application to Azure, but I'm not sure what services I need. Can you plan this for me?”
- The agent will analyze your app's requirements, suggest the appropriate Azure services, and provide a cost estimate for your approval.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/microsoft/azure-app-onboard/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip azure-app-onboard.zip -d .agents/skills
Documentation by Microsoft
Azure App Onboard
⛔ Every repo goes through the full pipeline (Steps 1–10). No exceptions. Do not skip steps, refuse, or short-circuit based on what you recognize. Follow the Workflow table below sequentially — read each step's references before acting.
Quick Reference
| Property | Value |
|---|---|
| Best for | Developers who know what to build but not which Azure services to use |
| Inputs | Business idea or existing codebase, budget/scale preferences (optional) |
| Outputs | Architecture plan, cost estimate, IaC files, deployed Azure resources |
| Phases | Discover → Architect → Scaffold → Deploy (self-contained, no external skill calls) |
When to Use This Skill
Deploy existing code without knowing which Azure services to use
Check if your existing code is ready to deploy to Azure
Move an existing app to Azure without rewriting or with minimal changes
Get cost estimates before committing to infrastructure
Understand architecture decisions and rejected alternatives
Get answers to Azure architecture or service selection questions (e.g., "What database should I use?")
Get guided Azure onboarding without prior experience
When NOT to Use
| Scenario | Use Instead |
|---|---|
Run azd up or execute an existing deployment | azure-deploy |
| Optimize existing Azure spend | cost-optimization from the optional azure-cost plugin |
| Generate Bicep/Terraform for a known architecture | azure-prepare |
| Validate infrastructure or run preflight checks | azure-validate |
| Troubleshoot a running Azure deployment | azure-diagnostics |
| Deploy to or manage AKS/Kubernetes directly | azure-kubernetes |
| Look up or list existing Azure resources | azure-resource-lookup |
If cost-optimization is unavailable, explain that it is provided by the
optional azure-cost plugin and direct the user to their client's supported
plugin installation flow; do not imply the handoff completed.
Pipeline Rules
⛔ You MUST read
references/pipeline-rules.mdat the start of every AppOnboard session. It contains approval gates, phase lifecycle, session artifacts, deploy-as-is, and security baseline rules.
Workflow
⛔ Deploy recovery: After deploy gate approval OR before any
az deployment/az webapp deploy/az acr build— if you haven't readdeploy/PHASE.md, read.copilot-azure/sessions/{id}/deploy-checklist.mdfirst, thendeploy/PHASE.md. ⛔ NEVER invoke{"skill": "azure-deploy"}— that is a DIFFERENT skill for a DIFFERENT workflow.
⛔ Post-scaffold transition (MANDATORY): Immediately after
scaffold-manifest.jsonis written, YOUR NEXT ACTION MUST be Step 8 (Deploy Approval Gate) — NOT a summary report, NOT a "here are the generated files" message, NOT a completion signal. Confirmcontext.jsonhascompletedPhases: [...,"scaffold"]+currentPhase: "deploy"(update it yourself if the scaffold subagent didn't). Re-read approval-gates.md § Deploy Gate if evicted from context (scaffold reference loading is heavy), then present the exact prompt: "🚀 Ready to deploy? (Yes / Run manually / Edit plan / Cancel)". This gate is the LAST content in your response — wait for the user's reply.
| # | Step | Action | Reference |
|---|---|---|---|
| 1 | Session check + Azure login | Create/resume session, verify Azure CLI auth, resolve subscription + user identity | ⛔ You MUST read session-protocol.md |
| 2 | Scope triage | Check azd markers, triage question. Empty workspace or code-only (no infra) → Step 3 directly. | ⛔ Read intent-gathering.md § Scope Triage |
| 3 | Prereq scan | ⛔ Skip if completedPhases includes "prereq". Otherwise: invoke {"skill": "azure-app-onboard-prereq"}. Write prereq-output.json, update context.json. Halt if: overallHealth: "blocked" OR routeToSkill set. | |
| 4 | Gather intent | Present prereq results, confirm stack + Azure services, ask remaining questions. | ⛔ Read intent-gathering.md § After Prereq Returns |
| 5 | Plan architecture | Write prepare-plan.json. | ⛔ You MUST read prepare/PHASE.md |
| 6 | Scaffold approval gate | Display plan for user approval BEFORE generating any files. | ⛔ Read approval-gates.md § Scaffold Gate |
| 7 | Scaffold | Generate IaC, self-review. Write scaffold-manifest.json. Update context.json. | ⛔ You MUST read scaffold/PHASE.md |
| 8 | Deploy approval gate | Display validation summary. ⛔ After approval: FIRST read deploy-checklist.md → deploy/PHASE.md. NEVER {"skill": "azure-deploy"}. | ⛔ Read approval-gates.md § Deploy Gate |
| 9 | Deploy | Execute IaC, health-check. Write deploy-result.json. | ⛔ You MUST read deploy/PHASE.md |
| 10 | Handoff | Surface deployment identity, cleanup commands, next steps. | ⛔ You MUST read handoff-protocol.md |
Error Handling
| Error | Remediation |
|---|---|
| Phase fails | Halt, report phase + error. User decides: retry, skip, abort. |
| MCP server unavailable | Skip affected checks, add disclaimer to costEstimate.assumptions[] and every approval gate. |
| Missing RBAC | Report required role + az role assignment command. |
Shared references: MCP tools (cross-phase tool parameters) | IaC resources (Azure resource docs for troubleshooting)
Files
- ATTRIBUTION.mdAdded by AutoGineer983 B
- LICENSELicence file added by AutoGineer1.1 KiB
- SKILL.md6.6 KiB
- deploy/PHASE.md7.5 KiB
- deploy/references/approval-gate-template.md2.9 KiB
- deploy/references/blocked-patterns.md5.7 KiB
- deploy/references/code-deployment-appservice.md4.6 KiB
- deploy/references/code-deployment-container-apps.md8.4 KiB
- deploy/references/code-deployment-swa.md5.7 KiB
- deploy/references/database-post-deploy.md4.5 KiB
- deploy/references/deploy-checklist-template.md10.1 KiB
- deploy/references/deploy-safety.md4.5 KiB
- deploy/references/deploy-schemas.tsScript3.5 KiB
- deploy/references/error-classification.md3.6 KiB
- deploy/references/health-check-patterns.md5.5 KiB
- deploy/references/mcp-tools.md5.5 KiB
- deploy/references/portal-links.md3.1 KiB
- deploy/references/preflight-checks.md4.4 KiB
- deploy/references/subagent-preflight.md5.1 KiB
- prepare/PHASE.md6.4 KiB
- prepare/references/deploy-strategy.md6.8 KiB
- prepare/references/mcp-tools.md5.6 KiB
- prepare/references/naming-patterns.md4.6 KiB
- prepare/references/prepare-schemas.tsScript7.0 KiB
- prepare/references/pricing-guide-services.md8.4 KiB
- prepare/references/pricing-guide.md4.0 KiB
- prepare/references/service-mapping.md8.5 KiB
- prepare/references/sku-matrix.md3.2 KiB
- prepare/references/sku-quota-validation.md9.0 KiB
- prepare/references/subagent-pricing.md2.5 KiB
- prepare/references/subagent-quota.md3.5 KiB
- prepare/references/validation-rubric.md2.3 KiB
- references/approval-gates.md8.4 KiB
- references/azd-template-routing.md4.7 KiB
- references/handoff-protocol.md7.8 KiB
- references/iac-resources.md2.6 KiB
- references/intent-gathering.md2.2 KiB
- references/mcp-tool-reference.md3.7 KiB
- references/pipeline-rules-runtime.md3.5 KiB
- references/pipeline-rules.md6.3 KiB
- references/session-protocol.md8.0 KiB
- references/session-schemas.tsScript5.2 KiB
- references/subscription-resolution.md2.1 KiB
- scaffold/PHASE.md14.2 KiB
- scaffold/references/bicep-app-service.md5.4 KiB
- scaffold/references/bicep-container-apps.md9.3 KiB
- scaffold/references/bicep-patterns-data.md4.0 KiB
- scaffold/references/bicep-patterns-security.md7.8 KiB
- scaffold/references/bicep-patterns.md6.8 KiB
- scaffold/references/bicep-swa.md757 B
- scaffold/references/cicd-pipelines.md325 B
- scaffold/references/dockerfile-generation.md4.1 KiB
- scaffold/references/env-var-secrets.md4.1 KiB
- scaffold/references/error-handling.md1.5 KiB
- scaffold/references/iac-generation-rules.md6.6 KiB
- scaffold/references/mcp-tools.md7.0 KiB
- scaffold/references/rbac-roles.md3.8 KiB
- scaffold/references/scaffold-healing-rules.md3.3 KiB
- scaffold/references/scaffold-schemas.tsScript3.5 KiB
- scaffold/references/self-healing.md2.3 KiB
- scaffold/references/self-review-checklist.md9.0 KiB
- scaffold/references/self-review-procedure.md2.3 KiB
- scaffold/references/subagent-iac-gen.md9.5 KiB
- scaffold/references/subagent-review.md3.5 KiB
- scaffold/references/subagent-validate.md7.2 KiB
- scaffold/references/terraform-patterns.md6.9 KiB
- scaffold/references/validation-and-manifest.md5.1 KiB
- scaffold/references/waf-checklist.md2.3 KiB
- scaffold/scripts/scaffold-conformance.ps1Script12.8 KiB
- scaffold/scripts/scaffold-conformance.shScript13.8 KiB
scaffold/references/terraform-patterns.md
Terraform Patterns
Alternative-path patterns for AppOnboard scaffold. Used when .tf files detected or user overrides iacFormat. Per-resource config comes from mcp_azure_mcp_azureterraformbestpractices at runtime — this file covers layout, provider, naming, state, tagging, and wiring.
File Structure
Default (greenfield or user override)
infra/
├── main.tf # Root module — provider, resource group, module calls
├── variables.tf # Input variables (all configurable values)
├── outputs.tf # Exported values (endpoints, resource IDs)
├── backend.tf # State backend config (local default, Azure Storage for prod)
├── terraform.tfvars # Default variable values (from prepare-plan.json)
└── modules/
├── app-service/
│ ├── main.tf
│ ├── variables.tf
│ └── outputs.tf
├── container-app/
├── sql-database/
├── key-vault/
├── log-analytics/
└── ...Non-Azure IaC coexistence (GCP/AWS TF already in repo)
When detectedInfraProvider.terraform is "gcp", "aws", or "multi" (without azurerm), write Azure TF to a separate directory from existing non-Azure TF. Never overwrite or modify existing IaC files.
Output directory rule: If existing TF is NOT at infra/, write to infra/. If existing TF IS at infra/ (or any path containing infra), write to infra-azure/. Same module structure as default layout.
Each Azure service gets its own module. main.tf orchestrates resource group + module calls.
Provider Configuration
terraform {
required_version = ">= 1.5"
required_providers {
azurerm = {
source = "hashicorp/azurerm"
version = "~> 4.0"
}
random = {
source = "hashicorp/random"
version = "~> 3.0"
}
}
}
provider "azurerm" {
features {}
subscription_id = var.subscription_id
resource_provider_registrations = "none"
}⛔ Never pin to exact patch versions (e.g.,
= 4.1.0). Use~> 4.0to allow minor/patch updates.azurermmanages API versions internally — if a resource isn't available inazurerm, useazapi_resourcewith the latest stable ARM API version.
Conditional access (AADSTS530084):
azurermprovider re-requests tokens that violate device-binding policies. Fix: (1) switch to Bicep, or (2) use service principal auth (ARM_CLIENT_ID+ARM_CLIENT_SECRET+ARM_TENANT_ID).
variables.tf
Required variables: environment_name (string, default "dev"), location (string, default "eastus"), subscription_id (string), session_id (string), deployed_by (string). All configurable values MUST be variables — no hardcoded regions, names, or SKUs.
terraform.tfvars
Populate from prepare-plan.json: environment_name, location, subscription_id, session_id. See naming-patterns.md for naming convention.
Backend
Local backend by default: backend "local" { path = "terraform.tfstate" }. Recommend Azure Storage backend in postDeployRecommendations[] for production.
Resource Group
Use rg-${var.project_name}-${var.environment_name}-${random_string.suffix.result} with tags = local.tags. Suffix prevents collisions across AppOnboard sessions.
Naming Convention
resource "random_string" "suffix" {
length = 4
special = false
upper = false
}
locals {
# Pattern: {type}-{appname}-{env}-{suffix}
app_name = "app-${var.environment_name}-${random_string.suffix.result}"
kv_name = "kv-${var.environment_name}-${random_string.suffix.result}"
sql_name = "sql-${var.environment_name}-${random_string.suffix.result}"
# Storage/ACR: alphanumeric only, no hyphens
storage_name = "st${replace(var.environment_name, "-", "")}${random_string.suffix.result}"
acr_name = "cr${replace(var.environment_name, "-", "")}${random_string.suffix.result}"
}Cross-reference naming with prepare/references/naming-patterns.md — Terraform names must match prepare-plan.json.naming.resources[].
Resource Tags — Mandatory
Apply all 5 AppOnboard tags via local.tags — see iac-generation-rules.md § Session Tags for tag names and values.
locals {
tags = {
"app-onboard-skill" = "true"
"app-onboard-session-id" = var.session_id
"created-at" = timestamp()
"environment" = var.environment_name
"deployed-by" = var.deployed_by
}
}⚠️
timestamp()changes on every plan. Addlifecycle { ignore_changes = [tags["created-at"]] }on every resource.
Secrets — random_password, Not random_string
resource "random_password" "db_password" {
length = 32
special = true
lifecycle { ignore_changes = [result] }
}
resource "azurerm_key_vault_secret" "db_password" {
name = "db-password"
value = random_password.db_password.result
key_vault_id = azurerm_key_vault.kv.id
}⛔ NEVER use
random_stringfor secrets — it is not markedsensitivein state. Always userandom_password.
Container Apps — Two-Phase Wiring
Same circular dependency as Bicep — see bicep-container-apps.md. Phase 1: placeholder image, no ACR/KV refs. Phase 2: build + push, assign AcrPull, update via az containerapp update --image outside Terraform.
# Phase 1: Placeholder image
resource "azurerm_container_app" "app" {
template {
container {
name = "app"
image = "mcr.microsoft.com/azuredocs/containerapps-helloworld:latest"
cpu = 0.25
memory = "0.5Gi"
}
}
identity {
type = "SystemAssigned"
}
}outputs.tf
Export: resource_group_name, app_url (https://${hostname}), resource_ids (list of all deployed resource IDs for deploy-result.json).
Security Defaults
Apply same security rules as Bicep — see bicep-patterns-security.md. Terraform-specific syntax:
| Rule | Terraform HCL |
|---|---|
| Managed identity | identity { type = "SystemAssigned" } |
| ⛔ No SQL admin password | azuread_authentication_only = true. Never generate administrator_login_password |
| Key Vault RBAC | enable_rbac_authorization = true on azurerm_key_vault |
| KV secret reference | app_settings = { KEY = "@Microsoft.KeyVault(VaultName=..;SecretName=..)" } |
| HTTPS only | https_only = true, minimum_tls_version = "1.2" |
| Storage | https_traffic_only_enabled = true, allow_nested_items_to_be_public = false, min_tls_version = "TLS1_2" |
| ⛔ Cosmos DB RBAC | azurerm_cosmosdb_sql_role_assignment, NOT azurerm_role_assignment — see rbac-roles.md |
| RBAC assignments | principal_type = "ServicePrincipal" REQUIRED — see rbac-roles.md |
| SCM/FTP auth | scm.allow: true (scaffold), ftp.allow: false (always) — use azapi_resource |
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 an MCP server, Needs Node.js
Security
What our scanner noticed· Low risk
- Instructions that use the network
- 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-app-onboard · 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.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download azure-app-onboard.zip