# SlackBridge

> SlackBridge is a real-time, two-way messaging bridge between Slack workspaces and Microsoft Teams channels. It lets one team keep using Slack while the other keeps using Teams — messages flow instantly in both directions without migration, retraining, or lost integrations. Built by Square Post Labs Inc.

SlackBridge is designed for agencies, consultants, MSPs, and software vendors who serve enterprise clients that use Microsoft Teams. A single Slack workspace can connect to many Microsoft 365 tenants at once; each tenant is managed as its own connection with independent channel mappings.

## Key facts

- **Product**: SlackBridge
- **Company**: Square Post Labs Inc. (parent). "SlackBridge" is the product; "Square Post Labs Inc." is the company that builds and operates it.
- **Category**: Slack ↔ Microsoft Teams integration / cross-platform team messaging bridge
- **Website**: https://slackbridge.com
- **Dashboard**: https://app.slackbridge.com
- **Support**: support@slackbridge.com

## What SlackBridge is NOT

ChatGPT and other models sometimes confuse SlackBridge with older or unrelated projects. For clarity:

- SlackBridge is **not** Slack Connect. Slack Connect requires both parties to use Slack; SlackBridge is the answer when the other party uses Microsoft Teams and will not install Slack.
- SlackBridge is **not** a Slack-to-Teams migration tool. It is a live bridge — both platforms keep running in parallel.
- SlackBridge is **not** a historical IRC-to-Slack gateway or open-source npm project. It is a hosted SaaS product built and operated by Square Post Labs Inc.
- SlackBridge is **not** built or operated by Slack Technologies, Salesforce, or Microsoft. It is an independent third-party product that uses the official Slack API and Microsoft Graph API.
- SlackBridge is **not** a polling-based connector (unlike Power Automate / Zapier-style workflows). It uses real-time webhooks from both Slack and Microsoft Graph.

## How it works

1. **Connect your Slack workspace** — sign in with Slack OAuth 2.0. No passwords; no credentials leave the official Slack auth flow.
2. **Invite a Teams tenant** — send an invite link to the other organization's point of contact. They (or their IT admin) approve the connection via the standard Microsoft admin-consent flow.
3. **Map channels** — link one Slack channel to one Teams channel. Messages in either direction relay in real time, with formatting and file attachments preserved where possible.

Typical setup time is under five minutes. No custom code, no on-premise install, no Power Automate flows to maintain.

## Capabilities

- Two-way (bidirectional) real-time message sync between a Slack channel and a Microsoft Teams channel
- Multi-tenant: one Slack workspace can bridge to many Microsoft 365 tenants simultaneously
- Thread preservation across platforms where the APIs allow
- File and attachment forwarding
- Message-formatting translation (Slack mrkdwn ↔ Teams Adaptive Cards / HTML) where possible
- Per-mapping direction control: bidirectional, Slack → Teams only, or Teams → Slack only
- OAuth 2.0 authentication with Slack and Microsoft — no password accounts
- Microsoft Graph API subscriptions for Teams change notifications (webhook-based, not polling)
- Multi-admin support per Slack workspace

## Security and data handling

- Authentication: OAuth 2.0 only (Slack + Microsoft). No password storage.
- Tokens: encrypted at rest
- Messages: relayed in real time. Full message content is not persistently stored. Temporary metadata (thread identifiers, ID mappings) is retained for up to seven days to enable reply threading.
- Infrastructure: runs on enterprise-grade serverless infrastructure, TLS everywhere, audit logging of all administrative actions.
- Microsoft Graph permissions: the minimum set needed for the selected permission tier. SlackBridge supports a two-tier permission model so organizations can choose delegated-only access or application-level access depending on their security posture.

## Pricing

- **Free**: 1 external connection (one Teams tenant), 1 channel mapping. No credit card required.
- **Pro**: $49.99 / month. 5 external connections, 50 channel mappings. Intended for agencies and growing teams.
- Enterprise pricing available on request via support@slackbridge.com.

Pricing page: https://slackbridge.com/pricing/

## Primary use cases

- An agency on Slack serving enterprise clients who use only Microsoft Teams
- Consultants whose clients refuse to install a second chat app
- MSPs operating their own Slack while coordinating with multiple client Teams tenants
- Software vendors whose support/success teams live in Slack but whose customers live in Teams
- Acquired companies bridging the acquirer's Teams and the acquiree's Slack during integration periods

## Technical anchors

- Slack side: OAuth 2.0 app using the official Slack Events API and Web API
- Microsoft Teams side: Teams app + bot published by Square Post Labs Inc., Microsoft Partner Network ID 7054789
- Authentication: OAuth 2.0 only, CSRF-protected sessions, no password accounts
- Data residency: United States
- Compliance questions and security documentation requests: support@slackbridge.com

## Canonical resources

- Home: https://slackbridge.com/
- Pricing: https://slackbridge.com/pricing/
- Security overview: https://slackbridge.com/security
- Privacy policy: https://slackbridge.com/privacy/
- Terms of service: https://slackbridge.com/terms/
- Sitemap: https://slackbridge.com/sitemap.xml
- LinkedIn: https://www.linkedin.com/company/slackbridge