Documentation
Bridge Slack and Microsoft Teams
Everything needed to connect both platforms, map a pair of channels, and keep the bridge running. Start with the quickstart if you're setting up for the first time.
Getting started
-
Overview
What ThreadBridge does, what it relays between Slack and Microsoft Teams, and what it deliberately leaves alone.
-
Quickstart
Connect Slack, connect Microsoft Teams, map a pair of channels, and start your first bridge.
Connecting platforms
-
Connect Slack
Install the ThreadBridge Slack app, the scopes it requests, and how to bridge private channels.
-
Connect Microsoft Teams
Connect your Microsoft 365 tenant and the Graph permissions ThreadBridge uses to read and post channel messages.
-
Microsoft admin approval
Why Teams bridges need tenant-wide admin consent, and how to hand the approval off to your Microsoft 365 administrator.
-
Slack workspace approval
How to hand off connecting a Slack workspace to someone else in it, without them needing a ThreadBridge account.
Running bridges
-
Bridges and channel maps
Create a bridge, map channels between platforms, and start, stop, or restart it.
-
How messages are delivered
What a bridged message looks like on each platform, how loops are prevented, and what is not relayed.
-
Reliability and monitoring
Health checks, automatic restarts, token refresh, and the alerts you get when a bridge stays down.
Reference
-
Architecture
How the Rails control plane and the Elixir runtime split the work, and the path a message takes between them.
-
Security and data handling
Credential storage, webhook verification, what ThreadBridge keeps, and what it never writes down.
-
Troubleshooting
The errors bridges report most often and what each one means.
Still stuck?
Email support@threadbridge.app with your bridge name and, if you have one, the error shown on the bridge page. That error is the fastest way for us to tell a permissions problem from a mapping problem.