$ loading_
评估并修复 Azure PaaS 应用可靠性配置，提升高可用与容灾能力
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "azure-reliability" 技能： 1. 下载 https://raw.githubusercontent.com/microsoft/GitHub-Copilot-for-Azure/main/plugin/skills/azure-reliability/SKILL.md 2. 保存为 ~/.claude/skills/azure-reliability/SKILL.md 3. 装好后重载技能，告诉我可以用了
请评估这个 Azure App Service 和 Azure Functions 环境的可靠性，检查是否启用了可用区冗余、ZRS 存储、健康探针和多区域故障切换，并列出单点故障与修复建议。
输出按功能分类的可靠性检查清单，标明风险项、影响说明和优先级修复建议。
根据当前扫描结果，为我的 Azure PaaS 应用生成分阶段可靠性改进方案，先给出低风险改动，再给出需要架构调整的高影响改动，并附上每一步的 CLI 或 IaC 修改建议。
输出可执行的分阶段整改计划，包含实施顺序、变更方式、确认节点和预期收益。
请检查我的 Azure Functions 与 App Service 是否具备多区域故障切换能力，并评估当前容灾设计是否存在区域级单点故障；如有问题，请给出具体修复步骤。
输出容灾准备度评估结果，说明故障切换缺口、风险来源及对应修复步骤。
| Property | Details |
|---|---|
| Best for | Reliability posture assessment, zone redundancy enablement, multi-region failover setup |
| Primary capabilities | Reliability assessment table, Zone Redundancy Configuration, Multi-Region IaC Generation |
| Supported services | Azure Functions, App Service (Container Apps planned for a future version) |
| MCP tools | Azure Resource Graph queries, Azure CLI commands |
Activate this skill when user wants to:
Scope note: This skill currently covers Azure Functions and Azure App Service only. If the user asks about Azure Container Apps reliability, acknowledge that support is planned but not yet available, and only proceed with the parts that apply to App Service and Functions resources in scope.
az loginaz extension add --name resource-graph| Tool | Purpose |
|---|---|
mcp_azure_mcp_extension_cli_generate | Generate az CLI commands for resource queries and configuration |
mcp_azure_mcp_subscription_list | List available subscriptions |
mcp_azure_mcp_group_list | List resource groups |
Primary query method: Azure Resource Graph via az graph query (requires az extension add --name resource-graph).
Important: Always scope queries to the user's specified resource group or subscription. Add these filters to every Resource Graph query:
| where resourceGroup =~ '<rg-name>'--subscriptions <sub-id> flag on az graph query| where name =~ '<app-name>'Two-step assessment: platform-level discovery first, then per-service deep dive.
Step 1 — Platform discovery (find what's there). Use these to enumerate resources in scope and detect cross-cutting reliability gaps:
| Platform check | Reference |
|---|---|
| Zone redundancy — discovery | references/zone-redundancy-checks.md |
| Storage redundancy (cross-service) | references/storage-redundancy-checks.md |
| Multi-region & global load balancers | references/multi-region-checks.md |
| Front Door / Traffic Manager / App Insights probes | references/health-probe-checks.md |
…
分析并精简 Markdown 内容，降低 token 消耗并提升 AI 处理效率。
评估 AKS 集群与工作负载对 Automatic 的兼容性并提供迁移修复建议