Teams plans third-party deepfake detection integration

Microsoft 365 Roadmap ID 573451 lists the feature as in development.[1] The roadmap entry was published on October 2, 2026, and gives November 2026 as the general-availability date.[1] The feature is described as a way for organizations to enhance meeting security using synthetic audio and video detection solutions from certified third-party providers.[1] Microsoft lists Desktop, Mac and Web as supported platforms, and Worldwide (Standard Multi-Tenant) as the cloud availability.[1] These are roadmap details, not confirmation that the feature is already generally available.

The division of work is central to the announcement: Teams will not perform the synthetic-media detection itself.[1] Instead, certified third-party solutions will analyze meeting media for signs of synthetic or manipulated audio and video, then send detection signals to Teams.[1] Microsoft says Teams will provide integration and in-meeting experiences to surface and act on signals from supported providers.[1] The roadmap also says Teams surfaces warnings and risk indicators when it detects a potential impersonation attempt.[3] Organizations considering the feature should therefore distinguish the provider’s detection from Teams’ handling of the resulting signal.

The roadmap does not name the certified detection providers or specify how their systems will identify synthetic media.[2] It also gives no detection-accuracy measurements and no information about false positives or false negatives.[2] Microsoft does not say whether Teams will show participant warnings, notify administrators or apply automated restrictions in response to detection results.[2] The roadmap does not guarantee that every flagged participant or media stream indicates malicious activity.[2] Teams leaders should treat the feature as a signal-handling capability, not as evidence that an alert alone establishes intent or identity.

Microsoft Graph documentation describes an action intended for certified third-party audio and video synthetic-media detection bots admitted to a meeting call.[4] The documentation says reported detection information is delivered to all participants in a roster update notification.[4] For that Graph beta action, the meeting tenant administrator must grant the app the Calls.ReportSyntheticMedia.All application permission.[4] Microsoft cautions that APIs under Graph’s beta version are subject to change.[4] This documentation offers implementation context, but its beta status means teams should not assume the API details are fixed.