Microsoft Teams Integration

Connect Microsoft Teams to Brief for channel signal, then chat with Brief directly in Teams — decisions, thread context, and Adaptive Cards included.

Last updated: July 5, 2026

Microsoft Teams is two things to Brief: a signal source (channel conversations you choose to share) and a full chat surface — you can talk to Brief, capture decisions, and approve agent actions without leaving Teams.

What does Brief capture from Teams?

  • Channel messages — from the teams/channels you choose to share during setup
  • Thread context — the surrounding channel conversation, so an in-thread reply to Brief carries the discussion with it
  • Decisions — captured when you talk through a choice with Brief in a Teams conversation
  • Speaker attribution — who said what, matched to a Brief account where possible

Why should I connect Teams to Brief?

Signal from where your team already talks

Product and customer context surfaces in Teams channels constantly. Connecting lets Brief fold that into the same product understanding it builds from your other tools — no separate export step.

A chat surface without switching tools

Once Brief is in your Teams tenant, you can ask it questions, review its answers, and confirm decisions in the same window you're already working in.

Context-aware replies

Brief reads the surrounding thread before it answers, so a reply in the middle of a channel conversation understands what came before it — not just the single message that mentioned it.

How do I set up the Teams integration?

Setup time: 2-3 minutes
Initial sync: 1-2 minutes
Updates: Periodic sync (no instant webhook for Teams)

Steps

  1. Go to Integrations in Brief
  2. Find Microsoft Teams and click Connect
  3. Authorize Brief in Microsoft's OAuth flow
  4. Choose channels to share — select which teams/channels Brief can read for signal, or skip if you only want the chat surface
  5. Done! Brief starts syncing selected channels

This OAuth connection governs signal ingestion. Getting the Brief bot itself into Teams (so you can chat with it) is a separate, one-time step — see below.

Chatting with Brief in Teams

Brief's Teams bot mirrors the Slack chat experience: @mention Brief in a channel, message it directly, or add it to a group chat. Answers render as Adaptive Cards, so tables, decision proposals, and follow-up prompts show up as native Teams UI rather than plain text.

  • Thread context — in a channel, Brief pulls in the surrounding conversation before it replies, so it understands what's already been discussed
  • Decision capture — talk through a choice with Brief in a thread and it proposes a structured decision card with Confirm / Edit actions, the same pattern as Slack's /decide
  • Tool-approval cards — when Brief needs to take a gated action (an agent-management change, a bulk operation), it sends an Approve / Deny card rather than acting silently
  • Personal, group, and channel scope — the bot works in 1:1 messages, group chats, and team channels
Thread context is available in channel conversations. Personal messages and group chats don't have a Graph-readable thread, so Brief answers from the message itself in those scopes.

Getting Brief into your Teams tenant

If your organization already uses Brief, an admin can install the Brief app from your Teams admin center (or your own Teams client) and add it to a team, channel, or chat. The first time you add Brief to a scope, Teams shows a one-time permission prompt.

If your organization hasn't connected Brief yet, ask a workspace admin to connect it — an admin needs to install the Brief app and link your Teams tenant before Brief can respond in your organization.

Common Issues

"Your organization isn't set up with Brief yet"

Cause: No one at your organization has connected Brief to your Teams tenant. Fix: Ask a workspace admin to connect Brief, then try again.

"I couldn't look up your account just now"

Cause: A temporary lookup hiccup — this is not the same as having no account. Fix: Try again in a moment. If it keeps happening, contact support.

Brief replies with a stripped-down card

Cause: The full answer exceeded Teams' card size limit, so Brief sent a compact version with a link to view the rest in Brief. Fix: No action needed — click through to see the complete answer.

Channel replies don't seem to know the thread

Cause: Brief couldn't read the channel's message history for that reply (a permissions or connectivity hiccup). Fix: Confirm Brief still has access to the channel. If it persists, contact support — Brief still answers, just without the surrounding context.

What's Next?

Now that Teams is connected: