How to use the Microsoft Graph API to get meeting transcripts from Teams
This guide walks through Microsoft Graph authentication, permissions, transcription, and more, while helping you understand when a unified meeting API is a better fit.
Microsoft Graph lets you retrieve transcripts that Microsoft Teams has already generated. For a scheduled meeting, the basic workflow is to authenticate your application, identify the onlineMeeting resource, list its transcripts, and download each transcript’s content.
There are two approaches to getting Microsoft Teams transcripts programmatically: retrieve a transcript Teams has already generated through Microsoft Graph, or capture meeting audio and generate a transcript through a service such as Recall.ai. This guide covers the Microsoft Graph approach. Recall.ai is another option when your product needs real-time transcription or support for Teams, Zoom, and Google Meet.
1. Make sure Teams generated a transcript
Before making an API request, confirm that transcription was enabled and actually started during the meeting, either automatically or by an authorized participant.
Who can start transcription depends on Teams policies and meeting options. Organizers, co-organizers, and eligible presenters can start transcription when permitted, but meeting options can restrict this to organizers and co-organizers or prevent anyone from starting it. Transcription must also be enabled by policy for both the organizer and the person initiating it.
A recording does not guarantee a transcript: Teams can record a meeting while transcription is disabled. Turning on live captions also does not create a saved transcript. Meanwhile, Recall.ai’s meeting bot API produces its own transcript from the meeting audio, so it doesn’t depend on Teams transcription being turned on.
Microsoft Graph’s transcript retrieval endpoints do not provide a live transcript stream. If your application needs real-time Teams transcription, Recall.ai's meeting bot API can capture meeting audio and deliver transcripts during the meeting.
2. Register an application and configure permissions
Create an app registration in Microsoft Entra ID. Record its application (client) ID and tenant ID, then configure credentials for your backend.
For this walkthrough, add these Microsoft Graph application permissions and have a tenant administrator grant consent:
OnlineMeetingTranscript.Read.All: Read meeting transcripts.OnlineMeetings.Read.All: Resolve anonlineMeetingfrom its Teams join URL.
Note: Recall.ai’s Meeting Bot API doesn’t need an Azure app registration, these Graph permissions, or an application access policy, and its bot can join Microsoft Teams meetings in other tenants.
OnlineMeetings.Read.All is needed for the meeting lookup shown below. It is not required solely to read a transcript when you already have the onlineMeeting ID.
For delegated access, the corresponding permissions are OnlineMeetingTranscript.Read.All and OnlineMeetings.Read. Use a signed-in work or school account and an appropriate delegated authentication flow. Personal Microsoft accounts are unsupported for these transcript endpoints.
Microsoft also supports OnlineMeetingTranscript.Read.Chat through resource-specific consent for scheduled private chat meetings. That is a separate authorization approach and is outside this walkthrough.
3. Configure an application access policy
For the OnlineMeetingTranscript.Read.All application-permission route used here, admin consent alone is insufficient. A tenant administrator must create an application access policy containing your app’s client ID and assign it to the user whose ID appears in your requests.
For this walkthrough, use the meeting organizer’s Microsoft Entra user object ID.
An administrator can run the following with Teams PowerShell:
Connect-MicrosoftTeams
New-CsApplicationAccessPolicy `
-Identity "TranscriptReaderPolicy" `
-AppIds "<CLIENT_ID>" `
-Description "Allow the app to retrieve meeting transcripts"
Grant-CsApplicationAccessPolicy `
-PolicyName "TranscriptReaderPolicy" `
-Identity "<ORGANIZER_USER_OBJECT_ID>"
Policy changes can take up to 30 minutes to affect Graph requests. An application access policy authorizes access on behalf of the assigned user; it does not grant unrestricted access to every Teams meeting.
4. Obtain a Microsoft Graph access token
For a backend service without a signed-in user, use the OAuth 2.0 client credentials flow.
The following illustrative request uses a client secret:
POST https://login.microsoftonline.com/<TENANT_ID>/oauth2/v2.0/token
Content-Type: application/x-www-form-urlencoded
client_id=<CLIENT_ID>&client_secret=<URL_ENCODED_CLIENT_SECRET>&scope=https%3A%2F%2Fgraph.microsoft.com%2F.default&grant_type=client_credentials
Read access_token from the response and include it in subsequent requests:
Authorization: Bearer <ACCESS_TOKEN>
The .default scope requests the Graph application permissions already granted to the application. It does not grant new permissions.
Keep credentials on the server. For production, consider certificate or federated credentials, and use Microsoft’s authentication libraries to handle token acquisition.
Application tokens use /users/{user-id} routes. The /me route requires delegated authentication.
5. Find the onlineMeeting ID
The transcript endpoint expects the id of an onlineMeeting resource. Do not substitute an Outlook calendar event ID or the numeric meeting ID attendees enter to join.
If you have the Teams join URL, resolve it through:
GET https://graph.microsoft.com/v1.0/users/<ORGANIZER_USER_ID>/onlineMeetings?$filter=JoinWebUrl eq '<TEAMS_JOIN_URL>'
Authorization: Bearer <ACCESS_TOKEN>
This example is shown in readable form. URL-encode the query parameter when sending the request, and escape embedded single quotes according to OData string rules.
Use the id of the matching object in the response’s value array as <ONLINE_MEETING_ID>. Treat this ID as opaque and encode it as a URL path segment in subsequent requests.
For delegated access, the analogous lookup is:
GET https://graph.microsoft.com/v1.0/me/onlineMeetings?$filter=JoinWebUrl eq '<TEAMS_JOIN_URL>'
Authorization: Bearer <DELEGATED_ACCESS_TOKEN>
Being able to resolve a meeting does not, by itself, establish permission to read its transcripts.
6. List the meeting’s transcripts
Request the transcript collection:
GET https://graph.microsoft.com/v1.0/users/<ORGANIZER_USER_ID>/onlineMeetings/<ONLINE_MEETING_ID>/transcripts
Authorization: Bearer <ACCESS_TOKEN>
The response contains callTranscript metadata, including each transcript’s id. If the collection is empty, check whether transcription ran and whether the artifact is available yet.
This API does not support meetings created with the standalone create onlineMeeting API when they are not associated with a calendar event. It also works only while the meeting has not expired.
If Teams never generated a transcript, there is no transcript for this Graph endpoint to return. For future meetings, an alternative is to capture audio with Recall.ai and generate a transcript from that recording. Recall.ai's calendar API allows you to schedule meeting bots to capture a meeting ahead of time, so users don't need to remember to record.
7. Download the transcript content
Listing transcripts returns metadata. To retrieve the words spoken, request /content for each transcript:
GET https://graph.microsoft.com/v1.0/users/<ORGANIZER_USER_ID>/onlineMeetings/<ONLINE_MEETING_ID>/transcripts/<TRANSCRIPT_ID>/content
Authorization: Bearer <ACCESS_TOKEN>
Accept: text/vtt
When speaker attribution is permitted, the WebVTT response contains timestamped utterances with speaker voice tags. An illustrative excerpt looks like:
WEBVTT
00:00:01.000 --> 00:00:04.000
<v Alex>Let's review the project timeline.</v>
Store the original transcript before converting it into plain text or structured utterances. Preserving timestamps makes it easier to connect summaries and extracted action items to their source passages.
If Graph returns SpeakerAttributionNotAllowed, retry the same request with:
Accept: application/vnd.microsoft.graph.transcript+text
That format provides timestamped utterances without speaker information. Select it through the Accept header; it is not supported through the $format query parameter.
This fallback applies when speaker attribution is disabled. It does not bypass a tenant-wide restriction on Graph transcript access.
8. Automate retrieval with change notifications
For ongoing ingestion, use Graph change notifications to learn when transcript artifacts become available.
Supported subscription scopes include:
- An individual meeting:
communications/onlineMeetings/{onlineMeetingId}/transcripts - Meetings organized by a particular user:
users/{userId}/onlineMeetings/getAllTranscripts - Tenant-wide meeting transcripts:
communications/onlineMeetings/getAllTranscripts
Each scope has its own permission requirements. Microsoft currently documents that the individual-meeting and organizer-level subscriptions do not support private channel meetings.
Create the relevant subscription before transcription starts; Microsoft documents this timing requirement for meeting transcript notifications. Your service also needs webhook validation, subscription renewal, and lifecycle handling. If the requested subscription expiration is more than one hour in the future, include a lifecycleNotificationUrl.
Treat notifications as triggers to queue retrieval work. Use the meeting and transcript identifiers to prevent duplicate processing, and retry temporary failures with bounded backoff.
If a tenant administrator disables Graph transcript access, creating or renewing transcript subscriptions also fails with GraphAccessToTranscriptsDisabled.
Common problems and limitations
“No application access policy found for this app”
Check that the policy includes the correct application client ID, is assigned to the user in the request path, and has had time to propagate.
GraphAccessToTranscriptsDisabled
The tenant administrator has disabled Graph API access to transcripts. Changing the request or acquiring another token does not resolve this setting. An administrator must re-enable access.
SpeakerAttributionNotAllowed
The tenant administrator has disabled speaker-attributed transcript content. Retry the content request with:
Accept: application/vnd.microsoft.graph.transcript+text
Missing transcript
Check that transcription ran, the artifact is available, the onlineMeeting ID is correct, and the meeting fits the endpoint’s supported scenario. Also check whether the meeting has expired.
For programmatic error handling, inspect error.code and, where supplied, error.innerError.code rather than matching human-readable error messages.
When to consider a unified meeting API like Recall.ai over Microsoft Graph
Microsoft Graph works when your application needs existing Teams transcripts and you can arrange the required access. However, for a consumer-facing product, the challenge is that an individual user signing up may not control the configuration your integration needs. The application-permission approach described here requires tenant administrator consent and an application access policy, and administrators can disable Graph transcript access altogether.
Microsoft Graph also depends on Teams generating a transcript in the first place, which requires an individual with the required roles – organizer, co-organizer, or presenter – to start meeting recording. Otherwise, if transcription never starts, there is no transcript to retrieve. Furthermore, these Microsoft Graph endpoints do not provide a live transcript stream, and supporting Zoom or Google Meet requires separate integrations. Recall.ai returns real-time and post-meeting transcripts for Teams, Zoom and Google Meet through one API.
Recall.ai's unified API allows you to get transcripts from Microsoft Teams without someone manually remembering to record, and works regardless of the user’s role in the meeting or what Teams plan they are in. You can also receive real-time or post-meeting transcripts without relying on Teams’ native transcription being enabled. That makes a unified API a practical option when you want users to connect meetings across platforms with less tenant-specific setup.
| Requirement | Graph saved-transcript workflow | Recall.ai Meeting Bot API | Recall.ai Desktop Recording SDK |
|---|---|---|---|
| Retrieve existing Teams transcript | Yes, with authorized access | Produces a transcript from captured audio | Produces a transcript from captured audio |
| Live transcription | No live stream through these endpoints | Yes | Yes |
| Depends on Teams transcription running | Yes | No | No |
| External meetings | Requires an eligible authorization path | Bot can join and record external meetings | User can record external meetings through a desktop app |
| Zoom and Google Meet | Separate native integrations | Supported | Supported |
| Capture interface | Backend Graph requests | Bot appears as a participant | Installed desktop application, without a bot participant |