TL;DR. First check status.slackbridge.com: it shows whether SlackBridge's own service is up, not the state of your individual bridge. If SlackBridge is up, open the dashboard: Linked Channels shows each bridge as Active, Paused, Pending or Error with a note saying what is missing, and the Connection Health page for each connected organization shows its setup checklist and message flow in each direction. The most common causes are a Microsoft administrator removing SlackBridge's consent, the app being removed from Slack, SlackBridge not yet added to a private or shared Teams channel, and the app missing from the partner's Teams app catalog. To reach a person, email support@slackbridge.com; SlackBridge's support page says it responds within 1 business day. SlackBridge's Terms of Service do not guarantee any specific service level unless agreed in writing.
The short version
- Is it SlackBridge? Check status.slackbridge.com.
- Is it your setup? Open the SlackBridge dashboard and look at the bridge's status and the connection's Connection Health page.
- Still stuck? Email support@slackbridge.com. A person will look at it.
Is SlackBridge down, or is it my setup?
status.slackbridge.com shows four checks: the API server (core API and message routing), the dashboard and website, the Slack integration (Slack's event webhook receiver) and the Microsoft Teams integration (the Teams bot endpoint). It does not show the state of your individual bridge.
Slack and Microsoft outages stop bridges too. If SlackBridge's status page is clear, check Slack's own status page and Microsoft 365 service health (in the Microsoft 365 admin center) before changing anything.
A useful rule of thumb: if every bridge has stopped, look at the status pages first. If one bridge, or one direction of one bridge, has stopped, the cause is more likely on one side of that bridge, and the dashboard often says what it is.
Before deciding a bridge is broken, allow a few minutes. Most messages typically arrive in seconds, but roughly one Teams-to-Slack message in twenty takes minutes, when Microsoft is slow to notify SlackBridge of a new message.
What to check in the dashboard
- Linked Channels. Each bridge has a status: Active, Paused, Pending or Error. A Paused bridge has been switched off; an admin can switch it back on in the same table. A Pending bridge often carries a note saying what is missing and who needs to do it.
- Organizations, then the Connection Health icon next to a connection. This page shows the connection's setup checklist and, for each linked channel, whether messages can flow Slack to Teams and Teams to Slack. If Microsoft's approval needs to be given again, it offers Re-consent now and Copy consent link (to send to the Microsoft 365 administrator).
- Send Test Message on a bridge in Linked Channels posts a test message into the Teams channel. If it arrives, Slack-to-Teams delivery works.
Common causes
| What you see | Likely cause | What to do |
|---|---|---|
| Nothing from Teams reaches Slack; Slack to Teams still works | A Microsoft 365 administrator removed SlackBridge's approval (Enterprise applications in Microsoft Entra) | The administrator approves SlackBridge again: see What does my Microsoft 365 admin need to approve? |
| Nothing reaches or leaves Slack | The SlackBridge app was removed from the Slack workspace | Reinstall it with Add to Slack: see Installing SlackBridge in Slack |
| Slack messages do not reach a private or shared Teams channel, and the sender gets a reply in Slack saying so | SlackBridge has not been added to that Teams channel | A channel member adds it under Manage channel, Apps: see private and shared Teams channels |
| Teams to Slack works, Slack to Teams does not, and the bridge is Pending with a note about the app catalog or the team | The SlackBridge app is not in the partner organization's Teams app catalog, or not installed in the team | The partner's Teams administrator uploads the app (instructions at slackbridge.com/downloads); SlackBridge then installs it automatically |
| Messages from a private Slack channel do not reach Teams | SlackBridge is not a member of the Slack channel | Run /invite @SlackBridge in the channel |
| Messages flow one way only, on purpose or not | The bridge's direction is set to one way | Check the direction in the bridge's settings in Linked Channels |
A failed payment is not a cause: when a Pro renewal payment fails, nothing is paused while Stripe retries the card. See Plans, trials, invoices and cancelling.
Does SlackBridge notice on its own?
Often, yes. SlackBridge's monitoring alerts the SlackBridge team when a bridge's deliveries fail repeatedly, when Microsoft's message notifications for a connection cannot be renewed, when the SlackBridge bot is missing from a team and cannot be reinstalled automatically, and when a bridge has delivered nothing 72 hours after it was created. These alerts go to SlackBridge, not to you, so they are not a reason to wait: if a bridge matters to you, tell us.
How do I reach a person?
Email support@slackbridge.com. The form on the support page opens a pre-filled email to the same address. Every email becomes a support ticket. How support email is handled, including an AI drafting step, is described in Which companies process our data, and does SlackBridge use AI?
To get it fixed fastest, include:
- your Slack workspace name and the Microsoft Teams organization's name;
- the Slack channel and Teams channel of the bridge;
- which direction is failing (Slack to Teams, Teams to Slack, or both);
- the approximate time of a message that did not arrive, with your time zone;
- what the bridge's status and Connection Health page show.
How fast will a person reply? SlackBridge's support page says: "We respond within 1 business day to all support inquiries." The Pro plan includes priority support. There is no uptime guarantee: SlackBridge's Terms of Service (section 9) say SlackBridge "cannot guarantee 100% uptime" and "We do not guarantee any specific service level unless otherwise agreed in writing."
Security issues go to security@slackbridge.com instead.