Skip to main content
Microsoft Teams brings your team channels into Brink — channel messages with replies threaded under the message they answer, arriving near-real-time. Who can connect: organization owners and admins.
Teams connects with work or school accounts (Microsoft 365). Personal Microsoft accounts aren’t supported.

​
Connect Microsoft Teams

1

Open Integrations

On the Integrations page (Organisation view), click the Microsoft Teams card, then Connect Microsoft Teams in the drawer.
Microsoft Teams connection drawer with a Connect button

The Microsoft Teams drawer before the first account is connected

2

Authorize with Microsoft

Approve the requested permissions: read channel messages (ChannelMessage.Read.All) and list teams and channels (Team.ReadBasic.All, Channel.ReadBasic.All), plus your basic profile (User.Read).
In most Microsoft 365 tenants these are admin-consent permissions — a Microsoft 365 administrator may need to approve them before the connection works. If the channel picker comes up empty after connecting, missing admin consent is the usual cause.
3

Bind channels

On the Projects page, open the project’s Integrations tab and bind each project’s Teams channel. Use the resource picker — a Teams binding needs both the team and the channel, and the picker handles that pairing for you.
Add scope binding form on the Projects page

Add scope binding on a project's Integrations tab

​
What gets synced

Channel messages, with replies threaded under their parent message and author names resolved. New messages arrive near-real-time — Brink subscribes to each bound channel and renews the subscription automatically — with the regular scheduled sync as a backstop.

​
Use your own Microsoft app

By default, Teams connects through Brink’s Microsoft app. Owners and admins can instead point Teams at their own Microsoft Entra ID (Azure AD) app registration — useful when your tenant restricts which third-party apps may be consented to, or when your security team wants the app registration inside your own directory.
This setting is specific to Teams. Pointing Teams at your own app does not change how Outlook or Outlook Calendar connect — they keep using Brink’s Microsoft app unless you change them separately.
You’ll need someone who can create app registrations in the Microsoft Entra admin center and grant admin consent. It takes about ten minutes, once per organization.

​
Create the app registration

1

Create a new registration

In the Microsoft Entra admin center, go to Identity → Applications → App registrations and click New registration. Give it a recognizable name such as Brink Connector.
2

Set the supported account types

Choose Accounts in any organizational directory (Any Microsoft Entra ID tenant — Multitenant).
This one matters. Brink signs users in through Microsoft’s organizations endpoint, and a single-tenant registration is rejected there — Microsoft returns AADSTS50194: Application is not configured as a multi-tenant application. Only accounts you invite can ever use the app, so multitenant here does not widen who can sign in to your Teams data.
3

Add Brink's redirect URI

In Brink, open Integrations → Microsoft Teams → Connection method → Use your own Microsoft Teams developer app and copy the Redirect URI shown there (it ends in /oauth/callback/teams).In the registration, under Authentication → Add a platform, choose Web and paste the URI exactly — it must match character for character.
4

Add the delegated Graph permissions

Under API permissions → Add a permission → Microsoft Graph → Delegated permissions, add all of these:Then click Grant admin consent for your tenant.
Without offline_access the connection dies about an hour after it’s made and every later sync fails. Without Team.ReadBasic.All the channel picker lists nothing.
5

Create a client secret

Under Certificates & secrets → Client secrets → New client secret, add a secret and copy its Value immediately — Microsoft shows it once and only once. (Copy the Value column, not the Secret ID.)Note the expiry you choose: when the secret expires, Teams connections stop refreshing until you create a new one and save it in Brink.
6

Copy the client ID

On the registration’s Overview page, copy the Application (client) ID.

​
Connect it to Brink

1

Save the credentials

Back in the Brink drawer, paste the Microsoft Teams OAuth client ID and Microsoft Teams OAuth client secret, then click Save credentials. Secrets are write-only — after saving, the value is shown masked and never displayed again.The Connection method card then reads Your own Microsoft Teams app · In use.
Connection method panel with redirect URI, client ID and client secret fields

Connection method — your own Microsoft Teams app in use

2

Connect

Click Connect Microsoft Teams and authorize as usual. From here everything is the same as the standard flow, including binding channels.
To go back to the standard connection, choose Use Brink’s app instead in the same section. Existing connections keep working — credentials take effect on the next connect.
Changing credentials on an already-connected account may invalidate the existing authorization. If the connection shows Needs attention afterwards, click Reconnect to re-authorize against the new app.
If something goes wrong: a redirect URI mismatch means the URI in Entra doesn’t exactly match Brink’s — re-copy it from the drawer. AADSTS50194 means the registration is still single-tenant. An empty channel picker after a successful connect almost always means admin consent hasn’t been granted.

​
Notes

  • Microsoft provides no way for Brink to revoke its own access. Disconnecting deletes Brink’s stored credentials; a Microsoft 365 admin can also remove the app’s access in Entra ID.
  • Only channels you bind are read. Chats and direct messages are never synced.