Loading benchmark data
Azure does not list this region in its published region list, so GPUQuant records it no more precisely than Texas and the map draws no shape for it. A cloud region is a set of availability zones rather than a building, and no provider publishes the addresses behind one.
History runs from Apr 2025 to Sep 2026.
A month with no publication holds the previous price and is marked as held.
The newest month each GPU was published.
| GPU | SKU | Variant | GPUs | Node per hour | Per GPU-hour | Normalization | Effective |
|---|---|---|---|---|---|---|---|
| H200 | Standard_ND96isr_H200_v5 | H200 141GB SXM5 | 8 | $93.28 | $11.6600 | Complete VM price divided by the GPU count | 2025-04-01 |
verified: The provider states the GPU model and count for this SKU on the row itself or on the specification page cited beside it.
No area the map draws is named for this region, so it has no place page. What the provider publishes about where it is, and does not, is stated above.
GPUQuant publishes no facility records with a recorded relation to Azure southcentralus2 yet. That is a statement about this site and not about the ground: a record is only published once a primary or near-primary source can be quoted for every claim on it, and none has been recorded here. Nothing on this page should be read as a complete list of the datacenters in this area.
No provider publishes which building is behind which cloud region, and the relationship is one-to-many in both directions, so GPUQuant does not assert it. A facility here is only ever recorded as sitting inside the area the provider names for this region, or as something the provider itself stated with a source. See methodology.