Are you passing the header Ocp-Apim-Subscription-Region while using the regional endpoint api-nam.cognitive.microsofttranslator.com? Regional endpoint forces the request to be handled by that geography mentioned in the URI. In this case it is NAM.
It is recommended to use the URI api-apc.cognitive.microsofttranslator.com if the resource is created in Australia region to avoid request being handled by other geographies.
When we sign up a Microsoft Trranslator service for a specific region but the translation request URL is of a different geography, the translation requests will be served based on specific region or geography?
While creating a Microsoft Translator Service, we can opt for a specific region instead of global and pass the in the header section as value for key 'Ocp-Apim-Subscription-Region'.
As per this link (https://learn.microsoft.com/en-in/azure/cognitive-services/translator/reference/v3-0-reference), if we have the region as 'global' then we can use geographical based URL to force the translation requests being served the corresponding data center region.
If we select region as 'australiaeast' while creating the translator service and use base URL as 'api-nam.cognitive.microsofttranslator.com' (United States), currently the translation requests are getting processed successfully.
However, we need to know whether these translation requests are being served from 'australiaeast' or 'api-nam.cognitive.microsofttranslator.com' region. Please confirm.
1 answer
Sort by: Most helpful
-
romungi-MSFT 48,401 Reputation points Microsoft Employee
2020-06-01T10:34:40.407+00:00