microsoft/azure-skills · Official

azure-upgrade

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

All-time #103 Trending #192 First seen Mar 13, 2026
8-week activity · all time api

Installation

$ npx skills add microsoft/azure-skills --skill azure-upgrade

Summary

  • Assess and automate upgrades of Azure workloads across plans, tiers, and SKUs.
  • Handles plan migrations (Consumption to Flex Consumption), tier upgrades, and cross-service moves (App Service to Container Apps) with sequential assessment before any changes Generates pre-upgrade readiness reports, collects existing app settings and configurations, then executes automated upgrade steps with idempotent scripts Requires explicit user confirmation for destructive actions and target plan/SKU selection before proceeding Validates upgrades by testing app reachability and monitoring, then hands off to azure-validate or azure-deploy for deeper validation or CI/CD setup

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Security audits

Partner security reviews for this skill.

agent-trust-hub SAFE

Analyzed May 6, 2026

This skill provides a robust framework for assessing and automating Azure service upgrades and Java SDK modernization. It employs standard development tools, including the Azure CLI and OpenRewrite, and fetches configuration data from trusted official sources. The security considerations identified are consistent with its intended purpose of automated code refactoring and project management.

snyk MEDIUM

Analyzed May 6, 2026

[MEDIUM] W011: Third-party content exposure detected (indirect prompt injection risk). [MEDIUM] W012: Unverifiable external dependency detected (runtime URL that controls agent).

socket Score 0.9000 · 0 alerts

Analyzed May 6, 2026

  • license 1
  • maintenance 1
  • quality 0.9
  • supply chain 0.97
  • vulnerability 1

0 alerts

Also in this package

Other skills from microsoft/azure-skills · top by installs.

npx skills add microsoft/azure-skills

Browse all from microsoft/azure-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1.5K
License MIT
Default branch main
Open issues 9
Last push Sep 10, 2026
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.2.1
LicenseMIT
Compatibilitypython3.10+
More metadata
author
Microsoft
version
1.2.1

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 6,191 B
  • docs SUMMARY.md 433 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 429,500 installs

SKILL.md

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

  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 mcpazuremcpgetazurebestpractices and mcpazuremcpdocumentation 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

Source Target Reference
Azure Functions Consumption Plan Azure Functions Flex Consumption Plan [consumption-to-flex.md](references/services/functions/consumption-to-flex.md)
Legacy Azure Java SDK (com.microsoft.azure.*) Modern Azure Java SDK (com.azure.*) [languages/java/README.md](references/languages/java/README.md)
Azure Cache for Redis (ACR/OSS) Basic/Standard/Premium Azure Managed Redis (AMR) [services/redis/redis-to-amr.md](references/services/redis/redis-to-amr.md)
Azure Cache for Redis Enterprise (ACRE) / Enterprise Flash Azure Managed Redis (AMR) [services/redis/redis-to-amr.md](references/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 mcpazuremcpdocumentation and mcpazuremcpgetazurebestpractices tools to research the upgrade path.

MCP Tools

Tool Purpose
mcpazuremcpgetazure_bestpractices Get Azure best practices for the target service
mcpazuremcp_documentation Look up Azure documentation for upgrade scenarios
mcpazuremcp_appservice Query App Service and Functions plan details
mcpazuremcp_applicationinsights Verify 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](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/PLANTEMPLATE.md) - [Progress Template](references/languages/java/templates/PROGRESSTEMPLATE.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