Skip to content

Teams

Connect Microsoft so Teams meeting transcripts, chat threads, and OneDrive documents can be part of what Mention learns from. This is one integration: a single Microsoft connection covers all three, and your organization can connect one Microsoft account to Mention.

What gets synced

Meeting transcripts

  • Transcripts from scheduled Teams meetings organized by a member of your Mention organization, regardless of who connected Microsoft or who attended. Meetings started with Meet now are not exposed by Microsoft's API and are not picked up.
  • Only meetings that end after you connect are picked up — there is no historical backfill of transcripts from before the connection.
  • Each transcript is a single Transcript asset with speaker turns preserved so context — who said what — stays clear. Participants inside your organization are matched to their Mention account; external guests appear under the name they used to join and are not matched to a person.
  • Reading transcripts at all needs a one-time tenant setup by your Teams admin — see Tenant setup. Until it is done, no transcripts sync, whoever connected.

Channel and chat threads

  • A thread is captured on demand when someone @-mentions the Mention bot inside the thread. Any user in your tenant who can reach the bot can do this — capture is not limited to admins.
  • The thread is ingested as a Conversation asset immediately — Conversations are activated on capture, with no separate activation step. See Managing Assets.
  • This lets you bring in specific discussions without subscribing Mention to every channel.

OneDrive documents

  • Mention discovers supported documents in the connected account's OneDrive: Word (.docx), PowerPoint (.pptx), and Excel (.xlsx) files, PDFs, and plain-text, Markdown, and HTML files.
  • Legacy Office formats (.doc, .xls, .ppt) and other file types (images, video, archives, and so on) are skipped.
  • Office files are imported with their structure — headings, sections, and text — preserved.

How to connect

  1. Add the Microsoft integration as a source in Mention.
  2. Sign in with a Microsoft account that can authorize the app for your tenant (your IT team can confirm who has the right role).
  3. Approve the requested permissions on the Microsoft consent screen. This covers OneDrive, chat capture, and the connecting account's own meetings.
  4. You are then sent to a second, tenant-level admin consent screen. Accepting it is what lets Mention read transcripts for meetings organized by any member of your organization. If you decline, the connection still works, but transcripts are limited to meetings the connecting account organized.
  5. Optionally choose a start date so only documents modified on or after that date are discovered.
  6. Have your Teams admin complete the tenant setup below.
  7. After connecting, review the discovered documents and transcripts and activate the ones Mention should use.
  8. To capture a thread, @-mention the Mention bot inside that thread in Teams.

Already connected before admin consent existed, or declined it the first time? Open the Microsoft source under Sources and click Reconnect next to Consent needed on the Teams transcripts card, then accept the admin consent screen. Nothing else about the connection changes.

If authorization fails, check that your tenant's admin consent settings allow the integration. See Connecting sources.

Tenant setup

Microsoft keeps transcript access off by default in every tenant, and there is no switch for it in the Teams admin center. Until a Teams admin turns it on, Mention cannot read any transcript, and the Microsoft source page reports Transcript access off. Three PowerShell commands, run once by a Teams administrator, complete the setup:

Connect-MicrosoftTeams
Set-CsTeamsMeetingConfiguration -Identity Global -EnableGraphTranscriptAccess $true -EnableAttributedTranscripts $true
New-CsApplicationAccessPolicy -Identity Mention-Transcripts -AppIds "<Mention application (client) ID>"
Grant-CsApplicationAccessPolicy -PolicyName Mention-Transcripts -Global
  • EnableGraphTranscriptAccess lets transcripts be read through Microsoft's API. Off by default; nothing works without it.
  • EnableAttributedTranscripts puts speaker names in the transcript. Without it every line is recorded as an unknown speaker.
  • The application access policy lets Mention read meetings organized by members other than the connecting account. Mention's application (client) ID is shown on the admin consent screen; Mention support can also provide it.

Changes can take up to 30 minutes to take effect. On macOS, the MicrosoftTeams PowerShell module's interactive sign-in fails with a kernel32 load error; use Connect-MicrosoftTeams -UseDeviceAuthentication instead.

Checking the setup. The Microsoft source page in Mention shows a Teams transcripts status: Transcript access off, Consent needed, Access policy missing, Speakers unnamed, or Healthy with the number of transcripts found in the last 90 days. Each names the step above that is still missing.

Things to know

  • Not every meeting produces a transcript; it depends on tenant transcription settings, recording policies, and host behavior in Teams.
  • After the tenant setup, Mention can read transcripts for meetings organized by your organization's members regardless of who attended. It does not see meetings organized by people outside your Mention organization, or Meet now meetings.
  • Transcript discovery runs independently of, and ahead of, document syncing, so your meetings surface quickly even when a large OneDrive is connected to the same account.
  • Microsoft's change notifications expire and are renewed daily by Mention. If they lapse — a revoked consent, a reconnect, a tenant change — the daily sync carries the integration until they are re-established, so content is delayed rather than lost.
  • @-mention capture requires the bot to have access to that conversation — your Teams admin controls where the bot can be added. Anywhere the bot is reachable, any tenant user can capture a thread, so treat sensitive channels carefully and only enable bot access where your security and compliance policies allow.
  • The account you connect with must be able to open a file in OneDrive for it to be a candidate to import. Mention does not see content the account cannot access.
  • Speaker labels in transcripts and threads are aligned with the participant information Teams provides.
  • Access rules apply per channel for channel threads, to all chats together, to all meeting transcripts together, and per first two folder levels for OneDrive files. See Source access.

Sync behavior

What Microsoft pushes to Mention differs per resource, so each of the three kinds of content keeps its own timing:

  • OneDrive documents — Microsoft notifies Mention when the connected account's OneDrive changes, so an edit, a rename, a move or a deletion is picked up within minutes. Files shared with the connected account from someone else's drive are not covered by those notifications; they are reconciled by the daily sync, which also recovers anything a missed notification would have lost.
  • Meeting transcripts — once your tenant has granted admin consent, Microsoft notifies Mention as each transcript becomes available, and Mention fetches it straight away. Notifications only cover transcriptions started after the connection was made; anything earlier, and any tenant that has not granted admin consent, is covered by the daily sync instead, which discovers transcripts through the connecting account's calendar.
  • Channel and chat threads — unchanged: a thread arrives when someone @-mentions the Mention bot in it. Microsoft's message notifications need permissions Mention does not ask for, so nothing is captured without that @-mention.

You can refresh manually whenever you want a meeting or document edit to appear immediately.

If you set a start date when connecting, Mention only discovers documents modified on or after that date — useful for keeping large drives fast to sync. Leave it empty to discover all supported documents regardless of age.

Activation limit

You can activate up to 2,000 documents per integration. Meeting transcripts and captured conversation threads do not count toward this limit.