AGENTIC MEMORY

Skills

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

← Back to Skills

azure-app-onboard

End-to-end orchestrator: from a business idea, app idea, or existing app to running Azure deployment with cost estimates and pre-deploy approval. Analyzes your app, auto-detects the right Azure services, scaffolds infrastructure code, and deploys — tailored to your app, not a template. Handles moving existing apps to Azure without rewriting or with minimal changes. WHEN: bring your app to Azure, plan my app, cost to run, is my code ready to deploy, deploy my app to the cloud, deploy all my services, what Azure services do I need, plan my Azure deployment, deploy my new app to Azure, one-click deploy, I have an app and want it on Azure, migrate my app to Azure, help me get started, build an app, no code yet, starter project. DO NOT USE FOR: use azd for deployment(use azure-deploy), optimizing existing costs (use cost-optimization), code readiness checks only (use azure-app-onboard-prereq).

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 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 · 11

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 → attempt az login (interactive browser login). If that fails (no browser, remote session), fall back to az login --use-device-code. On success, retry from step 2. Cap login at 3 attempts total — if login still fails after the 3rd attempt, HALT once with a clear, actionable message: the exact az login --tenant <tenant> command to run, and that re-invoking the skill resumes this session (completed phases are preserved). Do NOT retry past 3 attempts, and do NOT proceed without a resolved subscription.