The Pulse
Reference-Tenant Notice Sets Mid-November Target for Teams Deepfake Alerts
A 365Fanatic reference copy of a Microsoft Message Center notice says targeted rollout of third-party synthetic audio and video detection in Teams is expected to begin in mid-November 2026. Microsoft’s Graph documentation describes a separa
AI.info Team · Written with AI · fact-checked ·
A 365Fanatic reference-tenant copy of Microsoft Message Center notice MC1509787 lists a targeted worldwide rollout of third-party synthetic audio and video detection in Teams beginning in mid-November 2026. The copy says completion is expected by late November and that Microsoft will provide general-availability timing through Message Center when ready to proceed. 365Fanatic identifies the post as a reference from a West Europe tenant and advises readers to check their own Message Center for information that applies to their organization; it is not the original Microsoft announcement.
Teams will show alerts from outside detectors
The reference copy describes certified third-party providers analyzing meeting media for signs of synthetic or manipulated audio and video, then sending detection signals to Teams. Separately, Microsoft’s Graph documentation describes a bot that joins a meeting and reports a participant whose stream it identifies as AI-generated or synthetic. Teams distributes the result through participant roster updates, rather than keeping it only with the organizer or administrator. The provider performs the detection; Teams supplies the platform integration and experience for surfacing and acting on the signal.
The reporting interface accepts an overall confidence score from 0.0 to 1.0, a severity level and an indication of whether the bot considers the media malicious. It also supports audio, video and separate model or segment findings. These fields describe what a provider reports; they do not establish that a flagged participant is using a deepfake.
Administrators choose the provider and grant access
The Message Center copy says organizations should select a supported provider, deploy its app through Manage apps in the Teams admin center, grant permissions and configure meeting policies. In the Graph API, the required application permission is Calls.ReportSyntheticMedia.All; the bot must also be admitted to the call before it can submit a report. The API documentation says delegated permissions are not supported for this action.
The arrangement leaves detection to the outside provider and gives Teams the role of presenting and acting on its signals. The notice says certified providers may analyze meeting audio and video signals, and recommends administrators review provider terms, data handling and compliance documentation before enabling the feature. It does not detail how individual providers process or retain meeting data.
The reporting API is still marked beta
Microsoft’s reportSyntheticMedia documentation describes a beta Graph API, not the Teams rollout schedule. Microsoft warns that beta APIs can change and are not supported for production applications, so the published technical details should not be mistaken for a finished, generally available Teams feature.
The documentation recommends limiting reports to no more than one request per target participant per minute to avoid throttling; it does not state that rate as a hard API limit. It also advises bots to report meaningful changes rather than every analyzed frame. Each new report ID creates a separate record rather than merging with earlier reports; when several records exist, the participant’s detection property reflects the latest one. These details govern how the signal is submitted and recorded, not the accuracy of the provider’s detector.
Targeted release is scheduled for November
The reference copy of MC1509787, dated October 22, 2026, says worldwide targeted release is expected to begin in mid-November 2026 and finish by late November. For general availability, the copy says Microsoft will provide timing through Message Center when it is ready to proceed. The notice associates the feature with Microsoft 365 roadmap item 573451.
For IT teams, the listed steps are provider selection, app deployment, permission review and meeting-policy configuration. For meeting participants, the design means a provider’s detection can become visible across the call, even though the analysis originates outside Teams. The beta API documentation and the lack of a general-availability date in the reference copy leave the production rollout and provider arrangements unsettled.