AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

azure-app-onboard-prereq

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

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-app-onboard-prereq at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 14

references/deployability-check.md

Deployability Check

⛔ No build/install/test commands — npm install, npm test, dotnet build, dotnet restore, dotnet test, pip install, pytest, go mod download, cargo build. Use static analysis only during this check.

Assess whether the repository can feasibly be deployed to Azure and whether a preparation plan can be created.

⛔ You MUST read the following in order. Skip items marked conditional if the condition is not met:

  1. component-mapping.md — Steps 1–2: Component→Azure mapping, existing infrastructure detection, Terraform provider classification, compose service extraction. Conditional: monorepo only (>1 project manifest found). For single-component repos, skip to Step 3.
  2. dependency-compatibility.md — Step 3: EOL runtimes/frameworks, archived repos, vulnerable apps, platform deps, Dockerfile analysis, native module detection
  3. Steps 4–5 below

Step 4: Recipe Feasibility

Assess whether at least one deployment recipe is viable.

| Check | Question | |-------|----------| | AZD feasible? | Standard web app stack? No exotic build requirements? | | Container feasible? | Can be Dockerized? Or already has Dockerfile? | | Functions feasible? | Event-driven or HTTP-triggered stateless handlers? | | Terraform feasible? | User has TF experience or existing TF files? |

| Outcome | Verdict | |---------|---------| | At least one recipe clearly viable | ✅ PASS | | Viable with modifications (config change, Dockerfile tweak) | 🔧 Recommended Fix — note required changes | | Viable but requires significant rework (>5 files, architecture change) | 🔶 Major Migration — warn about scope | | Minor platform concerns (ephemeral storage, missing .dockerignore) | ⚠️ WARN — informational | | No viable recipe identified | ❌ FAIL |

Step 5: Specialized Skill Detection

Check if the repo's stack requires a specialized deployment skill. If a match is found, set context.json.routeToSkill and routeReason so Step 8 routes directly.

Non-Azure cloud SDK deps (AWS/GCP SDKs, Firebase, etc.) — evaluated and carried as 🔶 blockers (no routeToSkill); prereq stops at Step 8. See dependency-compatibility.md § Non-Azure Cloud SDK Dependencies.

| Dependency / Pattern | routeToSkill | routeReason | |---------------------|----------------|---------------| | @github/copilot-sdk, github-copilot-sdk, GitHub.CopilotSdk | azure-hosted-copilot-sdk | copilot-sdk-detected | | azure_ai_projects, azure-ai-agents, foundry-agents | microsoft-foundry | foundry-agents-detected |

f1Viable Aggregation

After the deployability check completes, cross-check buildRequirements.f1Viable. The build axis may have set an initial value — the deployability check MUST override it to false if ANY blocker was found during dependency-compatibility.md § Native Module Detection or § F1 Viability — Beyond Native Modules. Verify f1BlockReason is populated when f1Viable: false.