PluginBench
Skill
Official
Review
Audit score 70

azure-upgrade

microsoft/azure-skills

Assess and automate Azure workload upgrades between plans, tiers, SKUs, and modernize Azure SDK dependencies.

SourceView on skills.sh

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
Prerequisites
  • Python 3.10 or later
  • Access to Azure subscription and target Azure resources
  • For Java SDK modernization: Java project source code accessible
Claude Code
Cursor
Windsurf
Cline

How to use azure-upgrade

  1. 1.Identify the source and target Azure plan, tier, or SKU and confirm with the user
  2. 2.Run an assessment to analyze the existing app for upgrade readiness using the relevant scenario reference
  3. 3.Collect settings, identities, and configurations from the existing app
  4. 4.Execute the automated upgrade steps (create new resources, migrate settings, deploy code)
  5. 5.Validate the upgraded app by hitting the default URL and verifying endpoints and monitoring
  6. 6.Confirm upgrade completion with the user and offer next steps (performance verification, cleanup, IaC updates)

Use cases

Good for
  • 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
Who it's for
  • 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

What is the difference between azure-upgrade and azure-cloud-migrate?

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.

Do I need to stop my app during an upgrade?

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.

Can this skill migrate my app to a different cloud provider?

No. azure-upgrade only handles upgrades within Azure. For cross-cloud migration, use the azure-cloud-migrate skill.

What happens if the upgrade fails partway through?

All automation scripts are idempotent and resumable. The skill tracks progress in upgrade-status.md and can resume from the last completed step.

Does this skill handle Redis Enterprise (ACRE) to AMR migration?

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.* → modern com.azure.*). This is NOT for cross-cloud migration — use azure-cloud-migrate for that.

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

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

SourceTargetReference
Azure Functions Consumption PlanAzure Functions Flex Consumption Planconsumption-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/PremiumAzure Managed Redis (AMR)services/redis/redis-to-amr.md
Azure Cache for Redis Enterprise (ACRE) / Enterprise FlashAzure 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

ToolPurpose
mcp_azure_mcp_get_azure_bestpracticesGet Azure best practices for the target service
mcp_azure_mcp_documentationLook up Azure documentation for upgrade scenarios
mcp_azure_mcp_appserviceQuery App Service and Functions plan details
mcp_azure_mcp_applicationinsightsVerify monitoring configuration

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.

References

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