Today’s Azure regional probe surfaced two significant regression patterns for VM SKU availability: a full deprecation candidate event in australiasoutheast and a wave of recurring instability in canadaeast. Both affect the DC-series and EC-series v5 VM SKUs, which are commonly used for confidential computing and performance-sensitive workloads.
In australiasoutheast (Oceania), all tracked DCv2 SKUs (Standard_DC1s_v2, DC2s_v2, DC4s_v2, DC8_v2) transitioned from available to absent after 59 days of continuous catalog presence. This is not a recurring regression—there were no prior disappearances. The region now shows 0% coverage for these SKUs, down from 6.2% (4/64 regions previously). There are no fallback regions remaining in Oceania or globally, suggesting a likely deprecation event. For SREs, this means immediate revalidation of right-sizing, cost, and fallback plans for any DCv2-dependent deployments in this geography. See [VM size overview](https://learn.microsoft.com/azure/virtual-machines/sizes/overview) for SKU context.
Meanwhile, in canadaeast (North America), all DC- and EC-series v5 SKUs (ads/as, cc, and standard variants from 2 to 96 vCPU) again became unavailable after brief availability streaks. These are recurring regressions: each SKU was available for only 6 of the past 59 days, with 36 days missing and a prior disappearance already logged. The region’s coverage for these SKUs fell by 1 region per SKU, with current coverage at 25–34% across the monitored set. However, fallback remains possible in many other regions such as eastus, westeurope, and centralindia.
Operationally, these changes are highly relevant for capacity planning, automated right-sizing, and SKU selection logic. The abrupt and complete loss in australiasoutheast is a strong deprecation signal, while the instability in canadaeast reinforces the need for robust multi-region fallback strategies and automated catalog refreshes. Review your SKU allowlists and placement policies to avoid provisioning failures or unexpected cost/performance shifts.
For more details on VM SKU capabilities and alternatives, refer to the [Azure VM size documentation](https://learn.microsoft.com/azure/virtual-machines/sizes/overview).