IT teams that want Microsoft Teams to catch a cloned voice or a face-swapped video in a meeting will need an outside vendor to do the catching. Microsoft plans to start rolling out support for certified third-party deepfake detectors in mid-November, and its admin notice spells out who does the work: "Synthetic media detection is performed by the third-party provider."

The notice, MC1509787, was revised on Oct. 22. Targeted Release customers should see the feature between mid-November and late November on Teams for desktop, Mac and web. General availability no longer has a date; Microsoft says it will post again in the Message center "when we are ready to proceed." The first version had aimed for general availability from late November to mid-December, Windows Latest reported.

Abstract grid of nine video-meeting tiles in slate and teal, with one tile broken into shifted pixel blocks and circled by an amber scan ring

How a detection bot flags someone

The mechanics are already in Microsoft's Graph beta documentation. A provider's bot has to be admitted to the call, and the tenant administrator has to grant it the Calls.ReportSyntheticMedia.All permission. The bot then reports a participant with a confidence score from 0.0 to 1.0, an optional low, medium or high severity, and a yes-or-no judgment on malicious intent. Microsoft's sample requests use model tasks named voiceClone, faceSwap and lipSync. The result reaches every participant in the meeting through roster updates.

Admins will pick a provider, deploy its app from the Teams admin center and set meeting policies. The two policy settings, SyntheticMediaDetection and SyntheticMediaDetectionAppId, already sit in the Teams PowerShell reference with a note that they have no effect until release. The default app ID, Microsoft writes there, resolves to no provider "when 1P is not available, or Microsoft Detection when 1P is available."