Latest scan: 52 new availability signals and 343 regressions across 3 regions.
VM SKUs: VM sizes withdrawn (343 signals; 4 deprecation candidates, 339 recurring disappearances, up to 3 prior disappearances). SRE impact: capacity planning and SKU fallback lists should be rechecked. Coverage now ranges from 1 to 18 of 64 monitored regions. The noisiest affected signal was unavailable 99.1% of prior observations. Examples: eastus · Azure virtual-machine size for right-sizing compute (basic.a0); eastus · Azure virtual-machine size for right-sizing compute (basic.a1); eastus · Azure virtual-machine size for right-sizing compute (basic.a2); eastus · Azure virtual-machine size for right-sizing compute (basic.a3); and 339 more.
VM SKUs: VM sizes now offered (52 signals; 52 restored availabilities, up to 2 prior disappearances). SRE impact: more compute shapes for right-sizing, performance, and cost tuning. Coverage now ranges from 11 to 11 of 64 monitored regions. The noisiest affected signal was unavailable 98.2% of prior observations. Expansion pattern: restored regional signal. Examples: northcentralus · Azure virtual-machine size for right-sizing compute (d128ds.v7); northcentralus · Azure virtual-machine size for right-sizing compute (d128lds.v7); northcentralus · Azure virtual-machine size for right-sizing compute (d128ls.v7); northcentralus · Azure virtual-machine size for right-sizing compute (d128s.v7); and 48 more.
What this means for Azure users: review placement and fallback plans using these catalog/list signals before changing production deployments.