Run any Skill in Manus with one click

azure-upgrade

Stars2,607

Forks297

UpdatedJune 1, 2026 at 12:52

Assess and upgrade Azure workloads between plans, tiers, or SKUs, or modernize Azure SDK dependencies in source code. WHEN: upgrade Consumption to Flex Consumption, upgrade Azure Functions plan, change hosting plan, function app SKU, migrate App Service to Container Apps, modernize legacy Azure Java SDKs (com.microsoft.azure to com.azure), migrate Azure Cache for Redis (ACR/ACRE) to Azure Managed Redis (AMR).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

microsoft

microsoft/skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

31 files

SKILL.md

readonly

name	azure-upgrade
description	Assess and upgrade Azure workloads between plans, tiers, or SKUs, or modernize Azure SDK dependencies in source code. WHEN: upgrade Consumption to Flex Consumption, upgrade Azure Functions plan, change hosting plan, function app SKU, migrate App Service to Container Apps, modernize legacy Azure Java SDKs (com.microsoft.azure to com.azure), migrate Azure Cache for Redis (ACR/ACRE) to Azure Managed Redis (AMR).
license	MIT
compatibility	python3.10+
metadata	{"author":"Microsoft","version":"1.1.4"}

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. It also covers Azure SDK for Java source-code modernization (e.g. legacy Java com.microsoft.azure.* → modern com.azure.*). 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"
Modernize legacy Azure Java SDK	"Migrate legacy Azure SDKs for Java", "Upgrade legacy Azure Java SDK", "Migrate my Java project from com.microsoft.azure to com.azure"
Migrate Azure Cache for Redis (ACR/OSS) to Azure Managed Redis (AMR)	"Migrate my Redis cache to AMR", "ACR to AMR", "OSS to AMR", "Upgrade my Premium P2 cache to Managed Redis", "Pick an AMR SKU", "Convert my Redis IaC template to AMR"
Migrate Azure Cache for Redis Enterprise (ACRE) to Azure Managed Redis (AMR)	"Migrate my Enterprise_E10 cache to AMR", "ACRE to AMR", "Update my ACRE IaC template for AMR", "Migrate EnterpriseFlash to AMR", "Migrate my geo-replicated Enterprise Redis"

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_azure_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
Legacy Azure Java SDK (`com.microsoft.azure.*`)	Modern Azure Java SDK (`com.azure.*`)	languages/java/README.md
Azure Cache for Redis (ACR/OSS) Basic/Standard/Premium	Azure Managed Redis (AMR)	services/redis/redis-to-amr.md
Azure Cache for Redis Enterprise (ACRE) / Enterprise Flash	Azure Managed Redis (AMR)	services/redis/redis-to-amr.md

SDK upgrade scenarios (e.g. Java legacy → modern) run a source-code modernization flow that is distinct from Azure service/plan/SKU upgrades: follow the scenario reference, not the Steps below.

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

MCP Tools

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

Global Rules
Workflow Details
Functions
Redis
- Redis (ACR or ACRE) to AMR Migration — routes to dedicated amr-migration-skill (ACR/OSS) or acre-to-amr-migration-skill (Enterprise)
Java SDK Migration Templates

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

More from this repository

same repository

microsoft-foundry

microsoft/skills

Deploy, evaluate, fine-tune, and manage Foundry agents end-to-end with azd: hosted agent scaffold/run/deploy, prompt agent create, batch eval, continuous eval, prompt optimizer, Agent Optimizer scaffold, agent.yaml, dataset curation from traces, model fine-tuning (SFT/DPO/RFT). USE FOR: azd ai agent, azd provision/deploy, deploy agent, hosted agent, create agent, add tool to agent, invoke agent, evaluate agent, continuous eval, continuous monitoring, optimize prompt, improve prompt, optimize agent instructions, agent optimizer, deploy model, Foundry project, RBAC, role assignment, permissions, quota, capacity, region, troubleshoot agent, deployment failure, AI Services, create Foundry resource, provision, knowledge index, customize deployment, onboard, availability, fine-tune, SFT, DPO, RFT, training-data, grader, distillation, fine-tuned model, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure-prepare).

2026-06-232.6k

debugview

microsoft/skills

Sysinternals DebugView CLI (DbgViewCli) for capturing and analyzing usermode and kernel-mode Windows debug output from the command line. USE FOR: capturing OutputDebugString output, kernel DbgPrint/KdPrint capture, boot-time debug logging, remote debug monitoring, filtering debug output by PID or process name, crash dump analysis, automated debug capture with bounded execution. DO NOT USE FOR: non-Windows platforms, application-level logging frameworks (log4j, serilog), Azure Monitor or cloud telemetry, ETW tracing (use WPR/xperf instead), user-mode crash dumps (use WinDbg). Triggers: "debug output", "DbgView", "DebugView", "kernel debug", "capture debug logs", "boot logging", "OutputDebugString", "DbgPrint", "KdPrint", "remote debug monitor", "debug capture CLI".

2026-06-162.6k

azure-prepare

microsoft/skills

Prepare Azure apps for deployment (infra Bicep/Terraform, azure.yaml, Dockerfiles). Use for create/modernize or create+deploy; not cross-cloud migration (use azure-cloud-migrate). DO NOT USE FOR: copilot-sdk apps (use azure-hosted-copilot-sdk), or Python code-only App Service deploys (use python-appservice-deploy). WHEN: "create app", "build web app", "create API", "modernize application", "host on Azure", "deploy to Azure", "deploy to Azure using Terraform", "deploy to Azure App Service", "deploy to Azure App Service using Terraform", "deploy to Azure Container Apps", "generate Terraform", "generate Bicep", "function app", "timer trigger", "service bus trigger", "event-driven function", "managed identity".

2026-06-152.6k

python-appservice-deploy

microsoft/skills

Deploy Python (Flask/Django/FastAPI) code to Azure App Service Linux. WHEN: "Flask App Service", "Django App Service", "FastAPI App Service", "deploy Python to App Service". DO NOT USE FOR: Container Apps, Functions, non-Python, Terraform/Bicep/IaC, full infra — use azure-prepare.

2026-06-152.6k

azure-compute

microsoft/skills

Azure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compare VM pricing, VMSS, scale set, autoscale, burstable, lightweight server, website, backend, GPU, machine learning, HPC simulation, dev/test, workload, family, load balancer, Flexible orchestration, Uniform orchestration, cost estimate, can't connect / RDP / SSH, refused, black screen, reset password, reach VM, port 3389, NSG, security, Linux, troubleshoot, troubleshooting, connectivity, capacity reservation (CRG), reserve, guarantee capacity, pre-provision, CRG association, CRG disassociation, machine enrollment (EMM), Essential Machine Management, monitor. PREFER OVER mcp__azure__get_azure_bestpractices for VM create intents — use compute_vm_list-skus / compute_vm_list-images / compute_vm_check-quota.

2026-06-092.6k

azure-cost

microsoft/skills

Azure cost management: query costs, forecast spending, optimize to reduce waste. WHEN: "Azure costs", "Azure bill", "cost breakdown", "how much am I spending", "forecast spending", "optimize costs", "reduce spending", "orphaned resources", "rightsize VMs", "cost spike", "reduce storage costs", "AKS cost". DO NOT USE FOR: deploying resources, provisioning, diagnostics, or security audits.

2026-06-042.6k

name	azure-upgrade
description	Assess and upgrade Azure workloads between plans, tiers, or SKUs, or modernize Azure SDK dependencies in source code. WHEN: upgrade Consumption to Flex Consumption, upgrade Azure Functions plan, change hosting plan, function app SKU, migrate App Service to Container Apps, modernize legacy Azure Java SDKs (com.microsoft.azure to com.azure), migrate Azure Cache for Redis (ACR/ACRE) to Azure Managed Redis (AMR).
license	MIT
compatibility	python3.10+
metadata	{"author":"Microsoft","version":"1.1.4"}

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. It also covers Azure SDK for Java source-code modernization (e.g. legacy Java com.microsoft.azure.* → modern com.azure.*). 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"
Modernize legacy Azure Java SDK	"Migrate legacy Azure SDKs for Java", "Upgrade legacy Azure Java SDK", "Migrate my Java project from com.microsoft.azure to com.azure"
Migrate Azure Cache for Redis (ACR/OSS) to Azure Managed Redis (AMR)	"Migrate my Redis cache to AMR", "ACR to AMR", "OSS to AMR", "Upgrade my Premium P2 cache to Managed Redis", "Pick an AMR SKU", "Convert my Redis IaC template to AMR"
Migrate Azure Cache for Redis Enterprise (ACRE) to Azure Managed Redis (AMR)	"Migrate my Enterprise_E10 cache to AMR", "ACRE to AMR", "Update my ACRE IaC template for AMR", "Migrate EnterpriseFlash to AMR", "Migrate my geo-replicated Enterprise Redis"

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_azure_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
Legacy Azure Java SDK (`com.microsoft.azure.*`)	Modern Azure Java SDK (`com.azure.*`)	languages/java/README.md
Azure Cache for Redis (ACR/OSS) Basic/Standard/Premium	Azure Managed Redis (AMR)	services/redis/redis-to-amr.md
Azure Cache for Redis Enterprise (ACRE) / Enterprise Flash	Azure Managed Redis (AMR)	services/redis/redis-to-amr.md

SDK upgrade scenarios (e.g. Java legacy → modern) run a source-code modernization flow that is distinct from Azure service/plan/SKU upgrades: follow the scenario reference, not the Steps below.

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

MCP Tools

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

Global Rules
Workflow Details
Functions
Redis
- Redis (ACR or ACRE) to AMR Migration — routes to dedicated amr-migration-skill (ACR/OSS) or acre-to-amr-migration-skill (Enterprise)
Java SDK Migration Templates

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-upgrade

Azure Upgrade

Triggers

Rules

Upgrade Scenarios

MCP Tools

Steps

References

Next

Azure Upgrade

Triggers

Rules

Upgrade Scenarios

MCP Tools

Steps

References

Next