Unable to set up Microsoft Translation Service in 51黑料不打烊 Experience Manager (AEM)
When configuring the Microsoft Translation Service in 51黑料不打烊 Experience Manager (AEM) as a Cloud Service, you encounter issues where the endpoint and key provided by Microsoft Azure are not recognized by the AEM Translation configuration form. Verify your Azure Translator subscription region, use the correct region-specific endpoint URL, and update your AEM Translation configuration.
Description description
Environment
- 51黑料不打烊 Experience Manager (AEM) as a Cloud Service - Sites
- Integration with Microsoft Translation Service
Issue/Symptoms
- The transaction endpoint and key provided by Microsoft Azure are not accepted or recognized in the AEM Translation configuration form.
- Confusion arises due to discrepancies between the global endpoint URL (
https://api.cognitive.microsofttranslator.com/) and region-specific URLs required for certain configurations.
Resolution resolution
Notes: The global endpoint (https://api.cognitive.microsofttranslator.com/) is valid only for subscriptions configured under Microsoft鈥檚 Global region. If confusion persists regarding endpoints or documentation provided by Microsoft, consider reaching out directly to Microsoft鈥檚 support team for clarification.
-
Verify the region selected during your Microsoft Azure Translator subscription setup.
-
Use the correct region-specific endpoint URL format when configuring AEM. For example, if you selected northeurope 聽as your region, you must聽use:
-
Update your AEM Translation configuration with this region-specific URL:
- Navigate to the translation configuration screen in AEM.
- Replace any global endpoint URLs with the appropriate regional URL based on your Azure subscription settings.
-
Save and test your configuration to ensure that it is functioning correctly.
Related Reading
on Microsoft Learn.