How to solve an issue involving different API endpoints in Microsoft MT


This article explains how to set up Microsoft machine translation (MT) with two different endpoints.


Microsoft MT has different endpoints for different regions. If an endpoint is not a default endpoint, the XTM International Support team needs to add it so you can specify a custom endpoint (whose name includes the region for which it has been selected). The MT engine will only start working after you set this endpoint globally, in the global settings: select ConfigurationSettingsTranslationMachine translationMicrosoft Translator (administrative privileges required!).

Additionally, you can also specify that MT engine per XTM Cloud customer. To do so:

  1. Select CustomersCustomer list → (select a customer) → SettingsMachine translation.

  2. From the Microsoft Translator login data dropdown, select Customer specific.

You will now be able to enter a different API key from the one defined in the global settings. However, a problem occurs when you have two API keys and two different region endpoints. You cannot set a different endpoint for a customer than the globally-defined endpoint, so the customer's API key must be for the same region, otherwise it will not work. There can be two different API keys, but the endpoint itself must be the same as the globally-defined endpoint.

That being said, if you have two API keys, you can set one key globally and set the other one in an XTM customer. However, there are two conditions:

  • if there are two different endpoints, because they are for different regions, this setting in the customer service will not work.

  • if the endpoint is the same but there are two different API keys, the MT engine will work both for the individual XTM customer and globally.