Azure OpenAI Realtime: Can GPT Realtime processing remain in Australia East?

Teah Rota 0 Reputation points
2026-08-18T00:36:46.51+00:00

We need GPT Realtime for a speech-to-speech healthcare use case with Australian data-sovereignty requirements.

The Azure Speech regional documentation lists gpt-realtime as available for australiaeast, but only with a Global Standard deployment. Microsoft’s deployment documentation states that Global Standard may process prompts and responses in any Azure region, while single-region processing requires a Standard or Regional deployment.

Can GPT Realtime currently be deployed with processing restricted to Australia, either through a regional deployment, a private/approved configuration, or another supported Azure option?

Community Center | Not monitored

1 answer

Sort by: Most helpful
  1. Andrew Taylor - COREZENN 1,390 Reputation points Volunteer Moderator
    2026-08-18T01:44:15.06+00:00

    Hi @Teah Rota

    Thanks for reaching out to Microsoft Q&A I understand you are looking to validate data sovereignty for a health-care workload.

    I would not use the Australia East Global standard option for a workload that requires inference processing to remain in Australia.

    The Azure Speech supported-regions page lists Voice Live gpt-realtime in australiaeast, but it lists the deployment type as Global standard. The Foundry deployment-types documentation claims that Global deployments can process inference data in any Azure region. Therefore, deployment in Australia East does not by itself provide an Australia-only processing commitment.

    For a single-region processing requirement, the same documentation identifies Standard or Regional Provisioned as the relevant deployment types, where supported. I could not find a documented gpt-realtime Standard or Regional Provisioned option in Australia East. A private endpoint or other network configuration would not alter the documented processing location for a Global deployment. Data Zone processing is also not an Australia-only alternative: it is limited to a Microsoft-defined APAC zone.

    There is a documentation inconsistency worth calling out: the Speech region table shows gpt-realtime Global standard in Australia East, while the Foundry regional availability table does not show gpt-realtime in Australia East. I would open an Azure support request before proceeding, including the exact service path (Speech Voice Live or Azure OpenAI Realtime), model version, resource region, subscription, and the requirement for Australia-only processing. Ask support to confirm whether an Australia-only deployment type is available for that exact configuration and to investigate the conflicting availability tables.

    For a healthcare use case with a strict Australia-only requirement, I would treat this as a current product-availability dependency and wait for written confirmation of a supported single-region option rather than relying on Global standard.

    Please 'Upvote' (Thumbs-up) and 'Accept' as answer if the response was helpful. This will be helpful to other community members who face the same issue.

    Best regards, Andrew S Taylor

    Was this answer helpful?

    1 person found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.