Slack ⇄ Microsoft Teams
Two chat tools.
One conversation.
Your team lives in Slack. Your client lives in Teams. ThreadBridge connects a channel on each side so messages flow both ways in seconds: no guest accounts, no forwarding, nobody learning a second app.
Connect with OAuth. No admin access to your messages, no software to install. Sign up with email instead.
Priya Raman
Draft is ready for review whenever you are.
Dana Okafor via ThreadBridge
Dana Okafor: can we push the review to Thursday?
ThreadBridge relayed
Priya Raman: Draft is ready for review whenever you are.
Dana Okafor
can we push the review to Thursday?
Set up in an afternoon
Three steps, most of them clicks. The only thing you may wait on is your Microsoft administrator approving the app.
Connect both platforms
Install the Slack app in your workspace and sign in with Microsoft 365. Standard OAuth, revocable from either platform at any time.
Map your channels
Pick a Slack channel and the Teams channel it should talk to. Add as many pairs as a project needs.
Press start
The bridge comes up and stays up. It restarts itself when it can, and emails you when it can't.
Built to be left alone
Real time, both directions
Both platforms push messages to ThreadBridge over webhooks, so a message typically lands on the other side in a second or two, no polling, no digest.
No loops, ever
A relayed message lands in a channel the bridge is watching. ThreadBridge fingerprints every message it sends and drops the echo when it comes back, instead of hoping bot flags are enough.
One bridge per relationship
Run a separate bridge for each client or project, each with its own channel map and its own on/off switch. One customer's revoked token can't touch another's.
Restarts itself
Every bridge is health-checked every two minutes and restarted automatically when it drops. If it can't be recovered, the account owner gets one email naming the bridge and the reason.
Nothing archived
Message text isn't written to a database. It's relayed and released; your messages stay where they were posted, under your own retention policies.
Least privilege by default
List channels, read messages, post messages. No directory access, no mailboxes, no files, no DMs, and only the channels you mapped are ever subscribed to.
Questions people ask first
Do our clients have to install anything?
No. The bridge is installed once on each side by whoever administers that workspace. Everyone else just posts in their normal channel.
Can it see our other channels?
It only reads the channels you map. On Slack, it receives nothing at all from channels the app hasn't been invited to. On Teams, it subscribes only to the specific channels in a bridge's map.
Does it store our messages?
No. Message text passes through memory on its way to the other platform and isn't written to a database. What's recorded is the bridge's own lifecycle: started, stopped, errors, health checks.
What about threads, edits, reactions and files?
Threaded replies are relayed into the matching thread on the other side. Edits, reactions and files aren't relayed today: a bridged channel is a shared transcript of what people said, not a perfect mirror of one platform inside the other. The docs are explicit about the boundaries.
What happens if it goes down?
It's health-checked every two minutes and restarts itself up to three times. If it still can't come up, the account owner gets one email with the reason. Messages sent while a bridge is down aren't backfilled.
Can we disconnect?
At any time, from either platform or from here. Revoking in Slack or withdrawing consent in Microsoft Entra stops the relay immediately.
Stop copy-pasting between two apps
Connect a workspace, map a channel, and let the conversation happen in one place.