Translator Document Multilingual Publisher

Overview

This flow produces a multilingual document set from a single source. When a document is published to a SharePoint source library, it reads the content, translates it into a configured set of target languages with Microsoft Translator V3 (textType=html, so HTML structure and formatting are preserved), files each localized copy into a per-language folder in a separate destination library, and emails regional owners that the new versions are ready. Maintaining translated versions by hand is slow and drifts out of sync; auto-generating localized copies on publish keeps every language current from a single authoritative source.

Use Case

A team authors policies, guides, or marketing docs centrally (as HTML/text source documents) and needs them available in several languages, refreshed whenever a new source document is published. Regional owners are notified automatically so they can review the machine translations.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Microsoft Translator	shared_microsofttranslatorv	Translate
SharePoint	shared_sharepointonline	GetOnNewFileItems GetFileContent CreateFile
Office 365 Outlook	shared_office365	SendEmailV2

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Glossary / brand protection

Point flowlibs_TranslatorCategory at a Custom Translator category id so product, brand, and SKU terms are not translated.

Per-document languages

Add a metadata column on the source library and read it to drive target languages per document instead of the global env var.

Human review gate

For regulated content, insert an Approvals StartAndWaitForAnApproval between Translate Document and Create Localized File so a reviewer signs off before publishing.

Binary Office documents

For .docx/.pptx, swap the text Translate for Translator's asynchronous Document Translation (built-in HTTP, blob-staged) for full document fidelity.

Translation frequency

Adjust the trigger recurrence (default Minute/5) to match how often documents are published.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@base64ToString(body('Get_File_Content')?['$content'])

@body('Translate_Document')?[0]?['TranslatedText']

@{concat(variables('varDestinationLibrary'),'/',items('Apply_To_Each_Language'))}

@{concat(items('Apply_To_Each_Language'),'-',triggerOutputs()?['body/{FilenameWithExtension}'])}

@split(parameters('EnvVar_TargetLanguages'),',')

Customize & download