LioX Web Translation Engine with Microsoft Azure Translator for TranslatePress

LioX Web Translation Engine with Microsoft Azure Translator for TranslatePress adds Microsoft Azure Translator as an automatic translation engine inside TranslatePress.

The plugin is intended for site owners who already use TranslatePress and want to use their own Microsoft Azure Translator resource for new automatic translations.

Features include:

• Microsoft Azure Translator integration through the Azure Translator REST API.
• API Key, Region and Endpoint configuration inside TranslatePress.
• Support for multiple target languages.
• Optional target-language whitelist.
• Existing TranslatePress translations are not overwritten.
• New untranslated strings can be translated automatically.
• Batch translation support.
• API credential validation.
• Configurable monthly character hard limit.
• Current-month usage and remaining-character display.
• Automatic monthly usage counter reset.

This plugin requires TranslatePress and a Microsoft Azure Translator resource configured by the site administrator.

Development repository: https://github.com/lioxweb/liox-web-translation-engine-for-translatepress

External Service

This plugin relies on Microsoft Azure Translator, an external third-party service, to perform automatic translations.

When the site administrator enables automatic translation, selects this Azure engine, and provides their own Azure credentials, untranslated text strings requested by TranslatePress are sent to Microsoft Azure Translator for processing. Source and target language codes are sent with the translation request. The configured Azure API key and, when applicable, Azure region are sent in HTTP request headers to authenticate the request.

The plugin may also query Microsoft’s public Translator languages endpoint to determine supported translation languages. That supported-languages request does not require an API key.

The plugin does not intentionally send WordPress user account information, analytics, telemetry, or advertising data. However, if a text string selected for translation itself contains personal or sensitive information, that text will be transmitted to Microsoft as part of the translation request.

Microsoft Azure Translator service:
https://azure.microsoft.com/en-us/products/ai-foundry/tools/translator

Microsoft Azure legal information and service terms:
https://azure.microsoft.com/en-us/support/legal/

Microsoft Privacy Statement:
https://www.microsoft.com/en-us/privacy/privacystatement

Use of Microsoft Azure Translator is subject to the terms, privacy practices, availability, quotas, and pricing of the Microsoft Azure account configured by the site administrator.

Privacy

This plugin does not include its own telemetry, advertising, or user tracking.

The plugin stores its configuration through the TranslatePress machine-translation settings in the WordPress database. The Azure API key is stored there as part of the administrator’s configuration. The plugin also stores a local monthly character counter and short-lived cached validation/language-support data in the WordPress database.

See the External Service section above for information about data sent to Microsoft Azure Translator.

Notes

• TranslatePress supports one active automatic translation engine at a time. If Azure is active, new untranslated strings for any allowed target language can use Azure.
• The plugin batches translation requests conservatively and handles longer strings in smaller pieces.
• The plugin uses TranslatePress’ own machine-translation logger and quota counter in addition to its local monthly Azure counter.
• The monthly counter includes explicit API credential tests because those tests send a real translation request to Azure.
• Passive frontend credential checks are cached and do not send repeated test translations.
• The local monthly counter only tracks requests made by this WordPress installation.