Translator Knowledge Base Localizer

Overview

This flow keeps a multilingual help center current using Microsoft Translator V3. On a daily schedule it reads English-authored, Published knowledge-base articles from a SharePoint list, translates each one into a configured set of target languages (HTML-aware), stores every localized copy with language metadata in a second SharePoint list, and posts a summary of what was localized to a Teams channel.

Why it matters: support content authored in one language leaves non-native customers underserved. Automated localization scales a help center across languages without a translation team for every update.

Ships Off (Stopped).

Use Case

A support/enablement team authors articles in English in a SharePoint KB list and wants them available in several languages, refreshed on a schedule, with a record of coverage and a Teams notification each run.

Flow Architecture

Environment Variables

Connectors & Connections

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.

Languages

Edit flowlibs_KbTargetLanguages (e.g. fr,de,es,pt,ja,zh-Hans). The loop adapts automatically.

Source language

Change flowlibs_KbSourceLanguage, or remove the from parameter to let Translator auto-detect.

Scope

Adjust the Get Published Articles $filter (e.g. add a Modified date window) to localize only recently changed articles.

Glossary

Protect product names with a custom Translator category, or pre/post-process protected terms.

Human review

Write localized rows with a Draft status and gate publication behind an Approvals step for sensitive content.

Trigger swap

Replace Recurrence with a SharePoint item-created/modified trigger to localize on publish.

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.

split(parameters('flowlibs_KbTargetLanguages'), ',')

[ { "Text": "@{items('Apply_to_each_Article')?['ArticleBody']}" } ]

body('Translate_Article')?[0]?['TranslatedText']

concat('<li><strong>', items('Apply_to_each_Article')?['Title'], '</strong> localized into ', length(variables('varTargetLanguages')), ' language(s)</li>')