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/intent-gathering.md

Intent Gathering

Scope Triage (Step 2 — before prereq)

⛔ Scope triage — BEFORE prereq. Check for azd template markers (azure.yaml + IaC in infra/).

Skip triage when:

  • User explicitly asks for cost estimates, service recommendations, or code analysis
  • Empty workspace (prereq’s zero-code-path handles it)
  • Code exists but no infra files (no .bicep, .tf, azure.yaml, or infra/ dir) — full pipeline is the only sensible path
  • Intentionally vulnerable app signals (🛑 detection) — proceed to prereq directly

If azd template detected

⛔ You MUST read azd-template-routing.md for detection criteria, gate presentation, and routing protocol.

If NO azd template BUT infra files present

Ask ONE ask_user question:

  1. Yes — analyze and deploy end-to-end (Recommended)
  2. Just scaffold Bicep/Terraform
  3. Just deploy it (I have IaC ready)
  4. Other

Option 1 / vague → full pipeline (Step 3). Any other → invoke {"skill": "azure-prepare"}.

After Prereq Returns (Step 4 — scan-informed intent gathering)

Prereq has written prereq-output.json and context.json.components[] — this is the authoritative source for all downstream phases (prepare and scaffold consume context.json, not prereq-output.json).

Confirm the Azure target ("☁️ Azure target: {subscriptionName} ({subscriptionId})"). If the user wants a different subscription, write to context.json.overrides[].

Present scan results first, then ask only what prereq didn't answer (≤2 if mostly covered, ≤4 if gaps):

| # | Topic | Ask if... | |---|-------|----------| | 1 | App purpose | Not obvious from detectedStack + components[] | | 3 | Data/storage | Prereq didn't detect DB/compose | | 4 | Auth approach | No MSAL/passport/auth library detected | | 5 | Scale | Always — prereq doesn't know traffic expectations |

⛔ Do NOT ask about stack/language (always answered by prereq) or budget (only if user mentioned cost). User corrections → context.json.overrides[]. Stop when covered or user says "just go."

Update intent: Merge scan results into context.json.intent. Set refinedFromScan: true and populate scanDiscoveredFacts[].