You can translate documents directly in SharePoint and OneDrive using Microsoft 365's built-in document translation, which creates a translated copy of a file in up to 10 languages at once while preserving the original format. It supports common types including .docx, .xlsx, .pptx, .pdf, .csv, and .txt, with a 40 MB file size limit. The native feature works well for routine internal files — but it has hard limits that matter for professional work: it does not translate text embedded in images, it cannot process encrypted or password-protected files, and its language and quality ceiling is fixed. For confidential or formatting-critical documents, a dedicated platform fills those gaps.
Bluente is an AI-powered document translation platform used by 30,000+ professionals to translate files in 120+ languages while preserving original formatting. This article covers how native Microsoft 365 translation works, where it stops, and when to reach for a dedicated tool — accurate as of June 2026.
How Do I Translate a Document in SharePoint or OneDrive?
In a SharePoint document library or OneDrive, select the file or files, choose the translate action, and pick one or more target languages; Microsoft 365 generates a translated copy alongside the original while preserving the layout. You can select up to ten languages per request, and translation is available across all supported languages and dialects, with custom glossary support for consistent terminology.
For legacy formats like .doc, .xls, or .ppt, the translated copy is created in the modern equivalent — .docx, .xlsx, or .pptx. This is genuinely convenient for everyday internal documents: a team memo, an internal policy, a routine spreadsheet. The friction is low because the translation happens inside the tools people already use, with no upload or export step.
What Are the Limits of Native Microsoft 365 Translation?
Native SharePoint and OneDrive translation has three limits that matter for professional documents: text embedded in images is not translated, encrypted and password-protected files cannot be processed at all, and the maximum file size is 40 MB. These are not edge cases for legal, finance, and consulting work — they are common conditions.
Consider what each one means in practice. A scanned contract or a chart with labels baked into the image comes back with that text still in the original language, because the engine only translates the live text layer. A password-protected financial report or an encrypted board pack cannot be translated at all without first removing the protection, which may not be permitted. And a large, image-heavy diligence document can exceed the 40 MB ceiling. Each limit forces a manual workaround exactly when the stakes are highest.
Does Native Translation Handle Confidential Documents Safely?
Native Microsoft 365 translation runs within your Microsoft tenant, which is appropriate for many internal documents, but it does not give you the document-specific security controls that regulated work often requires — such as zero data retention by default, automatic deletion, and named compliance certifications scoped to the translation itself. Tenant-level security and document-level translation guarantees are not the same thing.
For a privileged contract, a counterparty's financials, or an HR investigation file, the right question is not only "does this stay in our tenant" but "what is the retention and processing guarantee for this specific document." Bluente is SOC 2, GDPR, and ISO 27001 compliant, with zero data retention by default, automatic deletion within 24 hours, and documents never used to train AI models. That posture is built around the document as the unit of risk, which is the standard most legal and financial teams are held to. It also gives compliance and security reviewers a clear, named answer to point to during procurement and audits, rather than a general assurance about tenant boundaries that may not map to how a specific document was actually handled.
When Should I Use a Dedicated Platform Instead?
Use a dedicated document translation platform when the file is confidential, exceeds native limits, contains text locked in images, or has formatting that must be exact. These are the documents where a near-miss is expensive — a contract clause, a financial table, a regulatory filing — and where the native feature's gaps turn into real work.
A dedicated platform also widens what is possible. Bluente supports 120+ languages versus a fixed native set, handles PDF, DOCX, XLSX, PPTX, images, and CSV, and completes most documents in under 2 minutes while keeping tables, charts, and layout intact. The practical rule: use native SharePoint and OneDrive translation for routine internal files, and a dedicated platform for anything client-facing, regulated, confidential, or formatting-critical. Many teams run both, choosing per document rather than standardizing on one.
Can I Translate a Whole SharePoint Library at Once?
You can translate multiple files in a single request — selecting a set of documents and up to ten target languages — but native translation is designed for file-by-file or small-batch work, not high-volume pipelines. For large libraries, recurring jobs, or programmatic translation, an API-driven approach scales better.
Bluente offers a translation API and an MCP server, so high-volume and automated translation can run without manual selection, and an AI agent can translate documents on demand while preserving formatting. For a one-off batch of internal files, native translation is fine; for an ongoing multilingual document operation, programmatic translation removes the manual ceiling entirely. It also keeps a consistent quality and security standard across every file, rather than depending on each user remembering to pick the right languages and the right tool one document at a time.
Frequently Asked Questions
Q: Can SharePoint translate documents while keeping formatting?
Yes. Microsoft 365's built-in document translation creates a translated copy in SharePoint or OneDrive while preserving the original format, for supported types like .docx, .xlsx, .pptx, and .pdf, up to 40 MB and up to 10 languages per request.
Q: Why didn't SharePoint translate the text in my images?
Native Microsoft 365 translation does not translate text embedded in images — only the live text layer. For scanned documents or charts with text baked into the image, use a platform with OCR-based document translation such as Bluente.
Q: Can I translate an encrypted or password-protected file in OneDrive?
No. Native translation cannot process encrypted or password-protected files. You would need to remove the protection first, or use a dedicated platform that can handle the document securely.
Q: How many languages does native Microsoft 365 translation support?
Native translation supports a fixed set of languages and dialects with custom glossary options. For broader coverage, Bluente supports 120+ languages across PDF, DOCX, XLSX, PPTX, images, and CSV.
Q: Is native SharePoint translation secure enough for confidential documents?
It runs within your Microsoft tenant, which suits many internal files, but it lacks document-specific guarantees like zero data retention and translation-scoped certifications. For privileged or regulated documents, a SOC 2, GDPR, and ISO 27001 compliant platform like Bluente is the safer choice.
---
Start translating documents for free. Bluente preserves your formatting across 120+ languages in under 2 minutes. Try BluTranslate free — no credit card required.