Skills

Skill 42 of 53

Azure Upgrade

Assess and upgrade Azure workloads between plans, tiers, or SKUs, or modernize Azure SDK dependencies in source code.

4 minutes · 856 words · 7 sections

Install

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

$ npx skills add microsoft/azure-skills

» /plugin marketplace add microsoft/azure-skills

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

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”
Discover Functions upgrade candidates	“What Consumption Function Apps do I have that can be upgraded 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 in order. Skip or defer work only when the selected scenario explicitly permits it, and record the reason in the migration status.
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 (opens in a new tab)
Always confirm the target plan/SKU with the user before proceeding
Propose a name for any new resource (default: <source>-<target-suffix>, e.g. <source>-flex for Flex Consumption migrations) and announce the proposed name to the user before creating it so they can override without a blocking prompt. Same pattern applies to other newly-created resources (storage accounts, App Insights, etc.) — see the scenario reference for service-specific defaults.
Windows Consumption → Flex source-change gate: treat the source app as read-only by default. Immediately before every command that would change its settings, triggers, state, deployment, bindings, or existence, use ask_user to describe the exact change and obtain explicit approval. Approval is action-specific and cannot be reused for later source changes.
Never delete or stop the original app without explicit user confirmation
Keep approval-gated workflows moving: after each completed step, immediately perform the next read-only preflight. If the next action requires approval, invoke ask_user in the same turn — never stop after merely announcing the next step and wait for the user to re-engage.
All automation scripts must be idempotent and resumable

Upgrade Scenarios

Source	Target	Reference
Azure Functions Consumption Plan (Linux)	Azure Functions Flex Consumption Plan	workflow.md (opens in a new tab)
Azure Functions Consumption Plan (Windows)	Azure Functions Flex Consumption Plan	workflow.md (opens in a new tab)
Legacy Azure Java SDK (`com.microsoft.azure.*`)	Modern Azure Java SDK (`com.azure.*`)	languages/java/README.md (opens in a new tab)
Azure Cache for Redis (ACR/OSS) Basic/Standard/Premium	Azure Managed Redis (AMR)	services/redis/redis-to-amr.md (opens in a new tab)
Azure Cache for Redis Enterprise (ACRE) / Enterprise Flash	Azure Managed Redis (AMR)	services/redis/redis-to-amr.md (opens in a new tab)

Functions Consumption-to-Flex routing: For a named app, inspect its Azure platform and load only the matching Linux or Windows workflow. For subscription-wide discovery, evaluate both platforms: use az functionapp flex-migration list for Linux and the Windows workflow’s manual discovery and compatibility checks for Windows. Label Windows results as candidates until per-app code compatibility is assessed.

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., workflow.md (opens in a new tab))
Pre-migrate — Collect settings, identities, configs from the existing app
Upgrade — Execute the automated upgrade steps (create new resources, migrate settings, deploy code)
Validate — Use the checks defined by the selected scenario: verify target resource state, applicable HTTP endpoints and non-HTTP triggers, and monitoring. If access restrictions or unavailable test resources prevent execution, record validation as deferred — never relax security automatically or report functional success.
Ask User — Offer performance validation and IaC updates. Offer source cleanup only when the selected scenario confirms production cutover and all cleanup prerequisites are complete.
Hand off to azure-validate for deep validation or azure-deploy for CI/CD setup

Track progress in <UPGRADE_DIR>/upgrade-status.md — see Artifact Output Policy (opens in a new tab) for path resolution.

References

Global Rules (opens in a new tab)
Workflow Details (opens in a new tab)
Functions
- Linux
- Windows
Redis
- Redis (ACR or ACRE) to AMR Migration (opens in a new tab) — routes to dedicated amr-migration-skill (opens in a new tab) (ACR/OSS) or acre-to-amr-migration-skill (opens in a new tab) (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

About this skill

Trigger

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

The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Compatibility: python3.10+
Licence: MIT
Also published for: GitHub — collapsed into this chapter because the copies are the same skill.
Source: skills/azure-upgrade/SKILL.md

Colophon for this issue

Colophon

How this issue was made

Source

github.com/microsoft/azure-skills, branch main, last pushed 6 November 2026.

Licence

MIT — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

53 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 11 distinct layouts observed: .github/plugins/aks-skills/skills/*/SKILL.md, .github/plugins/azure-advisor/skills/*/SKILL.md, .github/plugins/azure-cost/skills/*/SKILL.md, .github/plugins/azure-kusto-graph-skills/skills/*/SKILL.md, .github/plugins/azure-local-skills/skills/*/SKILL.md, .github/plugins/foundry-iq-skills/skills/*/SKILL.md, skills/*/SKILL.md, skills/azure-kubernetes/*/SKILL.md, skills/microsoft-foundry/*/SKILL.md, skills/microsoft-foundry/models/deploy-model/*/SKILL.md, skills/microsoft-foundry/models/*/SKILL.md.

Duplicates collapsed

35 mirror copies folded into their canonical skill — republished for GitHub. Copies match on content hash and on position once a leading per-agent prefix is stripped, because the same skill is routinely shipped under a dozen agent directories with a dozen different hashes.

Issue colours

Resolved from a curated brand profile — hue 251°, chroma 0.167. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Removed “Azure Upgrade”, a leading h1 that duplicated the skill title.

Spec compliance

Every skill satisfies the Agent Skills specification’s frontmatter rules.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .claude-plugin/marketplace.json by Microsoft, declaring 7 plugins. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /microsoft/azure-skills.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

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”
Discover Functions upgrade candidates	“What Consumption Function Apps do I have that can be upgraded 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 in order. Skip or defer work only when the selected scenario explicitly permits it, and record the reason in the migration status.
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 (opens in a new tab)
Always confirm the target plan/SKU with the user before proceeding
Propose a name for any new resource (default: <source>-<target-suffix>, e.g. <source>-flex for Flex Consumption migrations) and announce the proposed name to the user before creating it so they can override without a blocking prompt. Same pattern applies to other newly-created resources (storage accounts, App Insights, etc.) — see the scenario reference for service-specific defaults.
Windows Consumption → Flex source-change gate: treat the source app as read-only by default. Immediately before every command that would change its settings, triggers, state, deployment, bindings, or existence, use ask_user to describe the exact change and obtain explicit approval. Approval is action-specific and cannot be reused for later source changes.
Never delete or stop the original app without explicit user confirmation
Keep approval-gated workflows moving: after each completed step, immediately perform the next read-only preflight. If the next action requires approval, invoke ask_user in the same turn — never stop after merely announcing the next step and wait for the user to re-engage.
All automation scripts must be idempotent and resumable

Upgrade Scenarios

Source	Target	Reference
Azure Functions Consumption Plan (Linux)	Azure Functions Flex Consumption Plan	workflow.md (opens in a new tab)
Azure Functions Consumption Plan (Windows)	Azure Functions Flex Consumption Plan	workflow.md (opens in a new tab)
Legacy Azure Java SDK (`com.microsoft.azure.*`)	Modern Azure Java SDK (`com.azure.*`)	languages/java/README.md (opens in a new tab)
Azure Cache for Redis (ACR/OSS) Basic/Standard/Premium	Azure Managed Redis (AMR)	services/redis/redis-to-amr.md (opens in a new tab)
Azure Cache for Redis Enterprise (ACRE) / Enterprise Flash	Azure Managed Redis (AMR)	services/redis/redis-to-amr.md (opens in a new tab)

Functions Consumption-to-Flex routing: For a named app, inspect its Azure platform and load only the matching Linux or Windows workflow. For subscription-wide discovery, evaluate both platforms: use az functionapp flex-migration list for Linux and the Windows workflow’s manual discovery and compatibility checks for Windows. Label Windows results as candidates until per-app code compatibility is assessed.

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., workflow.md (opens in a new tab))
Pre-migrate — Collect settings, identities, configs from the existing app
Upgrade — Execute the automated upgrade steps (create new resources, migrate settings, deploy code)
Validate — Use the checks defined by the selected scenario: verify target resource state, applicable HTTP endpoints and non-HTTP triggers, and monitoring. If access restrictions or unavailable test resources prevent execution, record validation as deferred — never relax security automatically or report functional success.
Ask User — Offer performance validation and IaC updates. Offer source cleanup only when the selected scenario confirms production cutover and all cleanup prerequisites are complete.
Hand off to azure-validate for deep validation or azure-deploy for CI/CD setup

Track progress in <UPGRADE_DIR>/upgrade-status.md — see Artifact Output Policy (opens in a new tab) for path resolution.

References

Global Rules (opens in a new tab)
Workflow Details (opens in a new tab)
Functions
- Linux
- Windows
Redis
- Redis (ACR or ACRE) to AMR Migration (opens in a new tab) — routes to dedicated amr-migration-skill (opens in a new tab) (ACR/OSS) or acre-to-amr-migration-skill (opens in a new tab) (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

Triggers

Rules

Upgrade Scenarios

MCP Tools

Steps

References

Next

About this skill

Trigger

Colophon

Azure Upgrade

Triggers

Rules

Upgrade Scenarios

MCP Tools

Steps

References

Next

Appendix 42.1–42.49

References49 files

About this skill

Trigger

Colophon

Appendix 42.1–42.49

References49 files