azure-app-onboard-prereq

Topics in the source

• 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

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. | 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 | ⛔ 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, dotne

This is an excerpt. Refer to the complete source and its current requirements.