Azure App Onboard Prereq

Add skill

Assess whether source code is ready to deploy to Azure — the check BEFORE infrastructure work. Evaluates build health, app completeness, dependencies and local services, stack compatibility, and deployment feasibility. Answers questions about what your app needs before it can be deployed — frameworks, dependencies, and configuration. Checks whether dependencies are compatible and identifies deployment blockers and unsupported frameworks. WHEN: \"evaluate my repo\", \"is my app ready to deploy\", \"what does my app need to deploy\", \"what do I need before deploying\", \"does my app need\", \"can I ship this to Azure\", \"scan my repo for issues\", \"is this app deployable\", \"check if my app is ready for Azure\", \"do I need a Dockerfile\", \"what's blocking my deployment\", \"are there any blockers\", \"are my dependencies compatible\", \"does Azure support my framework\", \"what needs to change before deploying\", \"check my app configuration\".

Permissions

Version history

Azure App Onboard Prereq — Repository Evaluation

Evaluate a user's repository for build health, app completeness, and Azure deployment feasibility — before infrastructure planning. Produces per-component verdicts (PASS/WARN/FAIL) consumed by downstream phases.

Orchestrator relationship: Called by azure-app-onboard at Step 3, or standalone for code readiness checks. When called by orchestrator, return control to azure-app-onboard after writing artifacts — do NOT invoke downstream phases directly.

Phase 1 of 4 in AppOnboard pipeline. Session: .copilot-azure/sessions/{session-id}/. Reads context.json. Writes components[], repo{}, detectedInfra[]. Produces prereq-output.json. Schema: prereq-schemas.ts — PrereqOutput, BuildRequirements. Direct entry supported.

When NOT to Use

Signal	Redirect
Validate infrastructure (Bicep/TF/azure.yaml)	azure-validate
Generate IaC	azure-prepare
End-to-end idea-to-production	azure-app-onboard
Run `azd up` or deploy	azure-deploy

Rules

⛔ ABSOLUTE PROHIBITION — npm install, npm test, npx jest, pytest, and ALL install/build/test commands are NEVER allowed. Under NO circumstances may you run npm install, npm test, npx jest, pip install, pytest, dotnet build, dotnet restore, dotnet test, go mod download, cargo build, or ANY package-manager install, build, or test command during the prereq phase. Do NOT run test suites to verify code — check for test config files statically instead. The prereq phase is read-only evaluation + static-only verification. ONLY exception — two sanctioned contexts, both consent-gated: (a) code the agent modified during migration/remediation (see remediation-protocol.md step 6), or (b) code the agent wrote from scratch on the zero-code path (see ). In either case, install/build/test runs ONLY via the user-confirmed build-validation gate ( Step 3), after the user answers that specific per-command consent prompt. General prior consent never counts.

Tool	Purpose
`mcp_azure_mcp_get_azure_bestpractices`	Validate detected stack patterns against Azure best practices
`mcp_azure_mcp_extension_cli_install`	Check/install required CLI tools (az, azd, func)

Sub-step	Action	Reference
3.1	Build check	⛔ You MUST read build-check.md
3.2	Completeness check	⛔ You MUST read completeness-check.md
3.3	Deployability check	⛔ You MUST read deployability-check.md
3.3a	Component mapping (conditional)	Read component-mapping.md ONLY IF >1 project manifest found (monorepo)

#	Condition	Action
1	`routeToSkill` set (any entry)	`ask_user`: "Redirect to {routeToSkill}" / "Not now". ⛔ Pipeline stops — do NOT proceed to architecture planning.
2	`cloudSdkFindings[]` non-empty (user chose "Continue evaluation anyway")	Present the cloud-SDK → Azure swap mapping as 🔶 blockers, then `ask_user` with this exact prompt: "🔶 Cloud SDK migration required — these dependencies must be swapped before this app can deploy to Azure. (Redirect to azure-cloud-migrate / Stop — swap manually and re-run)" — Redirect sets `routeToSkill: "azure-cloud-migrate"`, Stop halts. ⛔ Pipeline stops — do NOT proceed to architecture planning, and do NOT offer a "continue to prepare" option; the app can't deploy until the deps are swapped.
3	Orchestrator + no `routeToSkill`	Tell the user: "✅ Your app has been evaluated and is ready — let's plan your Azure deployment." Then invoke `azure-app-onboard`. ⛔ Do NOT stop, do NOT wait for user input, do NOT narrate internal handoffs. The user already consented to the full pipeline at scope triage.
4	Direct + ready/readyWithCaveats + no Azure infra	`ask_user`: "Deploy to Azure (full pipeline)" → invoke `azure-app-onboard` / "Not now"
5	Direct + ready/readyWithCaveats + existing Azure infra	`ask_user`: "Start fresh" → invoke `azure-app-onboard` / "Use existing infra" → invoke `azure-prepare` / "Not now"
6	Direct + blocked	Report blocker summary + "Fix and re-run."

Artifact	Location	Consumer
Session context	`context.json` → `components[]`, `repo{}`, `detectedInfra[]`, `detectedServices[]`	All downstream phases
Prereq output	`prereq-output.json`	prepare phase (via `azure-app-onboard`)
Readiness report	`.copilot-azure/sessions/{uuid}/readiness-report.md`	User (offline reference)

Azure App Onboard Prereq

Azure App Onboard Prereq — Repository Evaluation

When NOT to Use

Rules

MCP Tools

Workflow

Step 1: Session Check

Step 2: Scan Workspace

Step 3: Per-Component Evaluation

Step 4: Write Artifacts + Readiness Gate

Step 5: Present Findings

Step 6: Remediation (conditional)

Step 7: Write Final State

Step 8: Route

Outputs