Microsoft is introducing a new tenant-level control that governs whether applications and agents can access Teams transcripts via the Microsoft Graph API, including whether speaker attribution is included in that transcript data.
- This update affects organizations utilizing apps or agents with Microsoft Graph API permissions to read transcripts for meetings or calls (such as OnlineMeetingTranscript.Read.All, OnlineMeetingTranscript.Read.Chat, CallTranscripts.Read.All,…).
- This update does not alter how transcripts are accessed via Microsoft Graph, nor does it affect transcription generation, meeting recording policies, or how transcripts appear within the Teams client.
Timeline
- Until 29 July 2026: Teams Administrators can update the API access control. The control is disabled by default.
- After 29 July 2026: The API access is enforced. If the control is disabled, API access to meeting and call transcripts will return an access error.
How does this affect your organization?
Currently, Entra ID app registrations and agents with appropriate Graph API permissions and admin consent can read and download transcripts (including speaker attribution) without a tenant-level toggle to block this centrally. This update introduces the control layer.
Teams administrators can now allow or block Graph API transcript access at the tenant level, independent of the individual app permissions granted in Microsoft Entra.
To configure this, navigate to the Teams admin center > Settings & Policies > open your global Meeting policy and locate the “Transcript API access” section.
Two settings govern this new control:
- Graph API access
Controls whether any app or agent can retrieve transcripts through the Graph API. This control is off by default.

- Include speaker attribution
Controls whether transcripts retrieved through the Graph API include speaker names. This control is off by default and only configurable once Graph API access is on.

Existing behavior remains unchanged until 29 July 2026, meaning no apps will lose access during this time.
Once enforcement begins, any app or agent relying on Entra-granted Graph API permissions to read transcripts will encounter access errors unless an administrator has explicitly enabled Microsoft Graph access. You can find an access error sample here.
HTTP/1.1 403 Forbidden
Content-Type: application/json
{
"error": {
"code": "Forbidden",
"message": "Graph API access to transcripts is disabled for this tenant.",
"innerError": {
"code": "GraphAccessToTranscriptsDisabled"
}
}
}