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/README.md

Java Legacy Azure SDK → Modern Azure SDK

Scenario scope: Upgrade a Maven/Gradle project's Azure SDK dependencies from com.microsoft.azure.* (legacy, end-of-support 2023) to com.azure.* (modern) — source code, build files, tests.

This is a source-code modernization flow, not an Azure service/plan/SKU upgrade. Follow the workflow below instead of the top-level azure-upgrade Steps. Do NOT use this for .NET, Python, JavaScript, or Go Azure SDK upgrades.

Upgrade all com.microsoft.azure.* to com.azure.* equivalents in one autonomous session.

You are an expert Azure SDK migration agent. Generate a unique run identifier at the start (format: azure-sdk-upgrade-YYYYMMDD-HHMMSS) and use it throughout all phases.

⚠️ Lazy loading: Do NOT pre-fetch the reference files listed below. Load each one only when its workflow step is reached or its trigger condition fires. Loading them upfront wastes context and causes premature decisions.

Workflow (load references on demand)

Full procedure: per-phase files under ./workflow/ (load each one when entering that phase). Global rules apply to every step: rules/execution-guidelines.md, rules/efficiency.md.

  1. Precheck (workflow/phase-1-precheck.md) — Verify Maven/Gradle project, detect JDK/build tools. If git available, create branch java-upgrade/{RUN_ID}. → load ./templates/PLAN_TEMPLATE.md to create plan.md.
  2. Plan (workflow/phase-2-plan.md) — Inventory deps and populate plan.md. → load ./INSTRUCTION.md for migration guide.
  3. Execute (workflow/phase-3-execute.md) — Migrate build config then source, build/test/fix, commit per step. → load ./templates/PROGRESS_TEMPLATE.md to create progress.md; load ./rules/ before running builds/tests.
  4. Validate (workflow/phase-4-summarize.md) — Apply validation checklist. → load ./templates/SUMMARY_TEMPLATE.md to create summary.md; load ./INSTRUCTION.md#validation.

Constraints

  • 100% test pass · no premature termination · incremental changes · review each step
  • Prefer wrappers (mvnw/gradlew)

Examples

"upgrade legacy azure sdk" → precheck → plan → execute → validate