/
Lack of MT matches in a project: an issue involving different API endpoints in Microsoft MT

Lack of MT matches in a project: an issue involving different API endpoints in Microsoft MT

Owned by Damian Rozmiarkowski (Unlicensed)
Last updated: Jan 17, 2025 by Damian Rozmiarkowski
3 min read

Introduction

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

However, on the face of it, you might not even realize that the problem you are experiencing stems from the issue involving Microsoft MT endpoints in the first place. The most common symptoms of that issue in XTM Workbench are:

  • missing MT matches;

  • inability to return any MT matches.

Instructions

  1. First of all, do not hesitate to contact the XTM Support team so that they can confirm that the problem is related to API endpoints indeed.

  2. Microsoft MT has different API endpoints for different regions. If your API endpoint is not a default endpoint, the XTM International Support team needs to add it so you can specify an API custom endpoint (whose name includes the region for which it has been selected).

  3. You then need to sign in to your Microsoft MT integration portal, and find both the key and the region you are using. For example:

image.png

  1. The MT engine will only start working after you set this endpoint globally, in the global settings: select Configuration → Settings → Translation → Machine translation → Microsoft Translator, and fill in the API key and Translation endpoint URL fields accordingly (administrative privileges required!).

If you are unsure where to type it in, provide the XTM Support team with a screenshot from the integration portal that shows a location/region and an endpoint (as presented on the first screenshot).

OPTIONALLY

You can specify a MS MT engine per XTM Cloud customer. To do so:

  • Select Customers → Customer list → (select a customer) → Settings → Machine translation.

  • 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.

Different API endpoints in Microsoft MT

The 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.