Microsoft Azure Translator

Azure Translator translates text and documents instantly or in batches across more than 100 languages, delivered through a single API that also handles source language detection. Detection matters more than it appears in real deployments: user-generated content, support tickets and inbound messages rarely arrive labelled, so a translation pipeline that requires the source language to be specified fails at the first step.

The most interesting capability is the hybrid approach to models. Alongside neural machine translation, Microsoft offers flexible translation using foundation models such as GPT-4o for tone, gender and style customisation. Gender is a genuinely difficult problem in machine translation, since many languages mark gender where English does not, and a system guessing wrongly produces output that is fluent and incorrect in a way that is embarrassing rather than merely inaccurate. Being able to control it explicitly is a real capability rather than a refinement.

Customisation covers domain-specific terminology, letting an organisation define how terms are translated based on previously translated documents and build customised translation models without machine learning expertise. That last clause is the commercially relevant part: model customisation is usually gated behind data science capability most organisations do not have.

The agentic use cases named are specific and current: translation for call centres, multilingual conversational agents and in-app communication. Real-time translation inside a support conversation is a different engineering problem from translating documents, so naming those separately reflects genuine capability rather than positioning.

It is delivered within Microsoft Foundry Tools as a production-ready, scalable engine. Pricing follows Azure consumption based on characters translated.