Quickstart

Setting up the first bridge takes about ten minutes, most of which is waiting on your Microsoft 365 administrator. You'll need permission to install apps in your Slack workspace, and an administrator who can approve an app for your Microsoft tenant.

1. Connect the platform you're starting from

Whichever side you're setting this up for, Slack or Teams, start there: Continue with Slack or Continue with Microsoft Teams on the homepage do two things in one step, creating your ThreadBridge account and connecting that platform together, using the name and email Slack or Microsoft already has for you. There's no separate sign-up form to fill in first, though one still exists (sign up with email) if you'd rather create the account on its own and connect platforms afterward from the dashboard.

If you chose Slack: Slack asks which workspace to install into and shows the permissions ThreadBridge is asking for. Approve it and you land on your new dashboard with the workspace already connected. Connect Slack covers the scopes and what they're for, including what to do if the workspace isn't yours to connect.

If you chose Teams: you're signing in with your Microsoft 365 account, which identifies your tenant and gives ThreadBridge a token to work with. Almost always there's a second step after this: a Microsoft 365 administrator has to separately approve ThreadBridge for the whole tenant, covered below.

2. Connect the other platform

From the dashboard, connect whichever platform you didn't start with. If it's Teams and you haven't already, this is also where a Microsoft 365 administrator has to approve ThreadBridge for the whole tenant before it can read or send channel messages. The dashboard shows a banner with a link you can send them once you're connected. They don't need a ThreadBridge account, and neither does a Slack-side contact if that's the platform you're handing off: Microsoft admin approval and Slack workspace approval cover both.

A workspace or tenant can only be connected to one ThreadBridge account. If someone else in your company already connected it, you'll be told so rather than ending up with two accounts fighting over the same messages.

3. Create a bridge

With both platforms connected, New Bridge becomes available. Give the bridge a name you'll recognize later (the customer or project it belongs to is usually the right name) and map at least one Slack channel to one Teams channel.

The channel dropdowns are populated from the workspaces you connected, so you're picking from real channels rather than typing IDs.

4. Invite the app to the channels

In Slack, invite the ThreadBridge app to each mapped channel (/invite @ThreadBridge). Slack won't deliver messages from a channel the app isn't a member of. In Teams, no per-channel step is needed once the tenant has approved the app.

5. Start it

Open the bridge and press Start Bridge. The status changes to Running. Post a message in one of the mapped channels and it should appear on the other side within a couple of seconds.

If it doesn't, the bridge page shows the current status, the last error the runtime reported, and a list of recent events; that's the first place to look, and Troubleshooting explains the errors you're most likely to see.