skilld
All skills
microsoft avatar

/azure-upgrade

@36a90f7 official
by microsoftmicrosoft/github-copilot-for-azure253 stars
206

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

Ask your Agent

Use this Skill: https://skilld.dev/gh/microsoft/github-copilot-for-azure/azure-upgrade

This session only. Nothing lands on disk.

referenceslanguagesjavabom-migrationbom-validation.md

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

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.

Source: SKILL.md on GitHub

Third-party checks

2 warnings4mo5 checks · Risk SAFE
  • Gen Agent Trust Hub4mo

    This skill facilitates Azure workload upgrades and Java SDK modernization. It includes security considerations such as command execution and fetching data from remote sources, which are within the skill's intended purpose of automating cloud and code migrations.

  • Socket4mo

    No alerts

  • Snyk4mo

    Risk: MEDIUM · 2 issues

  • Runlayer6mo

    3/6 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

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

Last checked against GitHub yesterday.

Activeupdated 5 months ago

Capability

compatibility
python3.10+
metadata
{
  "author": "Microsoft",
  "version": "0.0.0-placeholder"
}

Topics

  • Infrastructure
  • azure
  • azure-functions
  • azure-app-service
  • azure-redis
  • java-sdk
  • migrations
  • sku-upgrades
  • consumption-plan
  • flex-consumption

README badge

README badge for microsoft/github-copilot-for-azure/azure-upgrade

What it does

Assesses and automates Azure workload upgrades across plans, tiers, and SKUs—such as Functions Consumption to Flex Consumption, App Service to Container Apps, or Redis migrations to Azure Managed Redis. Also modernizes legacy Azure Java SDK dependencies (com.microsoft.azure to com.azure) in source code. Includes readiness checks, configuration migration, and validation steps.

Generated from the current SKILL.md.

Frequently asked

Does this skill handle cross-cloud migration?
No. This skill is for Azure-to-Azure upgrades only (plan changes, SKU swaps, service migrations within Azure). For cross-cloud migration, use the `azure-cloud-migrate` skill.
What Azure upgrades does this skill cover?
It handles Azure Functions plan upgrades (Consumption to Flex Consumption), hosting tier changes, App Service to Container Apps migration, Redis cache upgrades (ACR/ACRE to Azure Managed Redis), and legacy Azure Java SDK modernization (com.microsoft.azure to com.azure).
Will this skill delete my existing app without asking?
No. The skill requires explicit user confirmation before stopping or deleting the original app. All destructive actions trigger a confirmation prompt.
Does this skill support Java SDK modernization?
Yes. It handles source-code modernization from legacy Azure Java SDKs (com.microsoft.azure.*) to modern ones (com.azure.*).
What happens after the upgrade is complete?
The skill asks whether you want to verify performance, clean up the old app, or update your infrastructure-as-code. You can then hand off to `azure-validate` for deep validation or `azure-deploy` for CI/CD setup.

Generated from the current SKILL.md. These answers refresh after source changes.