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/bom-migration/bom-validation.md

BOM Migration — Validation Checklist

After BOM migration, verify:

  • [ ] Project compiles successfully.
  • [ ] No legacy com.microsoft.azure.* dependencies remain anywhere (pom.xml, build.gradle, TOML, settings.gradle).
  • [ ] BOM-managed Azure libraries have no explicit version (no <version> tag, no version string, no version.ref, no .versionRef()).
  • [ ] Re-resolve the latest stable azure-sdk-bom from the Azure SDK for Java source of truth and confirm the plan guideline TARGET_AZURE_SDK_BOM_VERSION matches it exactly.
  • [ ] Every BOM version in the migrated project equals TARGET_AZURE_SDK_BOM_VERSION; no BOM version was copied from the original project, examples, prior plans, or model memory.
  • [ ] No stale azure-sdk-bom version remains.

Additional checks for TOML version catalog projects

  • [ ] No orphaned entries in [versions] (every version key must be referenced by at least one library or plugin).
  • [ ] [bundles] aliases match current [libraries] aliases (no stale references).
  • [ ] build.gradle uses libs.<alias> references — no raw "group:artifact:version" strings for Azure libraries.

Additional checks for programmatic settings.gradle catalog projects

  • [ ] No orphaned version(...) calls (every version must be referenced by at least one library or plugin entry).
  • [ ] bundle(...) aliases match current library(...) aliases (no stale references).
  • [ ] build.gradle uses libs.<alias> references — no raw "group:artifact:version" strings for Azure libraries.