Azure App Onboard

MicrosoftOfficialCreated by Microsoft

Skill
Workflow
Cloud and DevOps
MIT
Low risk
Has scripts

From the author

End-to-end orchestrator: from a business idea, app idea, or existing app to running Azure deployment with cost estimates and pre-deploy approval. Analyzes your app, auto-detects the right Azure services, scaffolds infrastructure code, and deploys — tailored to your app, not a template. Handles moving existing apps to Azure without rewriting or with minimal changes. WHEN: bring your app to Azure, plan my app, cost to run, is my code ready to deploy, deploy my app to the cloud, deploy all my services, what Azure services do I need, plan my Azure deployment, deploy my new app to Azure, one-click deploy, I have an app and want it on Azure, migrate my app to Azure, help me get started, build an app, no code yet, starter project. DO NOT USE FOR: use azd for deployment(use azure-deploy), optimizing existing costs (use cost-optimization), code readiness checks only (use azure-app-onboard-prereq).

— the description by Microsoft

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/download

Unzip 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.md at 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 read deploy/PHASE.md, read .copilot-azure/sessions/{id}/deploy-checklist.md first, then deploy/PHASE.md. ⛔ NEVER invoke {"skill": "azure-deploy"} — that is a DIFFERENT skill for a DIFFERENT workflow.

⛔ Post-scaffold transition (MANDATORY): Immediately after scaffold-manifest.json is 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. Confirm context.json has completedPhases: [...,"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/self-review-checklist.md

Self-Review Checklist

4-layer adversarial review of generated IaC. Run after scaffold generates all files, before scaffold-manifest.json.

Rating System

VERIFIED — confirmed correct by inspecting the generated code
PLAUSIBLE — likely correct but cannot fully verify (e.g., API version exists but not checked against registry)
FLAGGED — incorrect, missing, or contradicts the plan/patterns

Consume results: If any finding is FLAGGED → fix the IaC, then re-run validation. If all VERIFIED/PLAUSIBLE → proceed. Write findings to scaffold-manifest.json.selfReview.

⛔ Halt on critical failures — if any finding is FLAGGED at L1 (Security) or L3 (Hallucination), do NOT proceed to deploy. Present findings and ask: "Fix / Continue with risks / Cancel".

⛔ Step 12 validation remains mandatory regardless of self-review results — IaC may change during FLAGGED fixes.

Layer 1 — Security Claims Extraction

Extract every security claim from the generated IaC and check for internal contradictions.

Check	Example
Managed identity declared but secret hardcoded	`identity: { type: 'SystemAssigned' }` but `password: 'hardcoded'` in same file
HTTPS enforced but HTTP endpoint exposed	`httpsOnly: true` but ingress allows HTTP
Resource accessed via managed identity but matching role not granted	KV secret read without KV Secrets User, ACR image pull without AcrPull, or any MI→resource dependency missing its `roleAssignment` — access fails at runtime → `FLAGGED`
⛔ Role assignment scope targets wrong resource	`scope: resourceGroup()` on resource-specific roles → `FLAGGED`. Must scope to specific resource.
`principalType` missing on role assignments	Causes intermittent 30s+ delays
⛔ Identity block missing on compute resource	⛔ MANDATORY FAIL — ALL compute MUST have `identity: { type: 'SystemAssigned' }`. ⛔ HARD EXCEPTION — F1/D1 Linux: MI sidecar causes OOM on free tier → rate `PLAUSIBLE`, NEVER `FLAGGED`. The gen template intentionally omits MI for F1/D1. If F1/D1 detected in plan, this check MUST be `PLAUSIBLE`.
SQL firewall `0.0.0.0/0` without private endpoint	Prefer MI + private endpoint. AllowAzureServices genuinely needed → `PLAUSIBLE`.
⛔ SCM/FTP auth policy missing on App Service	ALL App Service MUST have `basicPublishingCredentialsPolicies`: `scm.allow: true`, `ftp.allow: false`. Missing → `FLAGGED`.
⛔ KV URL uses `environment().suffixes.keyvaultDns`	Leading dot → double-dot URL → `ContainerAppSecretKeyVaultUrlInvalid`. Use `keyVault.name` + `.vault.azure.net` or `vaultUri` output. → ⛔ FLAGGED

Rating: Claims that contradict each other → FLAGGED. Consistent claims → VERIFIED.

Layer 2 — Pattern Validation

Validate against pattern files loaded at Steps 3–5 and rbac-roles.md.

Bicep

Check	Source
File structure: `main.bicep` → `modules/*.bicep`	`bicep-patterns.md`
`main.parameters.json` uses ARM JSON (not `.bicepparam`)	`bicep-patterns.md`
Naming: `{prefix}{name}{token}` ≤32 chars	`bicep-patterns.md`
System-assigned managed identity on all services	`bicep-patterns-security.md`
No `administratorLogin` in generated Bicep	`bicep-patterns-security.md`
KV uses RBAC authorization (not access policies)	`bicep-patterns-security.md`
⛔ `enablePurgeProtection` exists in KV module	Remove — `false` rejected by ARM, `true` blocks KV deletion → ⛔ FLAGGED
⛔ KV deployer role assignment — `Key Vault Secrets Officer` for `deployerObjectId` scoped to KV resource	`bicep-patterns-security.md` § Key Vault Deployer RBAC. Without this, `az keyvault secret set` fails with 403.
Prereq `warnings[]` each have a corresponding IaC fix	Read `env-var-secrets.md` for SSL/TLS fixes
Container Apps: two-phase ACR wiring, `registries` populated when ACR in plan, port alignment	`bicep-container-apps.md`
⛔ BuildKit Dockerfile without `Dockerfile.azure`	`hasBuildKitSyntax == true` but no `Dockerfile.azure` in `files[]` → ⛔ MANDATORY FAIL. ACR does not support BuildKit.
⛔ Role assignment `scope` targets specific resource, not `resourceGroup()`	`rbac-roles.md`
⛔ No `azure.yaml` in `scaffold-manifest.json.files[]`	`pipeline-rules.md`
Non-Azure TF in separate dir	`terraform-patterns.md`

Cross-Module Reference Validation

Trace references BETWEEN modules — per-file checks miss broken cross-module wiring.

Check	Rating
Param wiring — every `module` call in `main.bicep`: verify every param without `= default` is passed	Missing param → `FLAGGED`
Secret ref completeness — every CA `secrets[].keyVaultUrl` has a matching KV secret resource	Missing KV secret → `FLAGGED`
Output ref validity — every `moduleRef.outputs.X` is declared in the referenced module	Missing output → `FLAGGED`

Terraform

Check	Source
File structure: `main.tf`, `variables.tf`, `outputs.tf`, `backend.tf`, `modules/`	`mcp_azure_mcp_azureterraformbestpractices`
Provider: `azurerm ~> 4.0`	Terraform registry
System-assigned managed identity, no `administrator_login`, KV RBAC	`terraform-patterns.md`
Container Apps: two-phase ACR wiring	Same pattern as Bicep

Rating: Matches → VERIFIED. Reasonable deviation → PLAUSIBLE. Violates → FLAGGED.

Layer 3 — Hallucination Detection

Catch fabricated resource types, API versions, SKU names, or properties.

Bicep (default path)

Check	How
API versions, resource types, property names valid	`bicep build` — errors = `FLAGGED`
⛔ Deploy-time value validity (`bicep build` blind spot)	The compiler accepts any schema-valid string, but ARM rejects wrong enum-like values (engine versions, region-restricted SKUs), wrong resource `scope`, and empty resource-ID properties. Any such value the generator chose from memory — not traceable to `prepare-plan.json` or a pattern file — MUST be confirmed against the provider capabilities API; unconfirmed → `FLAGGED`.
SKU names match `prepare-plan.json`	Cross-reference `services[].sku`
OpenAI deployment uses `scaleSettings` instead of `sku`	`scaleSettings` deprecated → `FLAGGED`
Any resource uses `-preview` API version	Use latest GA from MCP tool → `FLAGGED`
VNet subnets as separate child resources	Must be inline in `properties.subnets[]` → `FLAGGED`

Run bicep build main.bicep --stdout > /dev/null as syntax + schema validation. Parse errors = FLAGGED.

⛔ az bicep build is MANDATORY for L3. If unavailable, write FLAGGED with "bicep build unavailable."

⛔ Verify main.bicep has targetScope = 'subscription'. Missing → FLAGGED (FIXABLE — add targetScope, RG resource with tags, scope: rg on modules).

mcp_bicep_build_bicep + az deployment sub what-if also appropriate at L3. ⛔ Do NOT use az deployment sub validate (known bug).

Rating: Passes bicep build → VERIFIED. Build warning → PLAUSIBLE. Build error → FLAGGED.

Terraform (alternative path)

Run terraform init -backend=false && terraform validate + terraform plan -detailed-exitcode. Same rating criteria as Bicep.

Rating: Passes validate + plan → VERIFIED. Plan warning → PLAUSIBLE. Validate/plan error → FLAGGED.

Layer 4 — WAF Alignment

Per-pillar spot check against Azure Well-Architected Framework.

Pillar	Check
Reliability	Health probes configured. ⛔ Verify probe path matches `prereq-output.json.healthEndpoint` — non-existent or mismatched path = `FLAGGED`. ⛔ ACA probes do NOT follow HTTP redirects — if app has trailing-slash normalization (Express `redirect`), use path WITHOUT trailing `/` (e.g., `/app` not `/app/`).
Security	No public blob access, TLS 1.2+, managed identity
Cost	SKU matches budget tier from `prepare-plan.json`
Ops	App Insights present + connected for APM, 5 AppOnboard tags on resources, all values parameterized. Present = `VERIFIED`. App Insights absent = `PLAUSIBLE`. ⛔ `diagnostic-settings` is not part of the plan — if the generator added one it MUST be gated (`if (enableDiagnostics)`, default `false`) or absent; wired UNCONDITIONALLY in `main.bicep` = `FLAGGED` (blocks first deploy).
Performance	Autoscale rules present for production SKUs
Reliability	⛔ Env var values compatible with app config validation (Pydantic `Settings`, Django `settings.py`). Typed fields reject wrong formats → `FLAGGED`

Rating: Pillar addressed → VERIFIED. Not applicable for SKU → PLAUSIBLE. Missing for production SKU → FLAGGED.

Output

Write findings to scaffold-manifest.json.selfReview.findings[]: { "layer": "L1", "claim": "...", "rating": "FLAGGED", "detail": "..." } (layer is one of "L1"|"L2"|"L3"|"L4"). All FLAGGED must be resolved or surfaced at deploy gate. PLAUSIBLE = informational.

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

2026-11-08

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

From the author

AutoGineer summary

What it does

When to use it

Advantages

Usage examples

Install

Documentation by Microsoft

Azure App Onboard

Quick Reference

When to Use This Skill

When NOT to Use

Pipeline Rules

Workflow

Error Handling

Files

scaffold/references/self-review-checklist.md

Self-Review Checklist

Rating System

Layer 1 — Security Claims Extraction

Layer 2 — Pattern Validation

Bicep

Cross-Module Reference Validation

Terraform

Layer 3 — Hallucination Detection

Bicep (default path)

Terraform (alternative path)

Layer 4 — WAF Alignment

Output

Requirements and compatibility

Security

Attribution and licence

Related skills

Shipping And Launch

Quantized Export

Deployment Pipeline Design

Gitops Workflow

Spark Environment Setup

Cloud Infrastructure Deployment Engineer

Download ZIP