Azure 升级评估与自动化工具 - 轻松迁移 Functions 计划、托管层级和 SKU

azure-upgrade by microsoft/azure-skills

47,400 周安装量

509 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/microsoft/azure-skills --skill azure-upgrade

云服务开发运维

🇨🇳中文介绍

Azure 升级

此技能处理现有 Azure 工作负载从一个 Azure 服务、托管计划或 SKU 到另一个的评估和自动化升级——所有操作均在 Azure 内进行。这包括计划/层级升级（例如消耗量 → 弹性消耗量）、跨服务迁移（例如 App Service → 容器应用）和 SKU 变更。这不适用于跨云迁移——请使用 azure-cloud-migrate 来处理跨云迁移。

触发器

用户意图	示例提示
升级 Azure Functions 计划	"将我的函数应用从消耗量计划升级到弹性消耗量计划"
更改托管层级	"将我的函数应用迁移到更好的计划"
评估升级就绪情况	"我的函数应用是否已准备好升级到弹性消耗量计划？"
自动化计划迁移	"自动化升级 Functions 计划的步骤"

规则

按顺序遵循各个阶段——不得跳过
在执行任何升级操作之前生成评估报告
加载场景参考并遵循其规则
使用 mcp_azure_mcp_get_bestpractices 和 mcp_azure_mcp_documentation MCP 工具

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

相关 Skills

Vercel React 最佳实践指南 | 58条Next.js性能优化规则与代码重构

245,300 周安装

agent-browser 浏览器自动化工具 - Vercel Labs 命令行网页操作与测试

128,699 周安装

Azure Data Explorer (Kusto) 查询技能：KQL数据分析、日志遥测与时间序列处理

83,400 周安装

Azure 配额管理指南：服务限制、容量验证与配额增加方法

58,700 周安装

Next.js 最佳实践指南：文件约定、RSC边界、异步模式与性能优化

破坏性操作需要 ask_user —— 全局规则

在继续之前，始终与用户确认目标计划/SKU

未经用户明确确认，切勿删除或停止原始应用

所有自动化脚本必须是幂等的且可恢复的

源	目标	参考
Azure Functions 消耗量计划	Azure Functions 弹性消耗量计划	consumption-to-flex.md

没有匹配的场景？使用 mcp_azure_mcp_documentation 和 mcp_azure_mcp_get_bestpractices 工具来研究升级路径。

工具	用途
`mcp_azure_mcp_get_bestpractices`	获取目标服务的 Azure 最佳实践
`mcp_azure_mcp_documentation`	查找升级场景的 Azure 文档
`mcp_azure_mcp_appservice`	查询 App Service 和 Functions 计划详情
`mcp_azure_mcp_applicationinsights`	验证监控配置

识别 —— 确定源和目标 Azure 计划/SKU。请用户确认。
评估 —— 分析现有应用以评估升级就绪情况 → 加载场景参考（例如，consumption-to-flex.md）
预迁移 —— 从现有应用收集设置、身份、配置
升级 —— 执行自动化升级步骤（创建新资源、迁移设置、部署代码）
验证 —— 访问函数应用的默认 URL 以确认应用可访问，然后验证端点和监控
询问用户 —— "升级完成。您是否要验证性能、清理旧应用或更新您的 IaC？"
移交 —— 将任务移交给 azure-validate 进行深度验证，或移交给 azure-deploy 进行 CI/CD 设置

在工作区根目录的 upgrade-status.md 文件中跟踪进度。

升级验证后，移交至：

azure-validate —— 用于彻底的升级后验证
azure-deploy —— 如果用户想为新应用设置 CI/CD

🇺🇸English

Azure Upgrade

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.

Triggers

User Intent	Example 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"

Rules

Follow phases sequentially — do not skip
Generate an assessment before any upgrade operations
Load the scenario reference and follow its rules
Use mcp_azure_mcp_get_bestpractices and mcp_azure_mcp_documentation MCP tools
Destructive actions require ask_user — global-rules
Always confirm the target plan/SKU with the user before proceeding
Never delete or stop the original app without explicit user confirmation
All automation scripts must be idempotent and resumable

Upgrade Scenarios

Source	Target	Reference
Azure Functions Consumption Plan	Azure Functions Flex Consumption Plan	consumption-to-flex.md

No matching scenario? Use mcp_azure_mcp_documentation and mcp_azure_mcp_get_bestpractices tools to research the upgrade path.

MCP Tools

Tool	Purpose
`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

Steps

Identify — Determine the source and target Azure plans/SKUs. Ask user to confirm.
Assess — Analyze existing app for upgrade readiness → load scenario reference (e.g., consumption-to-flex.md)
Pre-migrate — Collect settings, identities, configs from the existing app
Upgrade — Execute the automated upgrade steps (create new resources, migrate settings, deploy code)
Validate — Hit the function app default URL to confirm the app is reachable, then verify endpoints and monitoring
Ask User — "Upgrade complete. Would you like to verify performance, clean up the old app, or update your IaC?"
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.

References

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

Weekly Installs

47.4K

Repository

microsoft/azure-skills

GitHub Stars

509

First Seen

12 days ago

Security Audits

Gen Agent Trust HubPass SocketPass SnykWarn

Installed on

github-copilot47.4K

gemini-cli139

codex139

opencode137

cursor136

kimi-cli134