Overview

ThreadBridge relays messages between a Slack channel and a Microsoft Teams channel. Someone posts in Slack, the message appears in Teams a moment later; someone replies in Teams, it appears in Slack. Neither side installs anything or changes how they work.

It exists for the situation where two organizations, or two halves of one, have already standardized on different chat tools and neither is going to switch. An agency on Slack working with a client on Teams. A support team on Slack whose customers live in Teams. An acquisition that hasn't finished consolidating.

What gets relayed

• New messages posted in a mapped channel, in both directions.
• The author's name, shown as a prefix on the relayed message.
• Plain text. Teams HTML is converted to text, and Teams @mentions arrive in Slack as @Name.

What is not relayed

ThreadBridge deliberately keeps a small surface. These are not bridged today:

• Message edits and deletions: the original relayed copy stays as it was sent.
• Reactions and emoji responses.
• Files, images, and attachments.
• Direct messages and group DMs. Bridges operate on channels only.
• User identity mapping. Relayed messages are posted by the ThreadBridge app with the author's name attached, not by an account belonging to that person.

Knowing this up front matters more than any feature list: a bridged channel is a shared transcript of what people said, not a perfect mirror of one platform inside the other.

How a bridge is put together

1. Connect a Slack workspace and a Microsoft 365 tenant. Connecting either one is also how you get a ThreadBridge account, if you don't have one yet.
2. Create a bridge and map one or more pairs of channels to each other.
3. Start the bridge. From then on it runs until you stop it.

One account can run several bridges, typically one per customer or per project, each with its own channel map and its own start/stop control. The quickstart walks through the whole setup.