Microsoft Teams User Connector
Connect your own Microsoft Teams account to Abacus.AI so that ChatLLM Teams chats with RouteLLM, the Abacus AI Agent and Custom Chatbots can work with your Microsoft Teams data under your own identity. The connector can only see what your Microsoft Teams account can see, and the activity is recorded against your account in Microsoft Teams.
Microsoft blocks ordinary users from consenting to the Abacus.AI app on their own. Before anyone else in your tenant can connect Microsoft Teams, a Microsoft Entra admin must create the connector once and tick the "Consent on behalf of your organization" checkbox on Microsoft's Permissions requested screen, then click Accept.
This is not the same as the Grant admin consent button in the Entra admin center. Once the admin has ticked the checkbox, every user in that tenant can sign in and create their own connector freely. Until then Microsoft stops them with "Need admin approval".
See Microsoft Entra Tenant Consent for the full walkthrough.
Once connected, the Teams Tool can, for example:
- Read and search your chats and the channel posts of the teams you belong to
- Send chat messages and channel posts, and create new chats
- Find meetings on your calendar
- Retrieve and summarize the transcripts of Teams meetings you organized or were invited to. This needs a Microsoft Teams admin to enable transcript access for your tenant first.
Prerequisites​
- Access to ChatLLM Teams
- A Microsoft 365 work or school account with Microsoft Teams (personal Microsoft accounts are not supported)
- For meeting transcripts: a Microsoft Teams admin who can complete Enable meeting transcripts
- To restrict scopes or use your own Entra app: administrative access in Abacus.AI to create connectors
Scopes and permissions​
By default, the connector uses the Abacus.AI application and requests the delegated Microsoft Graph permissions below. You review them on Microsoft's consent screen when you connect. Delegated permissions act on behalf of the signed-in user, so the connector can never see more than your own Microsoft Teams account can.
| Permission | Purpose |
|---|---|
User.Read, openid, profile, offline_access | Sign you in, read your profile, and keep the connection active without signing in again |
User.Read.All | Look up other users in your organization, for example to @mention them |
Chat.Read, Chat.ReadWrite, Chat.Create | Read your chats, send and delete chat messages, and create new chats |
ChannelMessage.Read.All | Read channel posts |
ChannelMessage.Send, ChannelMessage.ReadWrite | Post channel messages and replies, and edit or delete your channel messages |
Group.Read.All | List the teams and channels you belong to |
Calendars.Read | Find meetings on your calendar |
OnlineMeetings.Read | Look up the Teams meeting behind a calendar event |
OnlineMeetingTranscript.Read.All | Read the transcripts of meetings you organized or were invited to |
Several of these permissions, including OnlineMeetingTranscript.Read.All, ChannelMessage.Read.All, Group.Read.All and User.Read.All, require admin consent. This is why an Entra admin has to set the connector up first.
To revoke access later, remove Microsoft Teams from Profile → User Connectors. You can also revoke the Abacus.AI app from your Microsoft account settings.
Restrict scopes or use your own Entra app (config connector)​
An organization administrator can create a Microsoft Teams config connector. Every user-level Microsoft Teams connection in the organization then uses the scopes, and optionally the Entra app, stored there instead of the defaults above.
- In the Abacus.AI interface, click your profile picture in the top right corner and select Manage Connectors (or open the Connected Services Dashboard).
- Click Add New Connector and choose Teams from the list.
- Pick an Auth Type:
- Basic keeps the Abacus.AI application. Turn the Config Only toggle on, then under Scopes select the scopes users may request.
- Custom OAuth uses your own Microsoft Entra app. Turn the Config Only toggle on and enter your app's Client ID and Client Secret. Enter a Tenant ID too if your app is single-tenant; otherwise it defaults to
common. You can also list the scopes to request in Scopes, separated by commas. Add the redirect URIhttps://abacus.ai/oauth/callbackto your app (Microsoft documentation), and grant admin consent for its delegated permissions under App registrations → your app → API permissions → Grant admin consent.
- Click Create.
Always turn the Config Only toggle on here. Without it, the form sets up the organization-level Microsoft Teams connector (the Abacus.AI bot in Teams) instead of a configuration for user connectors.
On a Basic config connector, the Scopes list starts with only the sign-in scopes selected (User.Read, openid, profile, offline_access). For users to read meeting transcripts, also select Calendars.Read, OnlineMeetings.Read and OnlineMeetingTranscript.Read.All.
Users who connected Microsoft Teams before the config connector was created or changed must remove it and connect it again from Profile → User Connectors for the new scopes to take effect.
Enable meeting transcripts (Microsoft Teams admin)​
The Teams Tool reads meeting transcripts through the Microsoft Graph transcript API. Microsoft turns Graph access to transcripts off by default in every tenant, whatever permissions an app has been granted. Until a Microsoft Teams admin completes the steps below, chats and channel posts work normally, but every transcript request fails with 403 Forbidden.
These steps are done once per tenant, on the customer side, by an account with the Teams Administrator or Global Administrator role.
Step 1 — Turn on Microsoft Graph access to transcripts​
- Sign in to the Microsoft Teams admin center.
- In the left navigation, go to Meetings → Meeting settings.
- Under Transcript API access, turn the Microsoft Graph access toggle On.
- Select Configure and turn the Include speaker attribution toggle On.
- Save your changes.
The Teams Tool requests transcripts in the speaker-attributed WebVTT format, which shows who said what. Include speaker attribution is off by default. While it is off, Microsoft rejects the request with 403 Forbidden (SpeakerAttributionNotAllowed), even though Graph access is on.
To do the same with PowerShell, use the latest version of the Microsoft Teams PowerShell module:
Connect-MicrosoftTeams
Set-CsTeamsMeetingConfiguration -Identity Global -EnableGraphTranscriptAccess $true -EnableAttributedTranscripts $true
The Configure panel also links to the Microsoft Entra admin center, where you can allow or block transcript access for each app. If you use that control, keep OnlineMeetingTranscript.Read.All allowed for the Abacus.AI Microsoft Teams app, or for your own Entra app if you use Custom OAuth.
Changes can take some time to apply to new requests. See Microsoft's Manage transcript API access for Teams meetings for details.
Step 2 — Allow transcription in your meeting policies​
A transcript exists only for a meeting that was transcribed. Transcription is controlled by the Teams meeting policy, and both the meeting organizer and the person who starts the transcription must have it allowed.
- In the Teams admin center, go to Meetings → Meeting policies.
- Open the policy assigned to your users. The Global (Org-wide default) policy applies to everyone who has no custom policy.
- Under Recording & transcription, turn Transcription On.
- Click Save, then repeat for any custom meeting policies assigned to your users.
With PowerShell:
Set-CsTeamsMeetingPolicy -Identity Global -AllowTranscription $true
See Microsoft's Manage transcription and captions for Teams meetings for details.
Step 3 — Make sure the transcript permission is consented​
OnlineMeetingTranscript.Read.All requires admin consent. How you grant it depends on how your users connect:
- Abacus.AI application (default): the tenant-wide consent described in Microsoft Entra Tenant Consent covers it, as long as the permission was listed on the Permissions requested screen when the admin accepted. Users might be asked for admin approval again, or transcripts might still fail with a permissions error after Steps 1 and 2. If so, have the Entra admin remove Microsoft Teams from Profile → User Connectors, connect it again, and tick Consent on behalf of your organization once more.
- Basic config connector: select
Calendars.Read,OnlineMeetings.ReadandOnlineMeetingTranscript.Read.Allunder Scopes, as described in Restrict scopes or use your own Entra app. - Your own Entra app (Custom OAuth): in the Microsoft Entra admin center, go to App registrations → your app → API permissions → Add a permission → Microsoft Graph → Delegated permissions. Add
Calendars.Read,OnlineMeetings.ReadandOnlineMeetingTranscript.Read.All, then click Grant admin consent.
After the permissions change, users must remove Microsoft Teams and connect it again from Profile → User Connectors.
Step 4 — Transcribe your meetings​
Teams does not transcribe meetings unless asked. For a meeting to have a transcript, someone in the meeting must start transcription from More actions (…) → Record and transcribe → Start transcription. If your meeting policy allows it, organizers can also turn on Record and transcribe automatically in the meeting's Meeting options (Microsoft documentation).
Step 5 — Check that it works​
After a transcribed meeting has ended, ask RouteLLM or the Abacus AI Agent something like:
"Get the transcript of my Weekly Sync meeting from yesterday and list the action items."
If you get an error instead, see Troubleshooting.
Transcript requirements and limitations​
- You can only read the transcript of a meeting you organized or were invited to through the calendar invite.
- The meeting must have a Teams event on your calendar, because the Teams Tool finds the meeting through your calendar.
- Transcripts of ad hoc calls (calls started directly from a chat rather than as a scheduled meeting) and of live events are not supported.
- A recurring meeting has a separate transcript for each occurrence that was transcribed. Include the date in your request.
- Transcripts follow your tenant's Teams retention and expiration settings. Expired transcripts can no longer be retrieved.
Use Microsoft Teams in ChatLLM​
Step 1 — Connect Microsoft Teams​
In ChatLLM Teams, click the Connectors link on the home page, or click your profile in the top right and navigate to Profile → User Connectors.

- Scroll the connector list and click Microsoft Teams.
- A browser pop-up opens asking you to sign in to Microsoft Teams and authorize Abacus.AI.
- Review the requested permissions and click Allow (or Authorize).
- After authorization completes, Microsoft Teams appears under your connected services and is ready to use.
User connectors are configured once per user and run under your own identity. After the connector is set up, every chatbot and the Abacus AI Agent in your workspace can query data from it.
Step 2 — Chat with RouteLLM​
- Open a new chat in ChatLLM Teams.
- From the model selector, choose RouteLLM (
route-llm). RouteLLM automatically routes each request to the most suitable underlying model, and is available for unlimited use to ChatLLM subscribers.

- Ask a question that references Microsoft Teams, for example "Summarize my recent Microsoft Teams messages". RouteLLM invokes the Microsoft Teams tool, fetches the data under your identity, and responds in chat.
The first time you query a newly connected service in a chat, you may be prompted to authorize the connector. Complete the sign-in once and the request continues automatically; subsequent requests reuse the connection.
You don't need to train a Custom Chatbot to use Microsoft Teams with RouteLLM. Once the connector is configured in the User Connectors panel, it is immediately available across your workspace chats and to the Abacus AI Agent.
If you want a dedicated bot with its own instructions and a restricted set of tools, train a Custom Chatbot in the Developer Platform and, under Advanced Options → Tool Use, select Teams_tool. End users of that chatbot are prompted to sign in to Microsoft Teams once, and the bot then acts under each user's own identity. See the Custom Chatbots guide for the full training and deployment walkthrough.
Troubleshooting​
- The authorization pop-up does not appear: allow pop-ups for the Abacus.AI site in your browser and click Microsoft Teams in the User Connectors panel again.
- "Need admin approval" when connecting: the tenant consent step has not been done yet. Ask a Microsoft Entra admin to follow Microsoft Entra Tenant Consent.
- "Not authorized" or stale results: remove Microsoft Teams from Profile → User Connectors and connect it again to refresh the authorization.
- Some items are missing: the connector cannot see more than your own Microsoft Teams account can. Check your access in Microsoft Teams itself.
- Transcript request fails with
403 Forbiddensaying Graph API access to transcripts is disabled (GraphAccessToTranscriptsDisabled): Microsoft Graph access to transcripts is still off for your tenant. A Teams admin must complete Step 1. The change can take some time to apply. - Transcript request fails with
403 Forbiddensaying speaker-attributed transcript content is disabled (SpeakerAttributionNotAllowed): Graph access is on, but Include speaker attribution is off. A Teams admin must turn it on, as described in Step 1. - Transcript request fails with any other
403 Forbidden: the connection does not have theOnlineMeetingTranscript.Read.Allpermission. Follow Step 3, then remove Microsoft Teams and connect it again. - "No transcript was recorded for this meeting": that meeting, or that occurrence of a recurring meeting, was not transcribed. Check that transcription is allowed for the organizer (Step 2) and that someone started it during the meeting (Step 4).
- The meeting cannot be found: make sure it has a Teams event on your calendar and that you were the organizer or on the invite. Include the meeting's title and date in your request.