Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Configure API endpoint for Microsoft Translator

Avatar

Level 2

Hello,
we are currently trying to setup and rollout automatic translations using Microsoft. (AEM Sites 6.5.16 on AMS).
With this we have configured the setup of language copies and translations as described here:
https://experienceleague.adobe.com/docs/experience-manager-65/content/sites/administering/introducti...

 

We get successful translations using a trail subscription key. So the setup itself works and we have translations.

But we have issues to use our licensed key given by Microsoft / Azure. When we enter these keys we are always getting a 401 connection issue in the trace logs. Within the translation process there is no error displayed. It succeeds to completed, but it just does not translate the content.

We tried together with our provider to generate new keys for the subscription, but any of them are failing. And always, when we switch back to the trail key it works again.

 

Currently our supposition is, that the Microsoft Translator configuration connects to an API endpoint, which does not support our subscription keys.
In the configuration of the Microsoft Keys based on Azure we see named API Servers to be used. But in the AEM configuration we can only configure the Subscription Key, but not the API endpoints.

 

Which are the default API endpoints being used?
How could we configure our own endpoints based on our subscription?

 

Thanks for supporting us.

Kind regards
Timo

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

This might be due to the region configured while enabling the translation service; the region for the Microsoft Translator Service should be enabled as global instead of selecting the local regions.

Refer to Microsoft Translator Service — Issue while fetching the Access Token | AEM(Adobe Experience Manager)... for more details.

Regards

Albin

https://www.albinsblog.com

Albin Issac – Medium

 

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

This might be due to the region configured while enabling the translation service; the region for the Microsoft Translator Service should be enabled as global instead of selecting the local regions.

Refer to Microsoft Translator Service — Issue while fetching the Access Token | AEM(Adobe Experience Manager)... for more details.

Regards

Albin

https://www.albinsblog.com

Albin Issac – Medium

 

Avatar

Level 2

Hi Albin,
thank you for that hint. Indeed, this was the solution for getting the translations!
Regards,
Timo