For the Omni-Channel realtime translation sample web resource: https://github.com/microsoft/Dynamics365-Apps-Samples/blob/master/customer-service/omnichannel/real-time-translation/webResourceV2.js
When using Bing Translator hosted in a non-US region (in my case australiaeast) you need to add an additional header for the API call to be successful.
For example:
'Ocp-Apim-Subscription-Region': 'australiaeast',
(I added this above the line for 'Ocp-Apim-Subscription-Key': C1WebResourceNamespace.bingTranslateApiClientSecret)
While not everybody might need to add this parameter, I think it'd be good to add it in and default it. Non-US users of this will need to set the value.
For the Omni-Channel realtime translation sample web resource: https://github.com/microsoft/Dynamics365-Apps-Samples/blob/master/customer-service/omnichannel/real-time-translation/webResourceV2.js
When using Bing Translator hosted in a non-US region (in my case australiaeast) you need to add an additional header for the API call to be successful.
For example:
'Ocp-Apim-Subscription-Region':'australiaeast',(I added this above the line for
'Ocp-Apim-Subscription-Key':C1WebResourceNamespace.bingTranslateApiClientSecret)While not everybody might need to add this parameter, I think it'd be good to add it in and default it. Non-US users of this will need to set the value.