{"id":2200,"date":"2026-06-02T10:00:06","date_gmt":"2026-06-02T17:00:06","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/foundry\/?p=2200"},"modified":"2026-06-02T17:16:59","modified_gmt":"2026-06-03T00:16:59","slug":"azure-translator-api-version-2026-06-06-ga-supporting-multilingual-applications-with-flexible-translation-options","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/foundry\/azure-translator-api-version-2026-06-06-ga-supporting-multilingual-applications-with-flexible-translation-options\/","title":{"rendered":"Azure Translator API Version 2026\u201106\u201106 (GA): Supporting Multilingual Applications with Flexible Translation Options"},"content":{"rendered":"
\n
\n

Ship multilingual features in hours, not months<\/strong><\/h2>\n

Your translation workflow probably looks like this: one vendor for real-time chat, another for document translation, a custom LLM integration for nuanced content, and a spreadsheet tracking which system handles what. Azure Translator’s new API (version 2026-06-06, now GA) consolidates all of this\u2014NMT speed, LLM fluency, and adaptive customization\u2014into a single endpoint.<\/p>\n<\/div>\n

Why It Matters: Managing Trade\u2011offs<\/h2>\n
Translation approaches often involve trade-offs. NMT is commonly used for fast, real\u2011time scenarios, while LLM-based approaches may provide more fluent or context-aware outputs depending on the use case.<\/div>\n
Azure Translator helps organizations manage these trade-offs by providing multiple model options through a single API. Developers can select models at runtime and make configuration choices based on cost, latency, and quality requirements. This can help reduce architectural complexity and support faster iteration in some development workflows.<\/div>\n

Azure\u2019s Differentiation: Unified API Experience<\/h2>\n
Azure Translator provides a unified API surface that supports multiple translation approaches, including NMT, LLM-based deployments, and customization features.<\/div>\n
This approach can reduce the need to manage multiple translation integrations while giving teams flexibility to balance latency, cost, and quality in real time, depending on configuration and scenario.<\/div>\n
It also introduces adaptive translation capabilities that may reduce the need for traditional model retraining in certain scenarios. Developers can provide reference examples to influence terminology, tone, and style, which may support faster iteration for some workflows.<\/div>\n

Enterprise\u2011Ready and Built for AI<\/h2>\n
Azure Translator is designed to help provide consistent outputs depending on model selection and input quality, with enterprise-grade security and compliance in accordance with Azure standards (see official documentation for details), and configurable cost and performance characteristics based on usage and model selection.<\/div>\n
These capabilities can support translation scenarios at scale.<\/div>\n
Designed for modern AI workflows, Azure Translator can integrate into copilots, agents, and multilingual applications. The service provides capabilities for model selection, customization, and multi-language processing, which may reduce infrastructure management overhead for developers.<\/div>\n

How It Works: Simple for Developers<\/h2>\n
Azure Translator is designed for simplicity, with a single REST API, structured request and response model, and SDKs across major programming languages. Developers can get started with minimal infrastructure management compared to building custom translation systems.<\/div>\n
The platform supports model routing between NMT and LLM-based deployments, adaptive customization using examples, and multi-language translation in a single call. Additional built-in capabilities include language detection, transliteration, and dictionary features. These capabilities can help reduce the amount of translation-related orchestration developers need to implement.<\/div>\n

What\u2019s New in API Version 2026\u201106\u201106 (GA)<\/h2>\n
API version 2026\u201106\u201106 is generally available and includes updates compared to v3.0, including changes to request and response formats.<\/div>\n
If you’re migrating from v3.0, plan a full validation pass for payload structure, response parsing, and production testing prior to rollout.<\/div>\n

Key updates include:<\/h3>\n