Azure’s monitor shows a restored availability signal in uaenorth for a large set of VM SKUs, all transitioning from unavailable to available. The newly observed shapes include dc, ec, and a-series variants across multiple sizes, which broadens placement options in the Middle East region.
This is not a clean first-time rollout: each SKU had one prior disappearance, with 89 days of history, 57 missing days, and an unavailable_pct of 64.0%. That pattern matters operationally because it lowers confidence in the catalog’s stability and makes these shapes better treated as a recovered option than a newly proven baseline.
For SRE and platform planning, the practical effect is more flexibility for right-sizing, performance tuning, and cost optimization in uaenorth. It also improves local fallback choices when you want to keep workloads in-region for latency or data residency reasons instead of moving to another geography.
The regional footprint expanded by one region for this feature set, from 11/64 to 12/64 regions covered, with deprecated_coverage at 0.0%. Current still-available regions include brazilsouth, centralindia, eastus, eastus2euap, italynorth, jioindiacentral, jioindiawest, northeurope, southeastasia, uaenorth, westeurope, and westus.
VM size availability affects placement, capacity planning, and upgrade targets; the current catalog signal is summarized in Azure’s VM sizes overview: https://learn.microsoft.com/azure/virtual-machines/sizes/overview