Back to Details

azure-upgrade

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Azure Upgrade

Azure 升级

This skill handles assessment and automated upgrades of existing Azure workloads from one Azure service, hosting plan, or SKU to another — all within Azure. This includes plan/tier upgrades (e.g. Consumption → Flex Consumption), cross-service migrations (e.g. App Service → Container Apps), and SKU changes. This is NOT for cross-cloud migration — use 
azure-cloud-migrate
for that.
本Skill可处理Azure现有工作负载的评估与自动化升级，支持在Azure内部从一种Azure服务、托管计划或SKU迁移至另一种。包括计划/层级升级（例如 Consumption → Flex Consumption）、跨服务迁移（例如 App Service → Container Apps）以及SKU变更。注意：本Skill不支持跨云迁移——跨云迁移请使用
azure-cloud-migrate
。

Triggers

触发条件

User IntentExample Prompts
Upgrade Azure Functions plan"Upgrade my function app from Consumption to Flex Consumption"
Change hosting tier"Move my function app to a better plan"
Assess upgrade readiness"Is my function app ready for Flex Consumption?"
Automate plan migration"Automate the steps to upgrade my Functions plan"
用户意图示例提示
升级Azure Functions计划"将我的函数应用从Consumption升级到Flex Consumption"
更改托管层级"将我的函数应用迁移到更优计划"
评估升级就绪性"我的函数应用是否已准备好升级到Flex Consumption？"
自动化计划迁移"自动化升级我的Functions计划的步骤"

Rules

规则

  1. Follow phases sequentially — do not skip
  2. Generate an assessment before any upgrade operations
  3. Load the scenario reference and follow its rules
  4. Use 
    mcp_azure_mcp_get_bestpractices
    and 
    mcp_azure_mcp_documentation
    MCP tools
  5. Destructive actions require 
    ask_user
    — global-rules
  6. Always confirm the target plan/SKU with the user before proceeding
  7. Never delete or stop the original app without explicit user confirmation
  8. All automation scripts must be idempotent and resumable
  1. 按阶段顺序执行——不得跳过
  2. 在执行任何升级操作前生成评估报告
  3. 加载场景参考文档并遵循其规则
  4. 使用
    mcp_azure_mcp_get_bestpractices
    和
    mcp_azure_mcp_documentation
    MCP工具
  5. 破坏性操作需调用
    ask_user
    ——参考全局规则
  6. 执行前必须与用户确认目标计划/SKU
  7. 未经用户明确确认，不得删除或停止原始应用
  8. 所有自动化脚本必须具备幂等性和可恢复性

Upgrade Scenarios

升级场景

SourceTargetReference
Azure Functions Consumption PlanAzure Functions Flex Consumption Planconsumption-to-flex.md
No matching scenario? Use 
mcp_azure_mcp_documentation
and 
mcp_azure_mcp_get_bestpractices
tools to research the upgrade path.
源服务目标服务参考文档
Azure Functions Consumption计划Azure Functions Flex Consumption计划consumption-to-flex.md
无匹配场景？使用
mcp_azure_mcp_documentation
和
mcp_azure_mcp_get_bestpractices
工具研究升级路径。

MCP Tools

MCP工具

ToolPurpose
mcp_azure_mcp_get_bestpractices
Get Azure best practices for the target service
mcp_azure_mcp_documentation
Look up Azure documentation for upgrade scenarios
mcp_azure_mcp_appservice
Query App Service and Functions plan details
mcp_azure_mcp_applicationinsights
Verify monitoring configuration
工具用途
mcp_azure_mcp_get_bestpractices
获取目标服务的Azure最佳实践
mcp_azure_mcp_documentation
查询Azure升级场景相关文档
mcp_azure_mcp_appservice
查询App Service和Functions计划详情
mcp_azure_mcp_applicationinsights
验证监控配置

Steps

步骤

  1. Identify — Determine the source and target Azure plans/SKUs. Ask user to confirm.
  2. Assess — Analyze existing app for upgrade readiness → load scenario reference (e.g., consumption-to-flex.md)
  3. Pre-migrate — Collect settings, identities, configs from the existing app
  4. Upgrade — Execute the automated upgrade steps (create new resources, migrate settings, deploy code)
  5. Validate — Hit the function app default URL to confirm the app is reachable, then verify endpoints and monitoring
  6. Ask User — "Upgrade complete. Would you like to verify performance, clean up the old app, or update your IaC?"
  7. Hand off to 
    azure-validate
    for deep validation or 
    azure-deploy
    for CI/CD setup
Track progress in 
upgrade-status.md
inside the workspace root.
  1. 识别——确定源和目标Azure计划/SKU。请用户确认。
  2. 评估——分析现有应用的升级就绪性 → 加载场景参考文档（例如 consumption-to-flex.md）
  3. 预迁移——收集现有应用的设置、身份信息、配置
  4. 升级——执行自动化升级步骤（创建新资源、迁移设置、部署代码）
  5. 验证——访问函数应用默认URL确认应用可访问，然后验证端点和监控
  6. 询问用户——"升级完成。是否需要验证性能、清理旧应用或更新基础设施即代码（IaC）？"
  7. 移交给
    azure-validate
    进行深度验证，或移交
    azure-deploy
    进行CI/CD设置
在工作区根目录的
upgrade-status.md
中跟踪进度。

References

参考文档

  • Global Rules
  • Workflow Details
  • Functions
    • Consumption to Flex Consumption
    • Assessment
    • Automation Scripts
  • 全局规则
  • 工作流详情
  • Functions
    • Consumption到Flex Consumption
    • 评估
    • 自动化脚本

Next

后续操作

After upgrade is validated, hand off to:
  • azure-validate
    — for thorough post-upgrade validation
  • azure-deploy
    — if the user wants to set up CI/CD for the new app
升级验证完成后，可移交至：
  • azure-validate
    ——进行全面的升级后验证
  • azure-deploy
    ——若用户需要为新应用设置CI/CD