Azure VM SKU docs lie about availability
Planning a cloud GPU rental against the official Microsoft Learn docs.
A SKU having a Microsoft Learn family page (with specs, naming, and ARM identifiers) does NOT mean it is actually rentable from a given subscription. Confirmed via az vm list-sizes that a documented new-generation GPU SKU was unavailable across all 16 regions checked, even with a Founders Hub-eligible sub. Two distinct portal signals matter: an explicit Request quota link next to a SKU means available-but-quota-zero (fixable in 1-3 days), while complete absence from the size picker means the SKU is not yet enabled for the subscription type (support ticket, weeks). The az vm list-sizes loop catches this in 30 seconds before any planning gets sunk.
Before any cloud-GPU plan around a newly-documented SKU, run az vm list-sizes --location <r> --query "[?contains(name, ...)]" across 5+ candidate regions. Empty result everywhere = pivot to a different cloud (vast.ai, Hostkey, Lambda) or a different SKU. Do not assume Microsoft Learn presence implies rentability.