All skills
microsoft avatar

/azure-upgrade

@b3c238e
by microsoftmicrosoft/skills3.1k stars
351

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

Use this Skill: https://skilld.dev/gh/microsoft/skills/azure-upgrade

This session only. Nothing lands on disk.

referenceslanguagesjavaworkflowphase-3-execute.md

≈609 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Phase 3: Execute Upgrade Plan

Load this file when executing Phase 3. Refer back to upgrade-success-criteria and upgrade-strategy for success criteria and strategy, and ../rules/troubleshooting.md when failures occur.

1. Initialize

  1. Read plan.md for step details
  2. Update progress.md:
    • Replace <RUN_ID>, <PROJECT_NAME> and timestamp placeholders
    • Create step entries for each step in plan.md (per Template compliance rule)

2. Execute

For each step:

  1. Read plan.md for step details and guidelines
  2. Mark ⏳ in progress.md
  3. Make changes as planned (use OpenRewrite if helpful, verify results)
    • Add TODOs for any deferred work, e.g., temporary workarounds
  4. Review Code Changes (per rules in Progress Template): Verify sufficiency (all required changes present) and necessity (no unnecessary changes, functional behavior preserved, security controls maintained).
    • Add missing changes and revert unnecessary changes. Document any unavoidable behavior changes with justification.
  5. Verify with specified command/JDK:
    • Steps 1-N (Setup/Upgrade): Compilation must pass (including both main and test code, fix immediately if not). Test failures acceptable — document count.
    • Final Validation Step: Achieve Upgrade Success Criteria — iterative test & fix loop until 100% pass (or ≥ baseline). NO deferring. See ../rules/troubleshooting.md when stuck.
    • Build: mvn clean test-compile (or ./gradlew compileTestJava for Gradle)
    • Test: mvn clean test (or ./gradlew test for Gradle)
  6. Commit on the java-upgrade/{RUN_ID} branch with message format (if git available; otherwise, log details in progress.md):
    • First line: Step <x>: <title> - Compile: <result> or Step <x>: <title> - Compile: <result>, Tests: <pass>/<total> passed (if tests run)
    • Body: Changes summary + concise known issues/limitations (≤5 lines)
    • Security note: If any security-related changes were made, include "Security: <change description and justification>"
  7. Update progress.md with step details and mark ✅ or ❗

3. Complete

  1. Validate all steps in plan.md have ✅ in progress.md
  2. Validate all Upgrade Success Criteria are met, or otherwise go back to Final Validation step to fix

Source: SKILL.md on GitHub

No alerts15d3 checks · Risk SAFE
  • Gen Agent Trust Hub15d

    This skill provides a structured framework for Azure workload upgrades and Java SDK modernization. It incorporates several security-focused practices, such as mandatory reviews to ensure the preservation of authentication and authorization controls during code migration. The skill utilizes standard development tools and follows official Microsoft guidance for Azure resource management.

  • Socket15d

    No alerts

  • Snyk15d

    Risk: LOW · No issues

Signed by skilld at b3c238e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 2 months ago
compatibility
python3.10+
metadata
{
  "author": "Microsoft",
  "version": "1.2.1"
}

README badge

README badge for microsoft/skills/azure-upgrade