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.
When to invoke
| 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
- Follow phases sequentially — do not skip
- 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
- Always confirm the target plan/SKU with the user before proceeding
- Never delete or stop the original app without explicit user confirmation
- 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 |
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/Premium |
Azure Managed Redis (AMR) |
services/redis/redis-to-amr.md |
| Azure Cache for Redis Enterprise (ACRE) / Enterprise Flash |
Azure 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
| 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., consumption-to-flex.md)
- Pre-migrate — Collect settings, identities, configs from the existing app
- Upgrade — Execute the automated upgrade steps (create new resources, migrate settings, deploy code)
- Validate — Hit the function app default URL to confirm the app is reachable, then verify endpoints and monitoring
- Ask User — "Upgrade complete. Would you like to verify performance, clean up the old app, or update your IaC?"
- 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
- Workflow Details
- Functions
- Consumption to Flex Consumption
- Assessment
- Automation Scripts
- Redis
- Java SDK Migration Templates
- Plan Template
- Progress Template
- Summary Template
Next
After upgrade is validated, hand off to:
azure-validate — for thorough post-upgrade validationazure-deploy — if the user wants to set up CI/CD for the new app
Output template
## Upgrade result
**Status:** assessed | upgraded | blocked
**Summary:** <one sentence covering scope and outcome>
### Details
Current and target plan, tier, SKU, or SDK, plus breaking changes.
### Validation
- <check performed>: <result and evidence>
Quality gate
1---2name: azure-upgrade-33description: Assess and upgrade Azure workloads between plans, tiers, or SKUs, and modernize Azure SDK dependencies in source code. Use when the user wants to upgrade Consumption to Flex Consumption, change an Azure Functions hosting plan or function app SKU, migrate App Service to Container Apps, modernize legacy Azure Java SDKs from com.microsoft.azure to com.azure, or migrate Azure Cache for Redis to Azure Managed Redis.4license: MIT5---67<!-- Generated from harness/github-copilot/plugins/azure-modernization/skills/azure-upgrade/SKILL.md by harness/claude-code/scripts/convert_from_copilot.py. Edit the source, not this file. -->89# Azure Upgrade1011> 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.1213## When to invoke1415| User Intent | Example Prompts |16|-------------|-----------------|17| Upgrade Azure Functions plan | "Upgrade my function app from Consumption to Flex Consumption" |18| Change hosting tier | "Move my function app to a better plan" |19| Assess upgrade readiness | "Is my function app ready for Flex Consumption?" |20| Automate plan migration | "Automate the steps to upgrade my Functions plan" |21| 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" |22| 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" |23| 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" |2425## Rules26271. Follow phases sequentially — do not skip282. Generate an assessment before any upgrade operations293. Load the scenario reference and follow its rules304. Use `mcp_azure_mcp_get_azure_bestpractices` and `mcp_azure_mcp_documentation` MCP tools315. Destructive actions require `ask_user` — [global-rules](references/global-rules.md)326. Always confirm the target plan/SKU with the user before proceeding337. Never delete or stop the original app without explicit user confirmation348. All automation scripts must be idempotent and resumable3536## Upgrade Scenarios3738| Source | Target | Reference |39|--------|--------|-----------|40| Azure Functions Consumption Plan | Azure Functions Flex Consumption Plan | [consumption-to-flex.md](references/services/functions/consumption-to-flex.md) |41| Legacy Azure Java SDK (`com.microsoft.azure.*`) | Modern Azure Java SDK (`com.azure.*`) | [languages/java/README.md](references/languages/java/README.md) |42| 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) |43| 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) |4445> 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.4647> No matching scenario? Use `mcp_azure_mcp_documentation` and `mcp_azure_mcp_get_azure_bestpractices` tools to research the upgrade path.4849## MCP Tools5051| Tool | Purpose |52|------|---------|53| `mcp_azure_mcp_get_azure_bestpractices` | Get Azure best practices for the target service |54| `mcp_azure_mcp_documentation` | Look up Azure documentation for upgrade scenarios |55| `mcp_azure_mcp_appservice` | Query App Service and Functions plan details |56| `mcp_azure_mcp_applicationinsights` | Verify monitoring configuration |5758## Steps59601. **Identify** — Determine the source and target Azure plans/SKUs. Ask user to confirm.612. **Assess** — Analyze existing app for upgrade readiness → load scenario reference (e.g., [consumption-to-flex.md](references/services/functions/consumption-to-flex.md))623. **Pre-migrate** — Collect settings, identities, configs from the existing app634. **Upgrade** — Execute the automated upgrade steps (create new resources, migrate settings, deploy code)645. **Validate** — Hit the function app default URL to confirm the app is reachable, then verify endpoints and monitoring656. **Ask User** — "Upgrade complete. Would you like to verify performance, clean up the old app, or update your IaC?"667. **Hand off** to `azure-validate` for deep validation or `azure-deploy` for CI/CD setup6768Track progress in `upgrade-status.md` inside the workspace root.6970## References7172- [Global Rules](references/global-rules.md)73- [Workflow Details](references/workflow-details.md)74- **Functions**75 - [Consumption to Flex Consumption](references/services/functions/consumption-to-flex.md)76 - [Assessment](references/services/functions/assessment.md)77 - [Automation Scripts](references/services/functions/automation.md)78- **Redis**79 - [Redis (ACR or ACRE) to AMR Migration](references/services/redis/redis-to-amr.md) — routes to dedicated [amr-migration-skill](https://github.com/AzureManagedRedis/amr-migration-skill) (ACR/OSS) or [acre-to-amr-migration-skill](https://github.com/AzureManagedRedis/acre-to-amr-migration-skill) (Enterprise)80- **Java SDK Migration Templates**81 - [Plan Template](references/languages/java/templates/PLAN_TEMPLATE.md)82 - [Progress Template](references/languages/java/templates/PROGRESS_TEMPLATE.md)83 - [Summary Template](references/languages/java/templates/SUMMARY_TEMPLATE.md)8485## Next8687After upgrade is validated, hand off to:88- `azure-validate` — for thorough post-upgrade validation89- `azure-deploy` — if the user wants to set up CI/CD for the new app9091## Output template9293```markdown94## Upgrade result9596**Status:** assessed | upgraded | blocked97**Summary:** <one sentence covering scope and outcome>9899### Details100Current and target plan, tier, SKU, or SDK, plus breaking changes.101102### Validation103- <check performed>: <result and evidence>104```105106## Quality gate107108- [ ] Breaking changes were enumerated before the upgrade.109- [ ] A rollback or fallback path is stated.110- [ ] The output follows `## Output template` exactly.111- [ ] Every reported check was performed and its evidence is shown.112- [ ] Irreversible Azure actions were confirmed with the user first.
paulasilvatech