az-scout-plugin-vm-sku-modernization 2026.8.0

Legacy SKU VM inventory and migration-scope dashboard for Azure v6/v7 planning

az-scout-plugin-vm-sku-modernization

External Az Scout plugin for VM SKU Modernization. It inventories legacy VM SKUs (v2-v5) that are in scope for Azure v6/v7 migration planning and adds guided recommendations for readiness, pilot validation, storage/network checks, quota planning, and exportable migration checklists.

What it provides

• a UI tab: VM SKU Modernization
• plugin API routes under /plugins/vm-sku-modernization/
• an MCP tool: list_migration_candidate_vms
• a target-SKU recommendation panel for inferred v6/v7 candidates
• script helpers for validation steps that must be run locally or from Azure CLI
• a Markdown checklist export from the VM detail modal

Package and plugin identifiers

Surface	Value
GitHub repository	JoGbd/az-scout-plugin-vm-sku-modernization
PyPI package	az-scout-plugin-vm-sku-modernization
Python module	az_scout_vm_sku_modernization
Az Scout plugin entry point	vm_sku_modernization
Mounted plugin name	vm-sku-modernization

The plugin is auto-discovered through:

[project.entry-points."az_scout.plugins"]
vm_sku_modernization = "az_scout_vm_sku_modernization:plugin"

Install locally in Az Scout

From this repository:

uv sync --group dev
uv pip install -e .

Then start Az Scout from your main Az Scout workspace:

uv run az-scout web

The plugin tab appears as VM SKU Modernization once the editable install is visible in the Python environment used by Az Scout.

Main capabilities

The dashboard includes:

• inventory columns for VM name, resource group, subscription, region, SKU, generation, OS, image publisher, disk controller, and zones
• readiness recommendations with statuses such as Verified, Needs remediation, Script / check, and Human review
• priority badges such as Critical risk, Important, and Advisory
• inline Why it matters guidance per recommendation
• an Advanced check flow for deep checks that require live ARM calls
• script helpers for:
  • driver validation
  • SCSI path validation
  • pilot boot diagnostics / extension validation
  • before/after network validation
  • app-state inventory
  • OS-disk backup / restore
  • temporary-disk checks
  • quota and capacity planning
• a checklist export for the currently selected VM

Migration-effort scoring is calculated by the backend and included in each VM record. Publisher classification is intentionally conservative: only publishers whose name begins with Microsoft are treated as first-party; Canonical and all other publishers remain third-party for planning purposes.

VM detail modal data flow

1. Selecting a keyboard-focusable inventory row opens the plugin modal and builds workload recommendations from the VM inventory record.
2. The plugin derives v5 or v6/v7 candidate names, then queries /api/skus for candidates in parallel. Results are cached for five minutes per tenant, subscription, region, source SKU, and modernization target.
3. The highest-confidence candidate is passed to /api/sku-detail. The response supplies the shared VM Profile, Zone Availability, Quota, Basic Deployment Confidence, and Pricing renderers.
4. Detail responses are cached for five minutes per candidate and currency. Changing the currency performs (or reuses) the matching currency request; an older in-flight response cannot replace the newly selected currency.
5. A failed or partial profile, quota, or pricing response does not hide the workload recommendations. The modal identifies unavailable values explicitly and uses the /api/skus snapshot only where it contains usable data.

Caches are cleared when inventory or modernization target changes. Live Azure capacity, quota, and retail prices can change during the cache window and must be revalidated before deployment.

Score limits

Basic Deployment Confidence is an indicative ranking signal, not a deployment guarantee. It combines the signals returned by az-scout (for example SKU match, quota pressure, zones, restrictions, and pricing pressure), excludes missing signals, and can become blocked when a hard constraint is detected. It does not prove instantaneous capacity, application compatibility, image support, performance, reservation eligibility, or successful migration.

The separate Migration Effort badge is a deterministic planning heuristic based on the inventory fields available to this plugin: Hyper-V generation, disk controller, security profile, publisher, and hibernation. Missing fields are handled conservatively. Neither score replaces a pilot, the Advanced check, subscription quota validation, or workload-owner review.

Quality checks

uv run ruff check src/ tests/
uv run ruff format --check src/ tests/
uv run mypy src/
uv run pytest
node --test tests/frontend/vm-sku-modernization.test.js

Publish and submit to catalog

1. Push this plugin to JoGbd/az-scout-plugin-vm-sku-modernization.
2. Tag a release (CalVer style recommended, for example v2026.7.0).
3. Publish the package to PyPI using .github/workflows/publish.yml.
4. Open a catalog request in Az Scout with:
   • the GitHub repo URL
   • the PyPI package name: az-scout-plugin-vm-sku-modernization
   • a short description and screenshots

Documentation

For Azure migration guidance behind these recommendations, see:

https://learn.microsoft.com/en-us/azure/virtual-machines/migration/sizes/sizes-v6-v7-migration-plan

Disclaimer

This plugin is not affiliated with Microsoft. Capacity, pricing, availability, and validation outputs are indicative and must be reviewed in your own tenant before production rollout.