Skip to content
FunCoding

Search

Search docs, Skills and MCP

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

DevOps 与云1.5kskills/azure-app-onboard/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/microsoft/azure-skills/azure-app-onboard/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

Azure App Onboard

⛔ Every repo goes through the full pipeline (Steps 1–10). No exceptions. Do not skip steps, refuse, or short-circuit based on what you recognize. Follow the Workflow table below sequentially — read each step's references before acting.

Quick Reference

PropertyValue
Best forDevelopers who know what to build but not which Azure services to use
InputsBusiness idea or existing codebase, budget/scale preferences (optional)
OutputsArchitecture plan, cost estimate, IaC files, deployed Azure resources
PhasesDiscover → Architect → Scaffold → Deploy (self-contained, no external skill calls)

When to Use This Skill

  • Deploy existing code without knowing which Azure services to use
  • Check if your existing code is ready to deploy to Azure
  • Move an existing app to Azure without rewriting or with minimal changes
  • Get cost estimates before committing to infrastructure
  • Understand architecture decisions and rejected alternatives
  • Get answers to Azure architecture or service selection questions (e.g., "What database should I use?")
  • Get guided Azure onboarding without prior experience

When NOT to Use

ScenarioUse Instead
Run azd up or execute an existing deploymentazure-deploy
Optimize existing Azure spendcost-optimization from the optional azure-cost plugin
Generate Bicep/Terraform for a known architectureazure-prepare
Validate infrastructure or run preflight checksazure-validate
Troubleshoot a running Azure deploymentazure-diagnostics
Deploy to or manage AKS/Kubernetes directlyazure-kubernetes
Look up or list existing Azure resourcesazure-resource-lookup

If cost-optimization is unavailable, explain that it is provided by the optional azure-cost plugin and direct the user to their client's supported plugin installation flow; do not imply the handoff completed.

Pipeline Rules

⛔ You MUST read references/pipeline-rules.md at the start of every AppOnboard session. It contains approval gates, phase lifecycle, session artifacts, deploy-as-is, and security baseline rules.

Workflow

⛔ Deploy recovery: After deploy gate approval OR before any az deployment/az webapp deploy/az acr build — if you haven't read deploy/SKILL.md, read .copilot-azure/sessions/{id}/deploy-checklist.md first, then deploy/SKILL.md. ⛔ NEVER invoke {"skill": "azure-deploy"} — that is a DIFFERENT skill for a DIFFERENT workflow.

⛔ Post-scaffold transition (MANDATORY): Immediately after scaffold-manifest.json is written, YOUR NEXT ACTION MUST be Step 8 (Deploy Approval Gate) — NOT a summary report, NOT a "here are the generated files" message, NOT a completion signal. Confirm context.json has completedPhases: [...,"scaffold"] + currentPhase: "deploy" (update it yourself if the scaffold subagent didn't). Re-read approval-gates.md § Deploy Gate if evicted from context (scaffold reference loading is heavy), then present the exact prompt: "🚀 Ready to deploy? (Yes / Run manually / Edit plan / Cancel)". This gate is the LAST content in your response — wait for the user's reply.

#StepActionReference
1Session check + Azure loginCreate/resume session, verify Azure CLI auth, resolve subscription + user identity⛔ You MUST read session-protocol.md
2Scope triageCheck azd markers, triage question. Empty workspace or code-only (no infra) → Step 3 directly.⛔ Read intent-gathering.md § Scope Triage
3Prereq scan⛔ Skip if completedPhases includes "prereq". Otherwise: invoke {"skill": "azure-app-onboard-prereq"}. Write prereq-output.json, update context.json. Halt if: overallHealth: "blocked" OR routeToSkill set.
4Gather intentPresent prereq results, confirm stack + Azure services, ask remaining questions.⛔ Read intent-gathering.md § After Prereq Returns
5Plan architectureWrite prepare-plan.json.⛔ You MUST read prepare/SKILL.md
6Scaffold approval gateDisplay plan for user approval BEFORE generating any files.⛔ Read approval-gates.md § Scaffold Gate
7ScaffoldGenerate IaC, self-review. Write scaffold-manifest.json. Update context.json.⛔ You MUST read scaffold/SKILL.md
8Deploy approval gateDisplay validation summary. ⛔ After approval: FIRST read deploy-checklist.md → deploy/SKILL.md. NEVER {"skill": "azure-deploy"}.⛔ Read approval-gates.md § Deploy Gate
9DeployExecute IaC, health-check. Write deploy-result.json.⛔ You MUST read deploy/SKILL.md
10HandoffSurface deployment identity, cleanup commands, next steps.⛔ You MUST read handoff-protocol.md

Error Handling

ErrorRemediation
Phase failsHalt, report phase + error. User decides: retry, skip, abort.
MCP server unavailableSkip affected checks, add disclaimer to costEstimate.assumptions[] and every approval gate.
Missing RBACReport required role + az role assignment command.

Shared references: MCP tools (cross-phase tool parameters) | IaC resources (Azure resource docs for troubleshooting)

Similar Skills

shipping-and-launch
addyosmani/agent-skills103k

shipping-and-launch

Prepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.

DevOps & cloud

publish
code-yeongyu/oh-my-openagent70k

publish

Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: <patch|minor|major|explicit-semver>. Triggers: publish, release, deploy, npm publish.

DevOps & cloud

acceptance-orchestrator
sickn33/agentic-awesome-skills47k

acceptance-orchestrator

Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.

DevOps & cloud

event-store-design
wshobson/agents40k

event-store-design

Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.

DevOps & cloud

arize-ai-provider-integration
github/awesome-copilot40k

arize-ai-provider-integration

Creates, reads, updates, and deletes Arize AI integrations that store LLM provider credentials used by evaluators and other Arize features. Supports any LLM provider (e.g. OpenAI, Anthropic, Azure OpenAI, AWS Bedrock, Vertex AI, Gemini, NVIDIA NIM). Use when the user mentions AI integration, LLM provider credentials, create integration, list integrations, update credentials, delete integration, or connecting an LLM provider to Arize.

DevOps & cloud

appinsights-instrumentation
github/awesome-copilot40k

appinsights-instrumentation

Instrument a webapp to send useful telemetry data to Azure App Insights

DevOps & cloud