Documentation

Configuring Microsoft Translator in AEM 6.5.23 without an endpoint URL field

Last update: Wed Dec 17 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

When integrating Microsoft Translator with Adobe Experience Manager (AEM) 6.5.23, the configuration dialog doesn’t provide a field to enter the Microsoft endpoint URL. This limitation causes authentication errors if the subscription key isn’t created for the global region, as AEM Microsoft Translator connector supports only global keys and endpoints by design.

To fix this, ensure you use a global subscription key, configure translation services in AEM, and verify connectivity.

Description description

Environment

  • Product: Adobe Experience Manager (AEM) On-Premise
  • Version: 6.5.23
  • Connector Bundle: com.adobe.granite.translation.connector.msft.core:1.3.28
  • Deployment Type: On-Premise hosted on Azure Cloud
  • Constraints: No configurable endpoint URL field in translation connector UI

Issue/Symptoms

  • The subscription key shows as invalid when configuring Microsoft Translator in AEM.
  • There is no field available in AEM to configure the endpoint provided by Microsoft.
  • Attempts to use regional keys (for example, eastus, india) result in authentication failures.
  • Error logs display connection reset and internal server errors when verifying access tokens.

Resolution resolution

Verify that your Microsoft Translator subscription key is created for the global region in Azure. If you have a regional key (for example, eastus), request a global region key from your Azure administrator.

  1. In the AEM navigation panel, go to Tools > Cloud Services > Translation Cloud Services.
  2. Create a new configuration for your site or globally as needed.
  3. Enter your global region subscription key into the Subscription Key field.
  4. Select Connect to verify connectivity between AEM and Microsoft Translator services.
  5. Save and close the configuration dialog once verification succeeds.
  6. Ensure network connectivity to https://api.cognitive.microsoft.com over port 443. Open firewall ports if necessary.
  7. If you’re running an older connector bundle version, upgrade to the latest AEM Service Pack to ensure you have the most recent Microsoft Translator connector bundle.
  8. Verify successful integration by performing a test translation using Multi Site Manager (MSM).
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f