AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

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

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-upgrade at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 49

references/languages/java/workflow/phase-1-precheck.md

Phase 1: Precheck

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

| Category | Scenario | Action | | ------------------- | -------------------------------- | ------------------------------------------------------ | | Unsupported Project | Not a Maven/Gradle project | STOP with error | | Unsupported Project | Git not installed or not managed | Log warning, continue without git | | Invalid Goal | No legacy Azure SDK deps found | STOP — nothing to migrate | | Java Version | Below JDK 8 | Include Java upgrade as part of the migration plan |

Prerequisites: JDK 8+ and Maven or Gradle must be pre-installed.

Environment detection:

Detect available JDKs:

  1. Check JAVA_HOME and JDK_HOME environment variables
  2. Run java -version and javac -version to detect the default JDK
  3. Search common JDK installation paths (platform-specific: Program Files on Windows, /usr/lib/jvm on Linux, /Library/Java on macOS)
  4. Check for version manager installations (SDKMAN, ASDF, jenv, Jabba)
  5. For each found JDK, read the release file to determine the version

Report all found JDKs with their path, version, and discovery source.

Detect build tools:

  1. Check for Maven Wrapper (mvnw/mvnw.cmd) or Gradle Wrapper (gradlew/gradlew.bat) in the project root — prefer wrappers when present
  2. If a wrapper exists, read .mvn/wrapper/maven-wrapper.properties or gradle/wrapper/gradle-wrapper.properties to determine the wrapper-defined version
  3. Run mvn --version or gradle --version to detect system installations
  4. Check MAVEN_HOME/M2_HOME environment variables

Report all found installations with their path, version, and source.

On success: Create .github/java-upgrade/{RUN_ID}/plan.md from the Plan Template — replace placeholders (<RUN_ID>, <PROJECT_NAME>, <current_branch>, <current_commit_id>, datetime) and follow the HTML-comment instructions to populate each section.