Index of every page on this site: llms.txt
All skills
microsoft avatar

/azure-app-onboard

@0d60658
by microsoftmicrosoft/skills3.2k stars
373
Run it yourself

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).

Use this Skill: https://skilld.dev/gh/microsoft/skills/azure-app-onboard

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈231 tokens for metadata: the name and description. ≈1.4k when used: this file. ≈83k more on demand in 61 files.

Description uses 11.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈921 characters, or 11.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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)

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts9d3 checks · Risk SAFE
  • Gen Agent Trust Hub11d

    This skill is a comprehensive orchestrator for deploying applications to Microsoft Azure. It includes detailed sub-agent workflows for infrastructure-as-code generation, security review, and deployment execution. The analysis identified no security concerns, as all external resources and tools are within the authoritative vendor's ecosystem and use standard Azure security practices.

  • Socket9d

    No alerts

  • Snyk11d

    Risk: LOW · No issues

Signed by skilld at 0d60658. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 weeks ago
metadata
{
  "author": "Microsoft",
  "version": "1.2.9"
}

README badge

README badge for microsoft/skills/azure-app-onboard