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

Source: https://skillsagentes.com/skills/microsoft/azure-skills/azure-upgrade
Repository: https://github.com/microsoft/azure-skills
Author: microsoft
License: MIT
Updated: hace 17 días
Context cost: 103 tok installed, 1.5k tok once triggered, 41.6k tok with every bundled file
Bundle: 31 files, 162 KB
Permissions requested: none declared

## Install

```bash
npx -y skills add microsoft/azure-skills --skill azure-upgrade --agent claude-code
```

## What it does

- Evalúa y ejecuta actualizaciones de cargas de trabajo **dentro** de Azure: entre planes, tiers y SKUs, y entre servicios.
- Cubre Functions de Consumption a Flex Consumption, App Service a Container Apps, y cambios de SKU.
- Moderniza dependencias del SDK de Azure en el código fuente Java, de `com.microsoft.azure.*` al moderno `com.azure.*`.
- Migra Azure Cache for Redis y Redis Enterprise a Azure Managed Redis, incluida la conversión de plantillas de IaC.

## Use it when

- Se quiere subir el plan de un Function App, cambiar de tier o de SKU.
- Se quiere modernizar SDKs legados de Azure para Java.
- Se quiere migrar de ACR/ACRE a Azure Managed Redis.

## Don't bother when

- Para migración entre nubes distintas: el archivo remite a `azure-cloud-migrate`.

## What triggers it

- "sube mi function app a Flex Consumption"
- "migra de App Service a Container Apps"
- "moderniza estos SDK de Java"
- "pasa mi Redis a AMR"

## Before you install

- El frontmatter declara compatibilidad con python3.10 o superior.

## Files

- SKILL.md — 6 KB
- references/global-rules.md — 2 KB
- references/languages/java/INSTRUCTION.md — 11 KB
- references/languages/java/README.md — 3 KB
- references/languages/java/bom-migration/bom-gradle-settings.md — 7 KB
- references/languages/java/bom-migration/bom-gradle-toml.md — 3 KB
- references/languages/java/bom-migration/bom-gradle.md — 5 KB
- references/languages/java/bom-migration/bom-maven.md — 5 KB
- references/languages/java/bom-migration/bom-migration.md — 4 KB
- references/languages/java/bom-migration/bom-validation.md — 2 KB
- references/languages/java/package-specific/com.microsoft.azure.eventprocessorhost.md — 6 KB
- references/languages/java/package-specific/com.microsoft.azure.management.md — 9 KB
- references/languages/java/rules/efficiency.md — 265 B
- references/languages/java/rules/execution-guidelines.md — 1 KB
- references/languages/java/rules/review-code-changes.md — 541 B
- references/languages/java/rules/troubleshooting.md — 3 KB
- references/languages/java/rules/upgrade-strategy.md — 1 KB
- references/languages/java/rules/upgrade-success-criteria.md — 686 B
- references/languages/java/scripts/upgrade_bom.py — 20 KB
- references/languages/java/templates/PLAN_TEMPLATE.md — 9 KB
- references/languages/java/templates/PROGRESS_TEMPLATE.md — 9 KB
- references/languages/java/templates/SUMMARY_TEMPLATE.md — 9 KB
- references/languages/java/workflow/phase-1-precheck.md — 2 KB
- references/languages/java/workflow/phase-2-plan.md — 3 KB
- references/languages/java/workflow/phase-3-execute.md — 2 KB
- references/languages/java/workflow/phase-4-summarize.md — 1 KB
- references/services/functions/assessment.md — 4 KB
- references/services/functions/automation.md — 14 KB
- references/services/functions/consumption-to-flex.md — 11 KB
- references/services/redis/redis-to-amr.md — 8 KB
- references/workflow-details.md — 2 KB

## SKILL.md

Reproduced verbatim from microsoft/azure-skills under MIT. This section is the upstream document and is in English.

# 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 `mcp_azure_mcp_get_azure_bestpractices` and `mcp_azure_mcp_documentation` 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 `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

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](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)
- **Java SDK Migration Templates**
  - [Plan Template](references/languages/java/templates/PLAN_TEMPLATE.md)
  - [Progress Template](references/languages/java/templates/PROGRESS_TEMPLATE.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

---

Skills Agentes — https://skillsagentes.com/skills/microsoft/azure-skills/azure-upgrade