Index of every page on this site: llms.txt
All skills
microsoft avatar

/azure-upgrade

@0d60658
by microsoftmicrosoft/skills3.2k stars
373
Run it yourself

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

Use this Skill: https://skilld.dev/gh/microsoft/skills/azure-upgrade

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesservicesfunctionsconsumption-to-flexwindowsautomation.md

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

Automation: Consumption to Flex Consumption Upgrade

Azure CLI scripts to automate the upgrade from Windows Consumption plan to Flex Consumption plan.

Shell compatibility: Scripts use a universal subset that runs unchanged in:

  • bash 5.x (Cloud Shell, WSL, macOS, Linux)
  • PowerShell 7.x on any OS

Secret-handling steps provide separate Bash and PowerShell 7 blocks when the shells require different cleanup or quoting syntax. Step 4c uses jq for the Bash in-memory JSON transform and ConvertFrom-Json / ConvertTo-Json for PowerShell.

Replace <PLACEHOLDERS> (e.g. <APP_NAME>, <RESOURCE_GROUP>) with literal values before running each command. Each az command is a single line for cross-shell safety; conditional steps are described in prose between code blocks.

Source docs: Windows migration guide

az functionapp flex-migration does not support Windows. All migration steps are performed using raw Azure CLI commands.

⚠️ Source-app safety invariant: All discovery and replication steps treat the source app as read-only. Before any command that changes the source app's settings, triggers, state, deployment, bindings, or existence, use ask_user to describe the exact command and impact and obtain explicit approval. Approval applies only to that specific action.

⚠️ Workflow continuity: After each step succeeds, immediately perform the next read-only preflight. If the next action requires approval, invoke ask_user in the same turn. Never stop after only announcing the next step and wait for the user to re-engage.

📍 Progress reporting: Create and maintain <UPGRADE_DIR>/upgrade-status.md using Migration Progress. Derive the current and total phases and executable steps from the workflow headings, then display the same Phase <current> of <total> · <step> · <description> · <state> banner before and after every step. Do not use percentages.

Workflow Files

Load only the file for the current workflow unit. Complete it before loading the next file unless that file explicitly directs otherwise.

Order Workflow unit Instructions
1 Prerequisites, discovery, and compatibility assessment Discovery and Assessment
2 Source configuration and dependency inventory Configuration Inventory
3 Deployment package retrieval when local source is unavailable Deployment Package
4 Target naming, storage selection, authentication preflight, and creation App Creation
5 Production-setting copy or defer decision and secure transfer App Settings
6 Site configuration and managed identities Site and Identity Configuration
7 Built-in authentication configuration or migration deferral Built-in Authentication
8 CORS, domains, and access restrictions Networking and Storage
9 Pre-deployment trigger safety, monitoring, and configuration verification Trigger Safety and Monitoring
10 Access-key inventory and preservation decision Access Key Strategy
11 Code deployment Code Deployment
12 Post-deployment access-key copy and verification Access Key Copy
13 Post-upgrade validation and production cutover Validation and Cutover
14 Outcome-gated cleanup and rollback Cleanup and Rollback

The headings inside these files remain the source of truth for stable step IDs and progress tracking. The table defines execution order; filenames describe responsibilities and do not encode ordering.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts25d3 checks · Risk SAFE
  • Gen Agent Trust Hub25d

    This skill facilitates the assessment and automated upgrade of Azure workloads and Java SDK dependencies. It includes security considerations such as command execution and external resource retrieval, which are used appropriately within its intended functionality as a migration tool.

  • Socket25d

    No alerts

  • Snyk25d

    Risk: LOW · No issues

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

Last checked against GitHub yesterday.

Activeupdated last month
compatibility
python3.10+
metadata
{
  "author": "Microsoft",
  "version": "1.2.3"
}

README badge

README badge for microsoft/skills/azure-upgrade