azure-upgrade
microsoft/azure-skills
Assess and automate Azure workload upgrades between plans, tiers, SKUs, and modernize Azure SDK dependencies.
What is azure-upgrade?
Handles assessment and automated upgrades of Azure workloads within Azure—plan/tier changes (Consumption to Flex Consumption), cross-service migrations (App Service to Container Apps), SKU changes, and Azure SDK for Java modernization (com.microsoft.azure to com.azure). Use this when upgrading Azure Functions plans, changing hosting tiers, migrating Redis caches, or modernizing legacy Java SDK dependencies.
- Assess upgrade readiness before executing plan or SKU changes
- Automate Azure Functions Consumption to Flex Consumption upgrades
- Migrate Azure Cache for Redis (ACR/ACRE) to Azure Managed Redis (AMR)
- Modernize legacy Azure Java SDK dependencies (com.microsoft.azure.* to com.azure.*)
- Collect and migrate settings, identities, and configs during upgrades
- Validate upgraded apps and confirm reachability post-migration
How to install azure-upgrade
npx skills add https://github.com/microsoft/azure-skills --skill azure-upgrade- Python 3.10 or later
- Access to Azure subscription and target Azure resources
- For Java SDK modernization: Java project source code accessible
How to use azure-upgrade
- 1.Identify the source and target Azure plan, tier, or SKU and confirm with the user
- 2.Run an assessment to analyze the existing app for upgrade readiness using the relevant scenario reference
- 3.Collect settings, identities, and configurations from the existing app
- 4.Execute the automated upgrade steps (create new resources, migrate settings, deploy code)
- 5.Validate the upgraded app by hitting the default URL and verifying endpoints and monitoring
- 6.Confirm upgrade completion with the user and offer next steps (performance verification, cleanup, IaC updates)
Use cases
- Upgrade an Azure Functions app from Consumption plan to Flex Consumption plan
- Migrate an Azure Cache for Redis Premium instance to Azure Managed Redis
- Modernize a Java project using legacy com.microsoft.azure SDKs to modern com.azure SDKs
- Assess whether an existing function app is ready for a plan upgrade
- Automate the full migration workflow for cross-service moves like App Service to Container Apps
- Azure platform engineers managing function app infrastructure
- Java developers maintaining legacy Azure SDK dependencies
- DevOps teams automating Azure service migrations
- Cloud architects planning Azure workload upgrades
azure-upgrade FAQ
azure-upgrade handles upgrades within Azure (plan/tier changes, SKU upgrades, SDK modernization). azure-cloud-migrate is for cross-cloud migrations. Use azure-upgrade for Consumption→Flex Consumption, ACR→AMR, or legacy Java SDK updates.
The skill follows a non-destructive workflow: it creates new resources, migrates settings, and validates before asking for confirmation to clean up the old app. You control when the original app is stopped.
No. azure-upgrade only handles upgrades within Azure. For cross-cloud migration, use the azure-cloud-migrate skill.
All automation scripts are idempotent and resumable. The skill tracks progress in upgrade-status.md and can resume from the last completed step.
Yes. The skill routes ACRE to AMR migrations to the dedicated acre-to-amr-migration-skill, and ACR/OSS to AMR migrations to the amr-migration-skill.
Full instructions (SKILL.md)
Source of truth, from microsoft/azure-skills.
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.2.1"
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.*→ moderncom.azure.*). This is NOT for cross-cloud migration — useazure-cloud-migratefor 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_bestpracticesandmcp_azure_mcp_documentationMCP 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_documentationandmcp_azure_mcp_get_azure_bestpracticestools 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-validatefor deep validation orazure-deployfor 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
Next
After upgrade is validated, hand off to:
azure-validate— for thorough post-upgrade validationazure-deploy— if the user wants to set up CI/CD for the new app
Related skills
More from microsoft/azure-skills and the wider catalog.
