PlugWiki

azure-app-onboard-prereq Skill: Check Your App Is Ready for Azure

Microsoft's skill that checks whether your code is ready to deploy to Azure, before any infrastructure work.

Installs
160.4K
on skills.sh
Stars
1.6K
on GitHub
Files
15
besides SKILL.md
Updated
Oct 2026
last repo commit

azure-app-onboard-prereq makes Claude scan your repository and judge build health, app completeness and Azure deployment feasibility. Each component gets a PASS, WARN or FAIL verdict, and it can fix problems once you agree.

It is phase 1 of 4 in Microsoft's Azure app onboarding flow and also runs on its own. It writes session files in your project, runs az account show, and by rule does not run installs, builds or tests during the check.

Good for

  • Developers about to move an app to Azure who want a go or no-go on the code first
  • Teams whose repo still uses AWS or Google Cloud SDKs and needs a migration decision
  • People with no code yet: it has a path for starting from scratch

Install azure-app-onboard-prereq

Claude Code

  1. 1

    Copy this prompt.

    Install the azure-app-onboard-prereq skill in Claude Code. Run this command:
    
    /plugin install azure@claude-plugins-official
    
    Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Azure CLI signed in with az login, Node.js 18+.

The plugin also wires in the Azure MCP Server, whose tools this skill calls. Installing the skill alone leaves those tools out. The README also lists an Azure account and the Azure Developer CLI (azd auth login) for deployment workflows.

From the project README. Source.

What's in the skill

When it loads

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

Sections in SKILL.md

  1. When NOT to Use
  2. Rules
  3. MCP Tools
  4. Workflow
  5. Step 1: Session Check
  6. Step 2: Scan Workspace
  7. Step 3: Per-Component Evaluation
  8. Step 4: Write Artifacts + Readiness Gate
  9. Step 5: Present Findings
  10. Step 6: Remediation (conditional)
  11. Step 7: Write Final State
  12. Step 8: Route
  13. Outputs

Key facts

Author
Microsoft
License
MIT
Installs on skills.sh
160,411 (Nov 2, 2026)
GitHub stars (whole repo)
1,609 (Nov 2, 2026)
Last commit to the repo
Oct 30, 2026

What it includes

  • Creates or resumes a session folder and reads your Azure account

    Uses .copilot-azure/sessions/ in your project, writes context.json, and runs az account show to record the subscription id, name and tenant.

    Runs code · Step 1: Session check

  • Finds components, infrastructure files and services

    Detects project files, Terraform providers and CLI availability. An early gate searches for AWS, Google Cloud and Firebase SDKs.

    Files · Step 2: Scan workspace

  • Three checks per component

    Build check, completeness check and deployability check, each with its own reference file. A monorepo adds a component-mapping step.

    Read · Step 3: Per-component evaluation

  • Writes the results to disk

    Produces prereq-output.json and a readiness-report.md in the session folder.

    Write · Step 4: Artifacts and readiness gate

  • Shows verdicts grouped by severity

    PASS, WARN or FAIL per component before anything else happens.

    Step 5: Present findings

  • Fixes problems after you consent

    Code or destructive changes need your answer first. Build and test commands are allowed only on code the agent changed or wrote, with consent.

    Runs code · Step 6: Remediation (if needed)

  • Records the git commit the scan used

    Runs git rev-parse HEAD and stores the SHA as lastScanCommit.

    Runs code · Step 7: Write final state

  • Offers the next skill

    Can hand off to azure-cloud-migrate, azure-app-onboard or azure-prepare, depending on the result and whether Azure infra exists.

    Step 8: Route

  • Best-practice check and CLI tool check

    mcp_azure_mcp_get_azure_bestpractices validates the stack; mcp_azure_mcp_extension_cli_install checks or installs az, azd and func.

    Runs code · Azure MCP tools

From the official docs

Permissions

Medium risk

The skill makes Claude read your repo and Azure login details, write session files into your project and edit code once you agree. Work on a branch and check the new session folder before you commit.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It writes session files into your project

    The .copilot-azure/sessions/ folder holds context.json, prereq-output.json and a readiness report. Check git status and decide whether to commit them.

  • It records your Azure account details

    It runs az account show and saves the subscription id, name and tenant id in context.json. Keep that file out of public repos.

  • It can change your code after you agree

    Remediation edits code, and consent-gated build or test runs apply only to code it changed or wrote. Review each change on a branch.

  • The plugin route adds MCP servers and needs Node.js 18+

    The README's Claude Code install adds the Azure plugin, which wires in the Azure MCP Server and Foundry MCP, started through npx. Those servers act on live Azure resources with your az login. Review what the plugin enables before installing, or take only this skill.

  • One tool can install Azure CLIs

    The Azure MCP tool it uses is described as checking or installing az, azd and func. Approve installs you did not expect.

Technical details
Talks toAzure MCP tools. Azure CLI (az account show)
Sign-in and keysIt uses your existing az login session and writes the subscription id, name and tenant id into context.json in your project.

Questions

How do I install azure-app-onboard-prereq?

Use the install box above. The README's Claude Code route installs the whole Azure plugin, which also sets up the Azure MCP tools this skill calls. The README lists Azure CLI with az login, and Node.js 18+, as prerequisites.

What does it check?

Three things per component: build health, app completeness and deployability to Azure. It also checks for AWS, Google Cloud and Firebase SDKs and offers to redirect you to azure-cloud-migrate if it finds working use of them.

Does it run my tests or install packages?

Not during the check. The SKILL.md forbids npm install, test runs, builds and similar commands. The two exceptions are code the agent changed during remediation and code it wrote from scratch, both after you consent.

Do I need the other Azure skills?

No. The SKILL.md says direct entry is supported. After the check it can hand off to azure-app-onboard, azure-prepare or azure-cloud-migrate, which are separate skills in the same repo.

How is it different from azure-validate and azure-prepare?

This skill checks code before infrastructure work. The SKILL.md sends infrastructure validation (Bicep, Terraform, azure.yaml) to azure-validate, IaC generation to azure-prepare, end-to-end onboarding to azure-app-onboard and azd up to azure-deploy.

Does it work in the Claude app?

The README lists GitHub Copilot, Claude Code, Gemini CLI, Cursor and Codex. The Claude app is not documented, and the skill needs your local repo and the Azure CLI.

Is it safe?

It reads your repo and Azure login details, writes session files into your project, and can edit code after you agree. Work on a branch, check the session folder before you commit, and review each change it proposes.

Information

updated Nov 2, 2026

Folder
skills/azure-app-onboard-prereq

microsoft/azure-skillsskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 5
  1. microsoft/azure-skills README · github.com
  2. skills CLI commands · github.com
  3. azure-app-onboard-prereq on skills.sh · skills.sh
  4. azure-app-onboard-prereq SKILL.md · github.com
  5. microsoft/azure-skills · github.com

Updated Nov 2, 2026.