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

deploy/PHASE.md

Deploy — IaC Execution & Health Verification

Quick Reference

Property	Value
Best for	Executing validated IaC against Azure, health-checking deployed resources
Inputs	`prepare-plan.json` + `scaffold-manifest.json` from `.copilot-azure/sessions/{id}/`
Outputs	`deploy-result.json` written to session directory
Parent	azure-app-onboard

When to Use This Skill

Invoked by the azure-app-onboard orchestrator at Phase 4 when scaffold-manifest.json exists with files[] and validationResult. Not directly user-routable.

Return to orchestrator: When complete, return control to azure-app-onboard for handoff (Step 10). Do NOT start new phases.

When NOT to Use

Scenario	Use Instead
Plan architecture, map services, estimate costs	prepare
Generate IaC files from a plan	`azure-app-onboard` Step 7 (scaffold)
Run `azd up` or execute existing deployment templates	`azure-deploy`
Debug a running app after deployment	`azure-diagnostics`
Optimize existing Azure spending	`cost-optimization` from the optional `azure-cost` plugin

Workflow

⛔ Sub-agent delegation is MANDATORY for Step 0. Read subagent-preflight.md, then dispatch as a task with the COMPLETE and UNMODIFIED template text between <<<TEMPLATE_START>>> / <<<TEMPLATE_END>>> delimiters. Do NOT summarize or rewrite the template — the sub-agent needs every "Read [file]" instruction to produce a correct deploy-checklist.md. Append session artifact data AFTER the template block. If your next action after reading the template is anything other than task, you are executing it inline instead of delegating.

⛔ Healing loop: ask user after 3 attempts, then every 5 (counter = healingAttempts[].length).

⛔ Region lock: Before az deployment retry, compare --location against prepare-plan.json.deploymentVariables.location. If changed → re-approval gate required. Update plan after approval.

⛔ After compaction or any az deployment/az webapp deploy/az acr build/failed health check: re-read deploy-checklist.md. If missing → fill from deploy-checklist-template.md. On significant context loss: also re-read this PHASE.md.

#	Step	Action	Artifact	Reference
0	Dispatch preflight sub-agent	⛔ You MUST dispatch `subagent-preflight.md` as a `task`. ⛔ agent_type: `"task"` — NEVER `"general-purpose"`. Read the template, then your NEXT action MUST be `task`. If after reading the template your next action is `powershell`, `view`, or anything other than `task`, STOP — you are executing inline instead of delegating. Writes `deploy-checklist.md`. `view` it immediately after return.	`deploy-checklist.md`	⛔ You MUST read `subagent-preflight.md`
1	Read upstream artifacts	Load `prepare-plan.json` + `scaffold-manifest.json`. Check `validationResult`. Resolve subscription + deployment variables.	—	—
3	Preflight checks	Auth, mandatory what-if preview, RBAC, RG per `deploy-checklist.md` § Preflight.	—	⛔ You MUST read `deploy-checklist.md` (re-read if compaction occurred)
4	Deploy approval gate	Present cost + resource summary per `deploy-checklist.md` § Deploy approval gate format.	—	—
5b	Write deploy-result.json skeleton	⛔ Read `deploy-schemas.ts`, write skeleton (`status: "in-progress"`). Must exist BEFORE first `az` command.	`deploy-result.json`	⛔ You MUST read `deploy-schemas.ts`
6	Execute deployment	⛔ BEFORE `az deployment sub create`: Generate portal link — `$dn="{deploymentName}"; $r="/subscriptions/{subId}/providers/Microsoft.Resources/deployments/$dn"; $l="https://portal.azure.com/#view/Microsoft_Azure_Resources/DeploymentDetails.MenuView/~/overview/id/$($r.Replace('/','%2F'))"; Write-Output "LINK=$l"`. ⛔ Auto-open link in browser: `Start-Process $l 2>$null`. Print bare URL in chat (ctrl-clickable).<br>Auto-generate ALL `@secure()` params (`openssl rand -base64 32 \| tr -d '/+='`), NEVER `ask_user` for passwords; on retry reuse from `deploy-secrets.env` or Key Vault — NEVER regenerate (see deploy-safety.md § Deploy Checklist). THEN deploy IaC.	—	⛔ You MUST read `deploy-checklist.md` § Execute deployment
6b	Deploy application code	⛔ Deploy code for EVERY service in `prepare-plan.json.services[]`. Follow `deploy-checklist.md` § Code deploy.	—	⛔ You MUST read `deploy-checklist.md` § Code deploy
7	Health-check + SCM re-disable	HTTP GET per endpoint (max 3 iterations). ⛔ Multi-service apps: Also inspect the response body for error patterns (`connection refused`, `MODULE_NOT_FOUND`, `localhost`, `SET-IN-DEPLOY-PHASE`) — HTTP 200 alone does not mean functional when the app depends on another service or KV secrets. Then ⛔ for EVERY App Service/Functions app run BOTH commands — no exceptions: `az rest --method put --url "/subscriptions/{sub}/resourceGroups/{rg}/providers/Microsoft.Web/sites/{app}/basicPublishingCredentialsPolicies/scm?api-version=2023-12-01" --headers "Content-Type=application/json" --body '{"properties":{"allow":false}}'` then verify: `az rest --method get --url "/subscriptions/{sub}/resourceGroups/{rg}/providers/Microsoft.Web/sites/{app}/basicPublishingCredentialsPolicies/scm?api-version=2023-12-01" --query properties.allow -o tsv` (must return `false`).	`deploy-result.json` full	⛔ You MUST read `deploy-checklist.md` § Health check
8	Finalize artifacts	⛔ Read `deploy-schemas.ts`. ⛔ Re-read `deploy-checklist.md` § Artifact verification — follow ALL 5 checks. ⛔ No "live"/handoff message until you overwrite the skeleton `deploy-result.json` — flip `status` off `"in-progress"` (→ `succeeded`/`failed`) and fill healthStatus, endpoints, completedUtc, deploymentNames, healingAttempts. Write `deployment-summary.md` (status table + health + portal link(s) + cleanup commands — same content as your handoff message). Update `context.json` — add `"deploy"` to `completedPhases`, `currentPhase: null`, `lastModifiedUtc`. Read back to confirm `status != "in-progress"` and `"deploy"` ∈ `completedPhases`. ⛔ Then STOP — return to orchestrator. No further CLI commands.	`deploy-result.json` final + `deployment-summary.md` + `context.json` update	⛔ You MUST read `deploy-schemas.ts` + ⛔ Re-read `deploy-checklist.md` § Artifact verification
9	Error handling + healing	⛔ Only if Steps 6/6b/7 returned nonzero exit code or health check failed. Skip entirely on clean deploys. Classify errors, healing loop, PLAN_LEVEL_CHANGE re-approval per `deploy-checklist.md` § During healing. ⛔ Even on unrecoverable failure: write `deploy-result.json` with `status: "failed"` and `errorDetails` before returning to orchestrator — the artifact must always exist.	—	⛔ You MUST read `error-classification.md`

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-09

Also distributed in

microsoft/azure-skills

AutoGineer is not affiliated with or endorsed by Microsoft or 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

deploy/PHASE.md

Deploy — IaC Execution & Health Verification

Quick Reference

When to Use This Skill

When NOT to Use

Workflow

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