Localized reading guide

azure-upgradePurpose, usage and source

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

Source retrieved: 2026-10-29

Source repository: microsoft/skills
SKILL.md: .github/plugins/azure-skills/skills/azure-upgrade/SKILL.md
Repository stars: 3,157
Repository updated: 2026-10-31
Categories: Cloud
Last collected: 2026-10-31 10:38 UTC+08:00

License: License file needs review

Source SKILL.md

Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.

The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.

What this Skill does

How the upstream workflow works

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) Pre-migrate — Collect settings, identities, configs from the existing app Upgrade — Execute the automated upgrade steps (create new resources, migrate settings, deploy code)

Upstream passage · L67 ↗

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.

Upstream passage · L11 ↗

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

Upstream passage · L28 ↗

Requirements and setup

compatibility

python3.10+

Upstream passage · L1 ↗

Limits and quality checks

No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.

Start with a safe trial

Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.

Skill format and directory specification ↗

Read further in the source

Translation and scope

This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.

This introduction refers to the pinned version below; current repository activity and collection time are shown separately.

Pinned source: Read the original ↗
Source retrieved: 2026-10-29T09:32:23Z
Source commit: 00d66a64919edca5bca2c673373444e36a4b5461
Source SHA-256: 58ed42a87e5b5aee1cc07f970f05da8fd860037f8a0201ce7e68a88fbee79063

Back to the full Skill catalog