Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 11:37 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Teams: Graph API transcript access controls for administrators

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Action date

29 Jul 2026 89d ago Act by , as Microsoft's metadata states

What the notice says

Microsoft’s text, with source markup removed
What and Why We are introducing new administrative controls in Microsoft Teams to help you govern how applications and agents access meeting transcripts through the Microsoft Graph API. These controls provide more granular governance over transcript data, including transcripts with speaker attribution, helping you align access with your organization’s security and compliance requirements. Rollout Schedule General Availability (Worldwide): Rollout of the settings will begin in late June 2026 and is expected to complete quickly.  Enforcement of the controls will begin approximately 30 days after availability (late July 2026). Impact on Your Organization Who is affected Microsoft 365 tenant administrators managing Microsoft Teams and Microsoft Graph API permissions Platforms/Services Microsoft Teams Microsoft Graph API What will happen New administrative controls will allow you to: Allow or block applications and agents from accessing meeting transcripts through Microsoft Graph API Apply access controls to transcripts with or without speaker attribution Govern access to sensitive transcript data across your tenant During the 30-day configuration period, existing behavior remains unchanged. After enforcement begins, applications that previously had access via Microsoft Entra Admin Portal permissions will receive access errors if administrators do not explicitly enable transcript access. Action Required/Recommendations Action is required within 30 days of feature availability to avoid disruption to applications that rely on transcript access. Review the new transcript access control settings when they become available. Decide whether to enable transcript access for applications and agents with Graph API permissions. Configure the settings based on your organization’s security and compliance requirements. Administrators can configure these settings in the Teams admin center under: Settings & policies > Meetings (new experience), or Meetings > Meeting settings (classic experience) These controls are also available via PowerShell cmdlets. Communicate changes to relevant stakeholders, including security and compliance teams. Update internal documentation if you track API access policies. Learn more:  Documentation for these controls will be available on Microsoft Learn at rollout. Content updates are currently in progress. Overview- Recording and transcription for Teams meetings, events, and calls | Microsoft Teams | Microsoft Learn Set-CsTeamsMeetingConfiguration | MicrosoftTeams | Microsoft Learn Teams settings and policies reference | Microsoft Teams | Microsoft Learn Compliance considerations Question Answer Does the change alter how existing customer data is processed, stored, or accessed? Yes. Introduces new controls governing how applications and agents access meeting transcripts via Microsoft Graph API. Does the change include an admin control and can it be controlled through Entra ID group membership? Yes. Provides administrative controls to enable or restrict transcript access for apps and agents.

What changed

Between archive captures, newest first

The archive supplies one version of this notice.

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 26 Oct 11:37 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current