azure-app-onboard

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

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.

⛔ 所有代码仓库都需经过完整流程（步骤1–10），无例外。 请勿跳过步骤、拒绝执行或根据已识别内容简化流程。请按下方工作流表格顺序执行——执行前请阅读每个步骤的参考文档。

Quick Reference

快速参考

Property	Value
Best for	Developers who know what to build but not which Azure services to use
Inputs	Business idea or existing codebase, budget/scale preferences (optional)
Outputs	Architecture plan, cost estimate, IaC files, deployed Azure resources
Phases	Discover → Architect → Scaffold → Deploy (self-contained, no external skill calls)

属性	值
适用人群	清楚要构建什么但不知道该使用哪些Azure服务的开发者
输入	商业构想或现有代码库，预算/规模偏好（可选）
输出	架构方案、成本估算、IaC文件、已部署的Azure资源
阶段	发现 → 架构设计 → 生成脚手架 → 部署（独立完成，无需调用外部技能）

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

在不知道该使用哪些Azure服务的情况下部署现有代码
检查现有代码是否已准备好部署到Azure
无需重写或仅需少量修改即可将现有应用迁移至Azure
在投入基础设施前获取成本估算
了解架构决策及被否决的替代方案
获取Azure架构或服务选择相关问题的答案（例如：“我应该使用哪种数据库？”）
在无经验的情况下获得Azure入门部署的引导

When NOT to Use

何时请勿使用

Scenario	Use Instead
Run `azd up` or execute an existing deployment	`azure-deploy`
Optimize existing Azure spend	`azure-cost`
Generate Bicep/Terraform for a known architecture	`azure-prepare`
Validate infrastructure or run preflight checks	`azure-validate`
Troubleshoot a running Azure deployment	`azure-diagnostics`
Deploy to or manage AKS/Kubernetes directly	`azure-kubernetes`
Look up or list existing Azure resources	`azure-resource-lookup`

场景	替代方案
运行 `azd up` 或执行现有部署	`azure-deploy`
优化现有Azure支出	`azure-cost`
为已知架构生成Bicep/Terraform代码	`azure-prepare`
验证基础设施或执行预检查	`azure-validate`
排查运行中的Azure部署问题	`azure-diagnostics`
直接部署或管理AKS/Kubernetes	`azure-kubernetes`
查询或列出现有Azure资源	`azure-resource-lookup`

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.

⛔ 每次AppOnboard会话开始时，你必须阅读
references/pipeline-rules.md
。其中包含审批关卡、阶段生命周期、会话工件、原样部署和安全基线规则。

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.

#	Step	Action	Reference
1	Session check + Azure login	Create/resume session, verify Azure CLI auth, resolve subscription + user identity	⛔ You MUST read session-protocol.md
2	Scope triage	Check azd markers, triage question. Empty workspace or code-only (no infra) → Step 3 directly.	⛔ Read intent-gathering.md § Scope Triage
3	Prereq 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.
4	Gather intent	Present prereq results, confirm stack + Azure services, ask remaining questions.	⛔ Read intent-gathering.md § After Prereq Returns
5	Plan architecture	Write `prepare-plan.json` .	⛔ You MUST read prepare/SKILL.md
6	Scaffold approval gate	Display plan for user approval BEFORE generating any files.	⛔ Read approval-gates.md § Scaffold Gate
7	Scaffold	Generate IaC, self-review. Write `scaffold-manifest.json` . Update `context.json` .	⛔ You MUST read scaffold/SKILL.md
8	Deploy approval gate	Display validation summary. ⛔ After approval: FIRST read deploy-checklist.md → deploy/SKILL.md. NEVER `{"skill": "azure-deploy"}` .	⛔ Read approval-gates.md § Deploy Gate
9	Deploy	Execute IaC, health-check. Write `deploy-result.json` .	⛔ You MUST read deploy/SKILL.md
10	Handoff	Surface deployment identity, cleanup commands, next steps.	⛔ You MUST read `handoff-protocol.md`

⛔ 部署恢复： 在部署关卡获得批准后，或在执行任何
az deployment
/
az webapp deploy
/
az acr build
之前——如果你尚未阅读
deploy/SKILL.md
，请先阅读
.copilot-azure/sessions/{id}/deploy-checklist.md
，然后再阅读
deploy/SKILL.md
。 ⛔ 切勿调用
{"skill": "azure-deploy"}
——这是适用于不同工作流的另一个技能。

⛔ 生成脚手架后的过渡（必填）： 在写入
scaffold-manifest.json
后，你的下一个操作必须是步骤8（部署审批关卡）——不能是总结报告、“以下是生成的文件”消息或完成信号。确认
context.json
中包含
completedPhases: [...,"scaffold"]
+
currentPhase: "deploy"
（如果脚手架子代理未更新，请自行更新）。如果上下文丢失了相关内容（脚手架参考加载量较大），请重新阅读approval-gates.md § Deploy Gate，然后显示确切提示："🚀 准备好部署了吗？（是 / 手动运行 / 编辑方案 / 取消）"。此关卡内容必须是你回复的最后部分——等待用户回复。

#	步骤	操作	参考文档
1	会话检查 + Azure登录	创建/恢复会话，验证Azure CLI身份验证，解决订阅和用户身份问题	⛔ 你必须阅读session-protocol.md
2	范围分类	检查azd标记，分类问题。空工作区或仅有代码（无基础设施）→ 直接进入步骤3。	⛔ 阅读intent-gathering.md § 范围分类
3	前置条件扫描	⛔ 如果 `completedPhases` 包含 `"prereq"` 则跳过。否则：调用 `{"skill": "azure-app-onboard-prereq"}` 。写入 `prereq-output.json` ，更新 `context.json` 。若出现以下情况则暂停： `overallHealth: "blocked"` 或已设置 `routeToSkill` 。
4	收集意向	展示前置条件扫描结果，确认技术栈和Azure服务，询问剩余问题。	⛔ 阅读intent-gathering.md § 前置条件返回后
5	规划架构	写入 `prepare-plan.json` 。	⛔ 你必须阅读prepare/SKILL.md
6	脚手架审批关卡	在生成任何文件前，向用户展示方案以获得批准。	⛔ 阅读approval-gates.md § 脚手架关卡
7	生成脚手架	生成IaC代码，自我审查。写入 `scaffold-manifest.json` 。更新 `context.json` 。	⛔ 你必须阅读scaffold/SKILL.md
8	部署审批关卡	展示验证摘要。 ⛔ 获得批准后：先阅读deploy-checklist.md → 再阅读deploy/SKILL.md。切勿使用 `{"skill": "azure-deploy"}` 。	⛔ 阅读approval-gates.md § 部署关卡
9	部署	执行IaC代码，进行健康检查。写入 `deploy-result.json` 。	⛔ 你必须阅读deploy/SKILL.md
10	交接	展示部署身份、清理命令和后续步骤。	⛔ 你必须阅读 `handoff-protocol.md`

Error Handling

错误处理

Error	Remediation
Phase fails	Halt, report phase + error. User decides: retry, skip, abort.
MCP server unavailable	Skip affected checks, add disclaimer to `costEstimate.assumptions[]` and every approval gate.
Missing RBAC	Report required role + `az role assignment` command.

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

错误	补救措施
阶段执行失败	暂停，报告阶段和错误。由用户决定：重试、跳过、中止。
MCP服务器不可用	跳过受影响的检查，在 `costEstimate.assumptions[]` 和每个审批关卡中添加免责声明。
缺少RBAC权限	报告所需角色和 `az role assignment` 命令。

共享参考文档： MCP工具（跨阶段工具参数） | IaC资源（用于故障排查的Azure资源文档）