Generated banner for Azure App Onboard
Generated logo for Azure App Onboard

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

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/microsoft/azure-app-onboard/download
  2. 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

PropertyValue
Best forDevelopers who know what to build but not which Azure services to use
InputsBusiness idea or existing codebase, budget/scale preferences (optional)
OutputsArchitecture plan, cost estimate, IaC files, deployed Azure resources
PhasesDiscover → 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

ScenarioUse Instead
Run azd up or execute an existing deploymentazure-deploy
Optimize existing Azure spendcost-optimization from the optional azure-cost plugin
Generate Bicep/Terraform for a known architectureazure-prepare
Validate infrastructure or run preflight checksazure-validate
Troubleshoot a running Azure deploymentazure-diagnostics
Deploy to or manage AKS/Kubernetes directlyazure-kubernetes
Look up or list existing Azure resourcesazure-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.

#StepActionReference
1Session check + Azure loginCreate/resume session, verify Azure CLI auth, resolve subscription + user identity⛔ You MUST read session-protocol.md
2Scope triageCheck azd markers, triage question. Empty workspace or code-only (no infra) → Step 3 directly.⛔ Read intent-gathering.md § Scope Triage
3Prereq 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.
4Gather intentPresent prereq results, confirm stack + Azure services, ask remaining questions.⛔ Read intent-gathering.md § After Prereq Returns
5Plan architectureWrite prepare-plan.json.⛔ You MUST read prepare/PHASE.md
6Scaffold approval gateDisplay plan for user approval BEFORE generating any files.⛔ Read approval-gates.md § Scaffold Gate
7ScaffoldGenerate IaC, self-review. Write scaffold-manifest.json. Update context.json.⛔ You MUST read scaffold/PHASE.md
8Deploy approval gateDisplay validation summary. ⛔ After approval: FIRST read deploy-checklist.md → deploy/PHASE.md. NEVER {"skill": "azure-deploy"}.⛔ Read approval-gates.md § Deploy Gate
9DeployExecute IaC, health-check. Write deploy-result.json.⛔ You MUST read deploy/PHASE.md
10HandoffSurface deployment identity, cleanup commands, next steps.⛔ You MUST read handoff-protocol.md

Error Handling

ErrorRemediation
Phase failsHalt, report phase + error. User decides: retry, skip, abort.
MCP server unavailableSkip affected checks, add disclaimer to costEstimate.assumptions[] and every approval gate.
Missing RBACReport required role + az role assignment command.

Shared references: MCP tools (cross-phase tool parameters) | IaC resources (Azure resource docs for troubleshooting)

Files

prepare/references/pricing-guide.md

App Onboard Prepare — Pricing Guide

⛔ SELF-CHECK: If costEstimate.breakdown[] has ANY monthlyUsd > 0, at least one pricing_get or az rest pricing API call MUST appear in this session. Estimating from memory or training data is NEVER acceptable — reference values in this file may be outdated. If API fails after 2 attempts, use the reference value WITH disclaimer: "⚠️ Estimated from reference — live API unavailable."

Free-Tier Shortcut — Skip API

⛔ Check this FIRST. If ALL services use free-tier SKUs → write $0 cost estimate, add disclaimer "Estimate assumes usage within free grant limits", skip to Step 7.

ServiceFree SKUSkip API?
App ServiceF1Yes
Static Web AppsFreeYes
FunctionsConsumption (≤1M exec)Yes
Cosmos DBFree tier (1000 RU/s)Yes
Container AppsConsumption (≤180K vCPU-s)Yes

App Service Quick Reference

SKUskuNameMonthly
B1 LinuxB1~$13.14

⛔ Case-sensitive: use B1 not b1. Use skuName (not armSkuName) for Basic/Standard.


How to Use

  1. Pick SKU from sku-matrix.md based on budget intent.

  2. Find service section in pricing-guide-services.md for filter strings and formulas.

  3. Call the pricing router — tool mcp_azure_mcp_pricing (VS Code) / azure-pricing (CLI) — with intent, command: "pricing_get", and a parameters object (NOT --flags). Parallel OK. ⛔ At least one filter inside parameters: sku, service, region, service-family, or filter. ⛔ sku matches armSkuName, not skuName — use it ONLY when armSkuName is populated (App Service, MySQL/PostgreSQL, Redis). Empty-armSkuName services (ACR, Storage, Cosmos, Key Vault) return [] or 400 for sku/service — use a raw filter on serviceName + meterName instead.

  4. Apply the monthly multiplier from each meter's unitOfMeasure (see § Monthly Multiplier) — NOT a per-service constant.

  5. Cross-check returned retailPrice against planned SKU.

Monthly Multiplier — by Meter Unit

⛔ Read unitOfMeasure per price record — NEVER blanket × 730 (one service mixes units, e.g. ACR returns 1/Day + 1 Second + 1 GB/Month):

unitOfMeasureMonthly formula
1 Hour / 1/HourretailPrice × 730
1/Day / 1 DayretailPrice × 30
1 GB/MonthretailPrice × estimatedGB (already monthly)
1 Second / 1 GiB SecondretailPrice × activeUnitsPerMonth (usage-based)
10K / 1M operationsretailPrice × estimatedOps ÷ unitSize

Usage-Based Services

When AI/OpenAI/LLM components detected: add "💸 Usage-based — excluded from total" to costEstimate.breakdown[] and "⚠️🤖 AI inference costs excluded" to assumptions[]. Surface at EVERY approval gate.

Service Pricing Reference

See pricing-guide-services.md for per-service filter strings, meter names, and monthly formulas.

Key rules:

  • armSkuName is empty for most PaaS — filter by meterName or productName

  • Monthly multiplier: read unitOfMeasure (§ Monthly Multiplier) — never assume ×730

  • Functions Consumption / Static Web Apps: not in API

  • Default isPrimaryMeterRegion eq true + priceType eq 'Consumption' — but check the service section in pricing-guide-services.md first; some drop isPrimaryMeterRegion (Service Bus, Cosmos 100 RU/s, Redis Basic).

  • Service names are case-sensitive

Troubleshooting

When pricing_get returns empty: (1) Check armSkuName populated/case-sensitive? (2) HTTP fallback: https://prices.azure.com/api/retail/prices?$filter={filter}. (3) After 2 failures, use pricing-guide-services.md with disclaimer. (4) Log to costEstimate.apiFailures[].

⛔ Never claim user has free credits remaining. Use: "Check balance at portal."

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