Azure Upgrade
Assess and automate Azure plan, SKU, service, and legacy Java SDK upgrades.
The evidence shows target confirmation, ask_user gates for destructive actions, preservation of the original resource, rollback guidance, managed-identity preference, and MIT licensing. It does not define least-privilege RBAC, configuration/identity data flows, sensitive-data handling, dependency security, or execution isolation, so 7 points are deducted.
Phases, recovery of the original application, and idempotent/resumable automation are specified. However, several referenced files, MCP tools, and scripts are not fully supplied here; the Java flow branches from the top-level workflow; and there are no skill-specific tests or strong diagnostic failure outputs. The score is therefore constrained by static calibration and reduced further.
Triggers, supported Functions, Redis, and Java SDK scenarios are explicit, and cross-cloud migration is excluded. However, the scope spans substantially different workflows, non-fit boundaries and input/output contracts are incomplete, Chinese-language interaction and mainland-China reachability are unsubstantiated, and core operation depends on Azure MCP and external documentation.
The skill provides name, description, compatibility, author, version, license, triggers, scenario tables, and layered references. It lacks a clear changelog, explicit maintenance/update path, complete installation dependency notes, FAQs, limitation disclosure, and representative output examples, so points are deducted.
The material supports assessment, migration, validation, and handoff workflows and includes a detailed Java migration checklist. But output correctness, script success, service-migration behavior, and benefit over manual alternatives are not supported by in-file execution evidence; external dependencies and omitted references may require substantial rework. The score remains within the static effectiveness cap.
The files contain detailed rules, commands, validation gates, and repository-level CI/test signals. They do not provide committed tests or real execution evidence covering azure-upgrade key paths, and the external references were not independently corroborated in the supplied material, so only limited verifiability is awarded.
- Before execution, verify that every referenced file, MCP tool, script, and required permission actually exists, and obtain renewed confirmation for subscription, region, resource creation, and configuration overwrites.
- Do not treat repository-level CI or badges as validation of azure-upgrade; add dedicated tests and failure cases for the Functions, Redis, and Java branches.
- The Java flow requires autonomous migration but depends on external BOM and migration guides; if those sources are unreachable, it should stop with an explanation rather than guess versions.
- No mainland-China reachability or Chinese-output guarantee is provided; environments depending on Azure MCP, GitHub, and external documentation require separate assessment.
What does this skill do, and when should you use it?
Azure Upgrade is the azure-skills plugin skill for changing existing Azure workloads between plans, tiers, SKUs, or selected services. It covers Functions Consumption to Flex Consumption, App Service to Container Apps, Azure Cache for Redis or Enterprise Redis to Azure Managed Redis, and legacy Java Azure SDK modernization from com.microsoft.azure.* to com.azure.*. The workflow begins with an assessment, requires target confirmation, and proceeds through preparation, upgrade, and validation. It fits Azure-to-Azure modernization work, but not cross-cloud migration.
Identifies source and target Azure plans, tiers, or SKUs; assesses readiness and loads the relevant scenario reference; collects settings, identities, and configuration; creates new resources, migrates settings, and deploys code; checks the default function-app URL, endpoints, and monitoring; calls Azure best-practice, documentation, App Service/Functions, and Application Insights MCP tools; and tracks progress in upgrade-status.md at the workspace root.
- An Azure Functions developer wants to assess and move an app from Consumption to Flex Consumption.
- An operations team wants to migrate an existing App Service workload to Container Apps.
- A Redis team wants to assess migration from Azure Cache for Redis or Enterprise Redis to Azure Managed Redis.
- A Java maintainer needs to modernize legacy com.microsoft.azure.* dependencies and source code to com.azure.*.
- A platform team wants a staged Azure plan upgrade with explicit checks for configuration, identity, reachability, and monitoring.
What are this skill's strengths and limitations?
- Covers Azure Functions plan changes, App Service to Container Apps, Redis to Azure Managed Redis, and Java Azure SDK modernization.
- Defines a sequential workflow from assessment through validation and handoff.
- Requires idempotent, resumable automation and user confirmation for destructive actions.
- Provides MCP integrations for Azure documentation, best practices, App Service/Functions details, and Application Insights.
- Scope is limited to the documented Azure upgrade scenarios; unmatched scenarios require additional research.
- The provided SKILL.md does not include the detailed automation scripts or complete migration commands.
- It depends on Azure MCP tools, network access, and a Python 3.10+ environment; platform-specific test coverage is not documented.
- Cleanup of the original application remains an explicit user decision.
How do you install this skill?
Run npx skills add microsoft/skills in the project and select the required skill in the installation wizard. Alternatively, in Copilot CLI run /plugin marketplace add microsoft/skills, then /plugin install azure-skills@skills. The source does not document a command for installing only this skill directory.
How do you use this skill?
Use a focused request such as “Upgrade my function app from Consumption to Flex Consumption” or “Migrate my Redis cache to AMR.” The skill identifies the target and asks for confirmation, then follows assessment, pre-migration, upgrade, and validation phases. It must not skip the assessment or delete or stop the original app without explicit confirmation.
How does this skill compare with similar options?
Unlike azure-cloud-migrate, this skill handles upgrades within Azure—plans, tiers, SKUs, services, and Java SDK source modernization—rather than cross-cloud migration. After validation it can hand off to azure-validate for deeper checks or azure-deploy for CI/CD setup.