GPT 5 azure AI model pricing not available for regional standard deployment

GPT-5 version 2025-08-07 cannot currently be deployed as Regional Standard in Australia East; use Global Standard, or Regional Provisioned Managed when geography-based processing is mandatory.

The missing Standard option and missing Regional Standard price are therefore consistent with the documented availability rather than a portal or quota problem. The current matrix lists GPT-5 2025-08-07 in Australia East for Global Standard and Regional Provisioned Managed, but does not confirm Regional Standard there.^1^

Currently documented choices

Microsoft documents that new deployment types generally arrive in this order: Global, then Data Zone, then geography-based. Geography-based availability arrives last, depends on capacity, and has no guaranteed availability date.^2^

Do not interpret an Australia East Global Standard deployment as Australia-only processing: Australia East is where the resource/deployment is created, while Global Standard may route inference to other Azure regions.

Pricing interpretation

The pricing page lists GPT-5 2025-08-07 Global and Data Zone rows but no GPT-5 Regional row.^3^ Without an available Regional Standard deployment and corresponding regional meter, there is no applicable public GPT-5 Regional Standard price for this combination.

For an independent meter check, query the public Azure Retail Prices API. This example follows pagination and restricts results to Australia East, GPT-5-family consumption meters, excluding global, Data Zone, batch, and provisioned SKUs:^4^

import requests

url = "https://prices.azure.com/api/retail/prices"
params = {
    "$filter": "productName eq 'Azure OpenAI GPT5' "
               "and priceType eq 'Consumption'",
    "api-version": "2023-01-01-preview",
}
items = []
while url:
    data = requests.get(url, params=params, timeout=30).json()
    items += data.get("Items", [])
    url, params = data.get("NextPageLink"), {}

for item in items:
    sku = item["skuName"].lower()
    excluded = ("global", "data zone", "batch", "prov")
    if item["armRegionName"] == "australiaeast" and not any(x in sku for x in excluded):
        print(item["skuName"], item["retailPrice"], item["unitOfMeasure"])

Inspect any returned SKU name carefully for the exact model and meter direction. A retail meter’s existence alone does not establish that the model is deployable; the model/version/deployment-type/region availability matrix remains authoritative.

If pay-per-token Regional Standard is a firm requirement, retain the existing architecture plan but open an Azure support request for roadmap or business-impact guidance. There is no published availability date to rely on.

References

1. Region availability for Foundry Models sold by Azure (standard)
2. Deployment types for Microsoft Foundry Models
3. Azure OpenAI Service - Pricing | Microsoft Azure
4. Azure OpenAI frequently asked questions