All skills
microsoft avatar

/azure-app-onboard

@cda1f27 official

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/github-copilot-for-azure/azure-app-onboard

This session only. Nothing lands on disk.

scaffoldreferencesscaffold-healing-rules.md

≈853 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Scaffold Healing Rules

Self-healing loop for scaffold validation failures. Contains error classification (FIXABLE vs BLOCKING) and scaffold-specific escalation and plan-change rules.

Error Classification

Error Type Class Auto-Fix Strategy
Invalid property name FIXABLE Fix from schema
Syntax error (HCL/Bicep) FIXABLE Regenerate from references
Missing required property FIXABLE Call mcp_bicep_build_bicep for structured error, fix from diagnostics output
Wrong API version FIXABLE Call mcp_bicep_list_az_resource_types_for_provider with { providerNamespace: "..." } for latest GA. Fallback: reference file examples
Provider version conflict FIXABLE Update required_providers
Undeclared variable FIXABLE Add to variables.tf
Policy-blocked SKU FIXABLE Next-best from rejectedAlternatives[]
Circular dependency FIXABLE Break cycle — refactor module refs
Permission/RBAC insufficient BLOCKING Surface role + az role assignment create
State backend inaccessible BLOCKING Surface az storage account create
Region unsupported BLOCKING Suggest alternate regions (user decision)
Quota exhaustion (all tiers+regions) PLAN_LEVEL_CHANGE ⛔ See § PLAN_LEVEL_CHANGE
Quota exhaustion (single region) PLAN_LEVEL_CHANGE ⛔ Region pivot — skip quotaValidation.checkedRegions failures
Policy blocks service entirely PLAN_LEVEL_CHANGE ⛔ Map to rejectedAlternatives[]

Healing Escalation Cadence

Classify Step 11 failures using the table above. FIXABLE: edit IaC → re-validate (max 3 before asking). Each attempt must be a different fix. BLOCKING: surface to user, halt.

⛔ After each FIXABLE auto-fix: call mcp_bicep_build_bicep with { filePath: "infra/main.bicep" } to quick-check before re-dispatching the validate sub-agent. If errors remain, fix again — saves a sub-agent dispatch. Fallback: az bicep build.

⛔ After 3 attempts: summarize error pattern, propose specific next fix (never "I'll try again" without naming the change), present options: "Yes, try that" (5 more) | "I have a suggestion" (apply user fix) | "Stop" (write validationResult.status: "Failed"). Ask again every 5 thereafter.

⛔ Same error 3×: read iac-resources.md for docs. Present to user; stop auto-healing that pattern.

PLAN_LEVEL_CHANGE

⛔ Service type or region changes require user re-approval — never silently rewrite IaC.

Step Action
1. STOP Never silently change service/region
2. Update plan prepare-plan.json: services[], naming.resources[], costEstimate, deployStrategy per prepare-schemas.ts
3. Re-approve "⚠️ Plan change: {old} → {new} (~${new}/mo). Approve? (Yes / Edit / Cancel)"
4. Regenerate New module files with correct names, delete stale, re-run self-review + validation
5. Log ScaffoldHealingAttempt with planLevelChange: true. Counts toward healing cap

⛔ Artifact consistency: After any service/region/SKU change, update ALL upstream artifacts (prepare-plan.json, scaffold-manifest.json, context.json, IaC files) — the plan MUST match deployed reality.

Source: SKILL.md on GitHub

No alerts22d3 checks · Risk SAFE
  • Gen Agent Trust Hub22d

    This skill includes some security considerations such as the processing of untrusted project files to generate deployment scripts and the dynamic generation of infrastructure code. While these warrant review, they are used within the skill's intended functionality to automate Azure onboarding. See detailed analysis for context.

  • Socket22d

    No alerts

  • Snyk22d

    Risk: LOW · No issues

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

Last checked against GitHub yesterday.

Activeupdated last week
metadata
{
  "author": "Microsoft",
  "version": "0.0.0-placeholder"
}

README badge

README badge for microsoft/github-copilot-for-azure/azure-app-onboard