TL;DR. Yes, with one extra step. A standard Teams channel works as soon as SlackBridge is installed in the team. A private or shared channel only lets apps in that a channel member has added to that specific channel, so after you link the channel in the SlackBridge dashboard, a member opens the channel in Teams, chooses Manage channel, opens Apps and adds SlackBridge. Until that is done, messages from Slack cannot be posted into the channel, and SlackBridge tells the sender so in Slack. Mentions and file copying stay off in private and shared channels.
The short version
Microsoft Teams has three kinds of channel, and they treat apps differently:
| Channel type | Who is in it | What SlackBridge needs |
|---|---|---|
| Standard | Everyone in the team | Nothing extra. Installing SlackBridge in the team is enough. |
| Private | A subset of the team, chosen by the channel owner | SlackBridge must be added to the channel by a channel member. |
| Shared (Teams Connect) | People and teams inside or outside your organization | SlackBridge must be added to the channel by a member of the host team. |
Teams does not let an app that is installed in the team post into a private or shared channel until someone adds it to that channel. There is no way for SlackBridge, or any other app, to do this step on your behalf: Microsoft deliberately keeps it in the hands of the channel's members.
How to add SlackBridge to a private or shared channel
- Link the channel in the SlackBridge dashboard as usual. The channel picker labels private and shared channels, and the dashboard reminds you of this step after the bridge is created.
- In Microsoft Teams, open the channel.
- Click the channel name at the top (or the three dots next to it) and choose Manage channel.
- Open the Apps tab and click Add an app.
- Find SlackBridge and add it. SlackBridge has to be installed in the team that hosts the channel first. The dashboard installs it in the team when it creates the first bridge for that team; if it is missing, a team owner can add it from the team's Apps page.
That is all. The next message from Slack is delivered into the channel. Messages posted in the channel reach Slack through the same Microsoft notification mechanism standard channels use; SlackBridge has confirmed it can read private-channel messages, but has not yet watched a shared channel deliver end to end, so send one test post from Teams after adding the app and tell [email protected] if it does not arrive in Slack. The dashboard clears the setup reminder once SlackBridge learns it has been added, either from Teams directly or from the first message it delivers.
If SlackBridge is not in the list of apps you can add, your organization's SlackBridge app package is an older version that predates private and shared channel support. Microsoft only lets a Teams administrator update it, signed in as a person: in the Teams admin center under Teams apps, Manage apps, open SlackBridge, choose Upload file and upload the current package from the SlackBridge dashboard's downloads page. The update keeps the existing installation. For a shared channel, the person adding SlackBridge must be a member of the team that hosts the channel.
What happens if the step is skipped
Before September 2026, a bridge to a private or shared channel failed silently: Slack messages were accepted, could not be posted into Teams, and were lost. That no longer happens quietly:
- The sender gets a threaded reply in Slack explaining that the message did not reach Teams and what to do, once a day per channel.
- The bridge shows the missing step in the dashboard.
- SlackBridge's daily health check flags a bridge that has never delivered a message.
Messages sent before SlackBridge was added to the channel are not delivered later. Send them again once the step is done.
What still does not work in private and shared channels
- Mentions. Typing someone's name does not notify them across the bridge, because SlackBridge cannot read a private or shared channel's member list. See Do @mentions translate between Slack and Microsoft Teams?.
- File copying. Files are announced by name rather than copied, because private and shared channels store files in their own SharePoint site rather than the team's.
- Teams Connect channels shared into your team from another organization. Only the host team can add apps to a shared channel. If the channel was shared into your team by someone else, ask the host organization to add SlackBridge, or bridge a channel your team hosts.
Delivery from Slack into the channel is what this step unlocks; the Teams-to-Slack direction is described above. Threads, reactions and emoji use the same code as standard channels, but SlackBridge has not yet verified every one of them in private and shared channels; if something does not bridge, tell [email protected].
Which kind of channel do I have?
In Teams, a private channel shows a small lock icon next to its name, and a shared channel shows a small link icon. In the SlackBridge channel picker, both are labelled next to the channel name. Standard channels carry no label.