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/rules/upgrade-strategy.md

Upgrade Strategy

  • Incremental upgrades: Stepwise dependency upgrades to avoid large jumps breaking builds.
  • Minimal changes: Only upgrade dependencies essential for compatibility with the modern Azure SDKs.
  • Risk-first: Handle EOL/challenging deps early in isolated steps.
  • Necessary/Meaningful steps only: Each step MUST change code/config. NO steps for pure analysis/validation. Merge small related changes. Test: "Does this step modify project files?"
  • Automation tools: Use automation tools like OpenRewrite for efficiency; always verify output. For BOM upgrades, run the scripts/upgrade_bom.py script in the parent folder when Python 3.10+ is available; if Python is not available or the script fails, manually resolve the BOM version and follow the Manual Fallback sections in bom-maven.md / bom-gradle.md instead (see Migration Guidelines).
  • Successor preference: Compatible successor > Adapter pattern > Code rewrite.
  • Build tool compatibility: Check Maven/Gradle version compatibility with the project's JDK. Upgrade the build tool (including wrapper) if the current version does not support the JDK.
  • Temporary errors OK: Steps may pass with known errors if resolved later or pre-existing.