Can Slack and Teams integrate?

Yes! While there's no native integration between Slack and Microsoft Teams, SlackBridge provides a seamless bridge. Messages you send in Slack appear in your client's Teams channel, and their replies come back to Slack in near real time.

How secure is SlackBridge?

SlackBridge uses OAuth 2.0 for authentication and the official Microsoft Graph API for Teams integration. We're 100% serverless, messages relay in real-time and full message content is not stored. Temporary metadata is retained for up to 7 days to support thread synchronization. All connections are encrypted on enterprise-grade infrastructure.

Do my clients need to install anything?

Your client contact receives an invite link and can approve the connection themselves or forward it to their IT administrator. Depending on setup method, their admin may also add the SlackBridge bot to Teams once. End users install nothing and message you normally in Teams while you stay in Slack.

What's the difference between SlackBridge and migrating from Slack to Teams?

Migration means abandoning Slack entirely and moving to Teams. SlackBridge lets you keep using Slack while communicating with Teams users. No migration, no retraining, no lost integrations.

Can I connect to multiple Teams tenants?

Yes! Agencies and consultancies can connect their single Slack workspace to multiple client Teams tenants. Each client connection is managed separately with its own channel mappings.

Can we share files between Slack and Teams?

Yes. With file sharing on, the file itself is relayed into the mapped channel in both directions; with it off, a file shared on one side is announced on the other by name and type. Images pasted directly into a Teams message are copied too, arriving in Slack as real images. New Full Integration installs have it on from the start, covered by the Microsoft administrator's consent at install, and any admin can turn it off per connection in the dashboard. Connections created before September 2026, and Core Bridging connections, stay announcement-only until someone enables it: the Slack workspace authorizes two file scopes and the Microsoft Teams administrator approves the request from the Organizations table. Files pass through in transit and are never stored on SlackBridge servers.

How much does Slack Teams integration cost?

SlackBridge is free to start with 1 external organization and 1 linked channel. Our Pro plan at $49.99/month includes 2 external organizations and 5 linked channels. Need more? Pro users can add an organization for $10/month (which includes an extra channel) or a channel for $5/month. Pricing is based on external organizations and linked channels, not on message volume or seat count.

Is this the same as Slack Connect?

No. Slack Connect requires both parties to use Slack. SlackBridge works when your client uses Microsoft Teams and doesn't want another app. They stay in Teams, you stay in Slack.

Downloads

The SlackBridge app package for Microsoft Teams, and how to add it to your organization.

SlackBridge for Microsoft Teams

App package (zip) for your organization's Teams app catalog

Download app package

Microsoft requires that this package be uploaded by one of your own Teams administrators. External services cannot add it to your catalog remotely, so this is a one-time step per organization. SlackBridge is not listed in the Teams Store, so this upload is how the app reaches your organization.

Download the Teams app package

Use the button above. The zip contains the SlackBridge app manifest and icons. Do not unzip it.

Upload it to your organization's app catalog

A Teams administrator opens the Teams admin center (admin.teams.microsoft.com), goes to Teams apps, then Manage apps, selects Upload new app, and chooses the downloaded zip. Alternatively, in the Teams client: Apps, Manage your apps, Upload an app, then "Upload an app to your org's app catalog".

SlackBridge finishes the setup

If your organization granted admin consent during setup, SlackBridge installs the app into your bridged team automatically within a few minutes. You can also add it to the team manually from your catalog. Then send a test message in either direction.

Why this matters: messages from Slack are posted into Teams by this app. Without it, Slack to Teams delivery cannot work, while Teams to Slack may still function. If you hit a permissions error mentioning Teamwork.Migrate.All, this upload is the fix; that permission is not required and should not be granted.

Questions or stuck on a step? Contact Support