TL;DR. Yes. Since September 2026, typing someone's name in a bridged channel sends that person a real notification on the other platform. SlackBridge posts the list of addressable names into each bridged channel; type one of them exactly as shown. Microsoft Teams will not suggest these names while you type, so type the name as plain text and send rather than picking from the Teams popup. Mentions work in standard Teams channels. They do not work in private or shared Teams channels, nor in a message whose file SlackBridge copies across to the other platform.
What's the short version?
You can now mention someone on the other side of the bridge and they will actually get notified. Type their name in a bridged Slack channel and the matching person is mentioned in Microsoft Teams, with a real Teams notification. Type their name in the bridged Teams channel and the matching person is mentioned in Slack, with a real Slack notification. This works for ordinary messages, including a message that simply names an attached file. The one exception is a message whose file SlackBridge copies across to the other platform, covered below.
This changed in September 2026. Before that, mentions crossed the bridge as readable text only and could not notify anyone on the destination platform.
| Direction | What happens |
|---|---|
| Slack → Teams | The named Teams person is mentioned in Microsoft Teams and notified there |
| Teams → Slack | The named Slack person is mentioned in Slack and notified there |
Slack #channel → Teams |
The channel name arrives as readable text |
@channel, @here, @everyone |
Readable text only; no destination-side broadcast |
The one thing to remember: Microsoft Teams will not suggest these names while you type. Type the name as plain text and send.
What do I type?
Type a name exactly as SlackBridge lists it in the channel. That list is the authority, and SlackBridge posts it into each bridged channel the first time mentions are switched on:
SlackBridge can pass an @mention to the Teams side of this channel.
It emits a Teams mention when a message names someone by one of these:
• Jeremy Warfield: @jeremy (or @jeremy_warfield_solobrands)
• Ron McCranie: @ron (or @rmccranie_solobrands)
The long spelling is the one every channel has. It is built from the account name that person's own platform already holds, plus a short tag for their company, and it is the one to use if you want certainty:
@jeremy_warfield_solobrands can you confirm the rollout date?
Do not try to work it out from someone's email address. Mailbox names vary, so the same person could be jeremy_warfield_solobrands in one company and jwarfield_solobrands in another. Read it off the list.
Some channels also offer a short spelling. Where one exists, the list shows it first and puts the long spelling in brackets after it, as in the example above. The short spelling is the person's first name, and it appears only when nobody else on either side of the bridge answers to it:
@jeremy can you confirm the rollout date?
Some channels additionally resolve a partial name of three characters or more, when it matches exactly one person on the far side and nobody on your own side. Where that is switched on, @jere finds Jeremy.
If a person's line shows only one spelling, type that one. On a channel with partial names switched on, a unique shortening of it will also resolve.
Mentioning a Slack person from Microsoft Teams
This direction works the same way, with one thing to watch.
The Teams compose box will not help you. Its popup lists colleagues in your own Microsoft 365 tenant, so the Slack people on the other side of the bridge never appear in it, however far you scroll. Do not pick from that popup.
Instead, type the name as plain text and send the message:
@paul the invoice is attached
SlackBridge reads the plain text of the message after it is sent and turns it into a real Slack mention. Paul gets a normal Slack notification.
If Teams turns your typing into one of its own mention chips, that chip is a Teams identity and SlackBridge cannot use it. Delete the chip and type the name as plain text. Pasting the name instead of typing it avoids the popup entirely.
The same trap exists in Slack
It is rarer, because the far-side names are not in Slack's autocomplete either. But if a colleague in your own Slack workspace happens to have the same username as the name you are typing, Slack may turn it into a chip pointing at them. Your colleague gets the notification and the person you meant does not. The message still bridges either way, with the name arriving on the Teams side as readable text.
You can see it happen: the chip shows your colleague's display name rather than the plain text you typed. Delete it and retype the name, or paste it.
Where do the names come from?
From the membership of the two bridged channels, and nowhere else.
SlackBridge reads the Slack channel's member list and the Microsoft Teams channel's member list, then derives one addressable name per person from the account name each platform already has: the Slack username on one side, and the mailbox name from the Microsoft 365 account on the other. Display names are never used to invent a name, because two people can have the same display name.
The list refreshes automatically, so someone who joins the channel usually becomes addressable within an hour. These are excluded and never addressable:
- Bots and apps
- Deactivated or disabled accounts
- Microsoft Teams guest accounts, including external guests whose mailbox looks like a company address
- Anyone an administrator has opted out
SlackBridge also refuses a name that is not unique. If two people would end up with the same addressable name, neither is advertised, so a mention can never notify the wrong person by accident. The same applies to a name that already belongs to someone on the sender's own side of the bridge.
When SlackBridge cannot confirm someone's account status, it leaves them off the list rather than guess. If a colleague you expected is missing from the channel's list, that is why, and support can tell you which rule applied.
What if I get the name wrong?
Nothing bad happens. The message bridges normally and nobody is notified.
SlackBridge also shows you the names it does recognize, and where that note appears depends on which platform you are typing in:
- In Slack, it is a private message that only you can see.
- In Microsoft Teams, it is a reply from the SlackBridge bot in your message's thread, and the channel can see it. Microsoft Teams has no private bot message, so this is the only way to reach you there.
Either way you see it once and then not again for a month, so it never becomes noise on a busy bridge.
Where mentions do not work
Private and shared Microsoft Teams channels
Mentions do not work in either direction in a private or shared Teams channel, because SlackBridge cannot confirm who is in one.
To let someone address a person, SlackBridge first confirms that person is actually in the bridged channel. For a standard Teams channel, the team's member list answers that. For a private or shared channel, it does not, and reading the channel's own member list needs a Microsoft Graph permission (ChannelMember.Read.All) that SlackBridge does not request. Rather than address someone who might not be in the channel, SlackBridge does not build a name list for that channel at all.
Everything else about the bridge works normally in a private or shared Teams channel. If mentions matter to your team, bridge a standard Teams channel instead.
Messages that carry a file
If your message has a file attached and your bridge copies files across to the other platform, that message arrives without mentions. The name you typed is delivered as readable text and nobody is notified by it.
Not every bridge copies files. Most simply name the attachment in the bridged message, as in shared a file: contract.pdf, and those messages carry mentions normally.
You can tell the two apart by what arrives on the receiving side. If the file itself is there to open, it was copied, and that message carries no mentions. If you only see its name written out, it was named, and mentions in that message work as usual. A file copied from Slack into Microsoft Teams arrives as a card with a button to open it; a file copied from Teams into Slack arrives as a normal Slack file upload.
If you want to notify someone about a file on a bridge that copies files, post the file, then mention them in a separate message in the same channel.
@channel, @here, and @everyone
Slack's three broadcast keywords arrive in Microsoft Teams as readable text (@channel, @here, @everyone). They do not fire a Teams channel-wide or team-wide notification, for two reasons:
- Permissions. Issuing a team-wide notification on behalf of every member is a much heavier permission than SlackBridge asks for at install time. See What permissions does SlackBridge ask for, and why?.
- Intent. Someone who types
@channelin Slack usually means the people in that Slack channel. Re-broadcasting to everyone on the Teams side would amplify the message beyond what they asked for.
The reverse is also true: a Teams channel or team notification does not become a Slack broadcast.
Channel names and user groups
A Slack #general mention arrives in Microsoft Teams as the readable text #general, and a Teams channel link arrives in Slack as the channel's name. Neither becomes a clickable link, because the destination platform does not have that same channel. Slack user-group mentions such as @design-team bridge as text for the same reason.
Are there limits on how many mentions a message can carry?
Yes, and they exist so a bridge cannot become a notification firehose:
| Limit | Value |
|---|---|
| Mentions emitted per message | 5 |
| Mentions one sender can emit per hour | 20 |
| Times one person can be mentioned per hour | 10 |
Past any of these, that message carries no mentions at all. It still bridges, and every name in it arrives as readable text. SlackBridge does not deliver some of the mentions and drop the rest, because a partly-delivered message is worse than a message everyone has to read. A bridged message counts as one message toward your plan's usage regardless of how many mentions it carries.
Switching mentions on or off
Mentions were switched on for existing bridged channels in September 2026. If you have set up a bridge since then and the name list has not appeared in the channel, contact SlackBridge support and we will switch it on.
If you would rather a bridge did not carry mentions, or you want one person made unaddressable, contact support with the bridged channel and we will change it.
Frequently asked questions
If I @mention someone in Slack, will they get notified in Microsoft Teams?
Yes, as long as they are a member of the bridged Microsoft Teams channel and that channel is a standard Teams channel. SlackBridge matches the name you typed against the people in the bridged channel and emits a real Teams mention, which notifies that person in Teams exactly as a Teams colleague's mention would. If the name does not match anyone, nothing is notified and the message still bridges normally.
What do I type to mention someone on the other platform?
Type a name exactly as SlackBridge lists it in the channel. Every channel lists a long spelling that always works, for example @jeremy_warfield_solobrands. Some channels also offer a short one, the person's first name, shown first on the list with the long spelling in brackets after it. SlackBridge posts that list into the channel when mentions are first switched on, and shows it again if you type a name it does not recognize (privately in Slack, as a visible bot reply in your thread in Microsoft Teams).
Why doesn't Microsoft Teams suggest these names while I type?
The Teams compose box only suggests people in your own Microsoft 365 tenant, and the people on the Slack side of the bridge are not in it. Type the name as plain text and send the message. Do not pick anything from the Teams suggestion popup. SlackBridge reads the plain text after the message is sent and converts it into a real Slack mention.
Do mentions work in a private or shared Microsoft Teams channel?
No. Confirming who is in a private or shared Teams channel needs a Microsoft Graph permission that SlackBridge does not request, and SlackBridge will not let someone address a person it cannot confirm is in the channel. Mentions are switched off in those channels in both directions. The rest of the bridge works normally. Move the bridge to a standard Teams channel if you want mentions.
Does SlackBridge translate @channel, @here, or @everyone keywords?
No. Slack's special-mention keywords arrive in Microsoft Teams as readable text such as @channel. They do not trigger a Teams channel-wide or team-wide notification. Sending a broadcast notification on behalf of every member of a team is a far heavier permission than SlackBridge asks for, and it would amplify a message beyond what the sender intended.
Where does SlackBridge get the list of names?
From the membership of the two bridged channels. SlackBridge reads the Slack channel's members and the Microsoft Teams channel's members and refreshes that list automatically about once an hour. Bots, deactivated accounts, and Microsoft Teams guest accounts are excluded.
If I get a name wrong, does everyone see me being corrected?
In Slack, no. The note listing the recognized names is private to you. In Microsoft Teams it is a reply from the SlackBridge bot in your message's thread, and the channel can see it, because Microsoft Teams gives a bot no way to message one person privately in a channel. You get it once and then not again for a month.
Does a message with a file attached still carry a mention?
It depends on whether your bridge copies files across to the other platform. If it does, that message arrives without mentions: the name is delivered as readable text and nobody is notified by it, so post the file and then mention the person in a separate message. Most bridges do not copy files, they simply name the attachment in the bridged message, and those messages carry mentions normally. To tell which you are looking at, check whether the file itself arrived or only its name.
Can someone be removed from the list?
Yes. An administrator can opt an individual out, and that person stops being addressable from the other platform. Ask SlackBridge support and name the person and the bridged channel.
Are channel-name mentions like #general bridged?
The channel name is preserved as readable text. A Slack #general mention arrives in Teams as #general. Neither side becomes a clickable link on the destination platform, because the destination platform does not have that same channel.
Does this send anyone's email address across the bridge?
No email address is bridged or displayed. On the Microsoft Teams side the addressable name is derived from the mailbox name on the person's Microsoft 365 account, so for many organizations it will resemble the part of their address before the at sign. The domain is never used.
For each bridged channel SlackBridge keeps a list holding, per person, their addressable name, their display name, and their Slack or Microsoft user ID, alongside the channel IDs it was built from and when it was last refreshed. It also records why anyone was left off, for example that they are a guest or that their name collided with someone else's.
Where partial-name matching is switched on, SlackBridge additionally stores the name fragments a person could be typed as, which for the Microsoft Teams side includes their mailbox name, and it stores those for everyone in the channel rather than only the people who are addressable.
No email domain is stored, no message content is stored against a person, and the whole list is rebuilt from scratch on every refresh. See How long does SlackBridge store my messages and data?.
Still need help?
If a mention is not working the way you expect, contact SlackBridge support and include:
- The exact text you typed, and on which platform
- A screenshot of how the message arrived on the other platform
- Whether the Microsoft Teams channel is standard, private, or shared
We aim to respond within one business day.