Microsoft Translator Translate tool
The Microsoft Translator tool translates untranslated block content with
the Microsoft Translator (Azure Cognitive Services) API. The provider is fixed
by the tool name, so there is no provider field. A target language is required
and an Azure subscription key must be supplied; the Azure region of the
Translator resource may also be required depending on how the resource is
provisioned. If the dedicated subscription key is empty, the shared apiKey
field is used as a fallback so keychain-based credential resolution works
uniformly.
Blocks that carry inline codes are round-tripped through semantic HTML so the API preserves the tags natively, then reconstructed from the response. With a session cache, targets already translated in a previous run are reused. When constructed without credentials the tool falls back to an offline demo provider so it remains listable and runnable for illustration.
Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
apiKey | string | API key for the MT provider | |
email | string | Account email for higher rate limits (mymemory) | |
projectId | string | Google Cloud project ID (google) | |
region | string | Azure region (microsoft) | |
subscriptionKey | string | Azure subscription key (microsoft) |
Configure these parameters interactively and copy the flow-step YAML on the Tool Reference.
Examples
Translate with Microsoft Translator
Translate untranslated blocks using an Azure subscription key and region.
subscriptionKey: your-azure-key region: westeurope
Processing notes
Operates on translatable blocks with non-empty source; other parts pass through unchanged.
Blocks with inline codes round-trip through semantic HTML so tags survive translation.
When subscriptionKey is empty the shared apiKey field is used as the subscription key.
Limitations
Requires a target language and an Azure subscription key; without a key the tool runs the offline demo provider, not Microsoft Translator.
The region must match the Translator resource when it is provisioned to a specific Azure region.
The provider makes a network round-trip per block; cost and latency scale with content volume.
← Back to the Tool Reference