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

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_azure_bestpractices and mcp_azure_mcp_documentation MCP tools
5. Destructive actions require ask_user — [global-rules](references/global-rules.md)
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

Upgrade Scenarios

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

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](references/services/functions/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.

References

• [Global Rules](references/global-rules.md)
• [Workflow Details](references/workflow-details.md)
• Functions
• [Consumption to Flex Consumption](references/services/functions/consumption-to-flex.md)
• [Assessment](references/services/functions/assessment.md)
• [Automation Scripts](references/services/functions/automation.md)
• Redis
• [Redis (ACR or ACRE) to AMR Migration](references/services/redis/redis-to-amr.md) — routes to dedicated amr-migration-skill (ACR/OSS) or acre-to-amr-migration-skill (Enterprise)
• Java SDK Migration Templates
• [Plan Template](references/languages/java/templates/PLAN_TEMPLATE.md)
• [Progress Template](references/languages/java/templates/PROGRESS_TEMPLATE.md)
• [Summary Template](references/languages/java/templates/SUMMARY_TEMPLATE.md)

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