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/subscription-resolution.md

Subscription Resolution — Defensive Fallback

The azure-app-onboard orchestrator resolves the subscription at Step 1 (login hard gate) and writes subscriptionId, subscriptionName, tenantId to context.json.azure before any sub-skill runs. In normal operation, context.json.azure.subscriptionId is always set by the time prepare runs.

At prepare phase entry, verify context.json.azure.subscriptionId is set. If it is (expected path), use it — done.

If context.json.azure is somehow empty, resolve now rather than halting the flow:

  1. Check env vars — if AZURE_SUBSCRIPTION_ID is set, use it directly (with AZURE_TENANT_ID if set). Write subscriptionId, subscriptionName, tenantId to context.json.azure, done.
  2. Run az account show — az account show --query "{id:id, name:name, tenantId:tenantId}" -o json. If it succeeds, auto-select — write subscriptionId, subscriptionName, tenantId to context.json.azure. Do NOT run az account list or present a picker.
  3. Fallback: mcp_azure_mcp_subscription_list + picker — only if az account show fails. Call mcp_azure_mcp_subscription_list to retrieve all subscriptions (returns subscriptionId, displayName, isDefault).
    • 1 subscription → auto-select, no question. Write subscriptionId, subscriptionName, tenantId to context.json.azure.
    • 2+ subscriptions → present a picker via ask_user: list each subscription as a choice "{displayName} ({subscriptionId})" with the default marked. The user selects one. Write subscriptionId, subscriptionName, tenantId to context.json.azure.
  4. MCP tool fails → run az login (interactive browser login). If that fails (no browser, remote session), fall back to az login --use-device-code. After login succeeds, retry from step 2. Do NOT proceed without a resolved subscription.