Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Azure Translator Text API 2026-06-06 is the latest generally available (GA) release, available through Microsoft Foundry. If you're currently using Translator Text API v3.0, this guide walks you through what changed and how to update your integration.
The new version introduces expanded model options, new translation controls, and a revised request and response schema. It is not backward compatible with v3.0—you need to update your API version, payload structure, and any code that depends on v3.0-specific methods.
Important
- API version
2026-06-06is not a drop-in replacement for v3.0. Changes to request structure, response schema, and supported methods are required. - Test your application thoroughly in a nonproduction environment before migrating any production workloads.
- Validate your code and internal workflows, and restrict production deployments to API versions you fully test.
What's new in API version 2026-06-06
There are key capabilities added in the 2026-06-06 API. Review each one to understand whether it applies to your integration and whether it requires code changes or opens up new scenarios for your application.
Large language model (LLM) selection. You can now choose between standard Neural Machine Translation (NMT) and a supported Large Language Model (LLM), such as GPT-5.1, for each translation request. This allowance lets you balance quality, cost, and performance without managing prompt engineering or manual quality pipelines. LLM-based translation requires a Microsoft Foundry resource.
Adaptive custom translation. You can supply up to five reference translation pairs or an adaptive dataset index ID to guide LLM output toward your preferred style and terminology. This allowance is useful for domain-specific content or applications with established glossaries.
Tone and gender controls. Translation requests now accept tone (formal, informal, neutral) and gender (male, female, neutral) parameters when using LLM-based translation. These parameters are optional but allow you to produce more targeted output for audience-specific scenarios.
Method changes
The 2026-06-06 API changes several required parameters and removes methods that v3.0 supported. Review the following tables to identify what you need to update in your code.
Warning
- API version
2025-10-01-previewis deprecated 90 days after GA. - To migrate from
2025-10-01-previewto GA, setapi-version=2026-06-06.
Required parameters
The most important structural change is the replacement of the v3.0 to parameter with a targets array. Update all translation requests to use the new schema.
| API version: 2026-06-06 | API version: v3.0 |
|---|---|
| api-version • Value must be 2026-06-06 |
api-version • Value must be 3.0 |
| text • Specifies the source text to translate. |
text • Specifies the source text to translate. |
| targets • An array that defines one or more translation targets. |
• The targets array isn't used in the v3.0 schema. |
| language • Target language code specified within the targets array.• Values must be from the supported languages. |
to • Specifies the target language for translation. • Values must be from the supported languages. |
For details about supported targets array values, see Translate text.
API compatibility
Several v3.0 methods are no longer available in 2026-06-06. If your application uses any of the removed methods, plan a replacement before migrating.
| Azure Translator v3.0 | Azure Translator 2026-06-06 |
|---|---|
| Translate text | Translate text |
| Transliterate | Transliterate |
| Languages | Languages |
| BreakSentence | No longer supported. Replace with a sentence delimiter function or a natural language processing (NLP) library compatible with your programming language. |
| Detect | No longer supported. Replace with the Azure AI Language detection API. |
| Dictionary Lookup | No longer supported. Consider using adaptive custom translation for domain-specific term handling. |
| Dictionary Examples | No longer supported. |