Translator resource in a non global region - api

Dana Shviro 26 Reputation points

I created a Translator resource with a specific region (non global) (example: eastus). when I'm calling the global api "", its guaranteed it will be processed on the specific region? or at least in the same geo? Or I should use the specific geo url (such as "")

I'm sending this header as part of the request "Ocp-Apim-Subscription-Region:<region>"
Example url I'm using:

+what happens on cases of disasters and BCDR? the call is guaranteed to be called within the Geo? or it will just fail?

Azure Translator
Azure Translator
An Azure service to easily conduct machine translation with a simple REST API call.
313 questions
0 comments No comments
{count} vote

Accepted answer
  1. GiftA-MSFT 11,141 Reputation points

    Hi, please review the reference document for more details:

    Requests to Translator are, in most cases, handled by the datacenter that is closest to where the request originated. If there is a datacenter failure when using the global endpoint, the request may be routed outside of the geography. To force the request to be handled within a specific geography, use the desired geographical endpoint. All requests are processed among the datacenters within the geography.

    --- *Kindly Accept Answer if the information helps. Thanks.*

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful