Azure Translator's Build 2026 updates add LLM-powered translation, native image translation, and a consolidated API (version 2026-06-06, now GA), which makes it a stronger general translation service, but for high-stakes business documents where exact formatting and confidentiality decide whether the output is usable, a document-first platform still does the job better. By way of context, Bluente is an AI-powered document translation platform covering 120+ languages, and format preservation is the problem it was built to solve.
The difference is not which engine is more fluent. It is whether the tool was built to rebuild a contract, a financial statement, or a regulatory filing exactly as it came in. This guide breaks down what changed at Microsoft Build in June 2026, what those changes are good for, and where teams translating legal, financial, and regulated documents will still feel the gap.
What Did Azure Translator Announce at Build 2026?
At Microsoft Build on June 3, 2026, Azure Translator expanded its Document Translation feature with LLM-powered translation, native image translation, and broader structured-content support, and the new Azure Translator API (version 2026-06-06) went GA, consolidating neural machine translation, LLM translation, and adaptive customization behind a single endpoint. Microsoft framed it as letting teams choose LLM quality when nuance matters and classic NMT when throughput and cost matter.
Two of the additions are genuinely useful. Native image translation uses Azure AI Vision to detect text in an image, translate it, and render it back in place, and Document Translation can now optionally translate text embedded in images inside Word documents. Earlier in 2026, Azure also added native support for XML DITA and XLIFF 2.0. These are real steps forward for a cloud translation service.
Is Azure Translator a Document Translator or a Translation API?
Azure Translator is primarily a translation API and cloud service that includes a document translation feature, which means it is built for developers and platforms to call programmatically, not for a lawyer or analyst to drop a file into and get a finished document back. That distinction matters more than the model quality.
A dedicated document translator like Bluente is built around the document as the unit of work: you upload a PDF, DOCX, XLSX, or PPTX and receive the same file back, translated, with tables, charts, headers, footnotes, and numbering intact. Azure's document feature can preserve a lot of structure, but it lives inside Azure's tooling, has file-size and format constraints per request, and assumes you are building or operating the pipeline around it. For a professional who just needs the translated file to look exactly like the original, that operational overhead is the cost.
Does LLM-Powered Translation Fix the Formatting Problem?
No. A better language model improves fluency and nuance, but formatting breaks for a different reason: how the tool extracts and reinserts text relative to the document's layout. A PDF stores text as fragments at fixed positions, and a translation that swaps words without modeling the structure will still collapse tables, shift clause numbering, and reflow pages, no matter how good the underlying model is.
This is why dedicated document translators invest in a layout-aware engine that maps the full structure of a file before translating and rebuilds it in place afterward. Bluente reports 100% formatting retention across PDF, DOCX, XLSX, PPTX, images, and scanned files, because the engine treats layout as a first-class part of the job rather than something to reconstruct downstream. LLM quality and format preservation are separate problems, and Build 2026 advanced the first, not the second.
How Do They Compare on Confidential Documents?
For confidential documents, the deciding factor is the data-handling policy, and a document-first platform built for regulated work tends to make stronger, simpler commitments. Azure Translator inherits Microsoft's enterprise security posture, which is robust, but configuring it correctly across data residency, retention, and logging is the buyer's responsibility within their Azure environment.
Bluente is built for sensitive documents by default: SOC 2 Type II, GDPR, and ISO 27001 compliant, with end-to-end encryption, zero data retention, and automatic deletion of documents within 24 hours. Documents are never used to train AI models, NDAs and security reviews are standard, and trials can run on synthetic or public data so an evaluation never depends on uploading real client files. For in-house legal, banking, and compliance teams, that default posture is the difference between a quick yes and a months-long infosec review.
When Should You Use Azure Translator?
Use Azure Translator when translation is one component of a larger software product or pipeline you are already building on Azure, when you need programmatic translation at high volume across many surfaces, or when you want to translate UI strings, support content, and structured files inside an existing Microsoft stack. As a translation API with a strong new model layer, it is a solid choice for engineering teams.
Choose a dedicated document translator when the document itself is the deliverable: cross-border contracts, financial statements, board decks, regulatory filings, and any file where a misaligned table or a shifted clause number creates real work or real risk. The two are not mutually exclusive; many teams use a cloud API for in-product strings and a document-first platform for the high-stakes files that go to clients, counterparties, and regulators.
What Does Bluente Do Differently?
Bluente is document-first across the whole workflow. It rebuilds files in their original layout across 120+ languages in under two minutes on average, handles text inside images and scanned files through OCR, and produces side-by-side bilingual output for verification. Teams lock terminology with a custom glossary so defined terms, entity names, and regulated phrasing translate the same way every time, and Bluente reports around 95% accuracy on legal terminology, trained on 500,000+ contract terms.
It also spans both speed and formality: instant AI translation for high-volume review, plus human-certified attested translation in the same platform for the documents that need it. And for teams building agentic workflows, Bluente offers a translation API and an MCP server, so AI agents can translate documents without leaving the layout behind. The result is the outcome professionals actually want, a finished file that looks exactly like the original, at less than $0.60 per page and up to 90% below agency cost.
Frequently Asked Questions
Q: What's new in Azure Translator after Build 2026? At Build 2026, Azure Translator added LLM-powered translation, native image translation via Azure AI Vision, and broader structured-content support, and the consolidated Azure Translator API (version 2026-06-06) reached general availability. It also added native XML DITA and XLIFF 2.0 support earlier in 2026.
Q: Does Azure Translator preserve document formatting? Azure's Document Translation feature preserves a meaningful amount of structure, but it is an API-centric cloud service with per-request format and size constraints. A document-first platform like Bluente is built specifically to return the same file with tables, charts, and numbering fully intact, reporting 100% formatting retention.
Q: Is Azure Translator or a dedicated translator better for legal documents? For legal documents, a dedicated document translator is usually the better fit because format preservation, terminology control via glossary, certified output, and a strict data-handling default matter more than raw model fluency. Bluente reports around 95% accuracy on legal terminology and offers certified translation alongside instant AI translation.
Q: Can I use both Azure Translator and Bluente? Yes. Many teams use a cloud translation API for in-product strings and high-volume software localization, and a document-first platform for client-facing and regulated documents. They solve different parts of the problem and work well together.
Q: How does Bluente handle security for confidential files? Bluente is SOC 2 Type II, GDPR, and ISO 27001 compliant, with end-to-end encryption, zero data retention, and automatic deletion within 24 hours. Documents are never used to train AI models, and trials can run on synthetic or public data.
Q: Does Bluente offer an API or MCP server like a cloud service? Yes. Bluente provides a format-preserving translation API and an MCP server so developers and AI agents can translate documents programmatically while keeping layout intact. See the documentation and the MCP server repo.
Related Reading
ATA Certified Translators vs Government Sources: Which Is Better for Your Transcripts?
Cipher by Translayte vs Bluente: Which Document Translator Fits You?
Sources and Further Reading
Primary standards, regulations and specifications referenced above:
How to Use AI on Confidential Documents Without Violating Client Privacy — practitioners describing this problem in r/Entrepreneurs
Last reviewed 29 August 2026. Written by the Bluente document engineering team, who build and test the format-preservation pipeline described above. We update these guides when the underlying standards, regulations or file formats change.
Start translating documents for free. Bluente preserves your formatting across 120+ languages in under 2 minutes. Try BluTranslate free — no credit card required.