Translator Teams Cross-Language Channel Bridge

Overview

This flow turns a single Microsoft Teams channel into a multilingual collaboration space. It polls the channel for new messages, detects each message's source language, translates it into a configurable set of target languages with Microsoft Translator V3, posts the combined translations back into the channel as a single reply, and writes an audit row to Dataverse for every translation. Distributed teams otherwise fragment into language-specific channels or copy-paste into external translators; an automatic in-channel bridge keeps the whole team in one conversation, in the language each member reads.

Use Case

A team with members across regions shares one Teams channel. When anyone posts a message, the flow detects the language and replies with translations into the configured target languages (e.g. Spanish, French, German), so everyone reads the discussion without leaving the channel. Each translation is logged in Dataverse for usage tracking and audit.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Microsoft Teams	shared_teams	OnNewChannelMessage PostMessageToConversation
Microsoft Translator	shared_microsofttranslatorv	Translate
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords CreateRecord
HHTTP (built-in)	http	HTTP - Detect language

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.

Target languages

Edit flowlibs_BridgeTargetLanguages (e.g. es,fr,de,ja). The flow loops over every code automatically.

Lingua-franca mode

Set a single code (e.g. en) to translate everything into one common language instead of many.

Per-member languages

Extend the loop to read each member's preferred language from Dataverse and translate per reader.

Skip code/links/short messages

Add a Filter or extra Condition before the loop to skip code blocks, URLs, or messages below a length threshold (cost control).

Reply threading

Switch PostMessageToConversation to a reply op and pass the original replyToId to thread the translation under the source message.

Polling cadence

Adjust the trigger recurrence (default Minute/5) for faster delivery vs. fewer API calls.

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.

@and(not(equals(trim(variables('varMessageText')),'')), not(contains(variables('varMessageText'), variables('varMarker'))))

@equals(length(outputs('List_Existing_Log')?['body/value']), 0)

@coalesce(first(body('Detect_Language'))?['language'], 'en')

@concat('<p><b>', toUpper(trim(item())), ':</b> ', first(body('Translate_Message'))?['TranslatedText'], '</p>')

Customize & download