Can Teams stop a deepfake ‘CFO’ on a call before someone pays?

You’re right to take this seriously. It’s no longer a film plot: practitioners on r/cybersecurity and r/AskNetsec keep pointing to large losses from convincing fake video calls, and MSPs report fake “Help Desk” tenants ringing users in Teams to talk them into a remote-support session.

Here’s what’s going on. Two roadmap items landed this month. 573157, Impersonation Protection for Teams meetings, will show warnings and risk indicators when Teams spots a potentially deceptive participant or organiser. 573451, Third-party synthetic audio and video (deepfake) detection, lets certified third-party providers analyse meeting media and send signals into Teams. Microsoft is explicit that the detection is done by the provider; Teams supplies the integration and the in-meeting experience. Both are In development, targeted for November 2026, so you can’t switch them on today and will likely need a separate product for the deepfake part.

What you do have today is in Learn. You can restrict external access to an allow-list of trusted domains rather than open federation, which shuts out the throwaway tenants those fake help desks use. You can control anonymous join, push guests and external people through the lobby, and limit who can admit people to organisers and co-organisers. With Teams Premium, organisers can require unverified participants to verify by email code before joining. And Teams now detects external bots (note-takers and the like), parks them in the lobby and warns organisers before admitting them.

The honest limitation: detection is an arms race, and the people defending against this professionally say the same. A warning banner is helpful; it isn’t a control. The control is a process that doesn’t trust a face or a voice for anything that moves money or grants access. This is the Security pane and the Narrative pane working together, and it’s Schofield’s Third Law again: the easier you make it to act on a call, the easier you make it for an impostor.

Options that actually work:

1. Process first, technology alongside. Payments, bank-detail changes and password or MFA resets never happen on the strength of a call alone: call back on a known number, use a second approver, and give finance and the service desk explicit permission to slow down. Best Steady default.
2. Tighten Teams now. Move external access to an allow-list (with a simple request route for new partner domains), keep anonymous join and lobby bypass tight for sensitive meetings, and remove or restrict remote-assistance tools users can launch themselves.
3. Pilot the new protections in November. When 573157 arrives, test the warnings with finance and executive assistants first; evaluate certified detection providers for 573451 on accuracy, privacy and where media is processed.
4. Wait for detection and do nothing else. It leaves you relying on a vendor winning an arms race on your behalf.

12 Panes action / comms: Tell finance and executive assistants: A video call is not authorisation. Hang up and call back. Tell the service desk: We never ask you to start a remote session from an unexpected Teams call. Tell Teams admins: External access allow-list, lobby discipline, external bot detection on. Leadership: Impersonation warnings are coming; our process is the real defence.

Benefits / risks: Simple callback rules stop most of these attacks regardless of how good the fake is; an allow-list adds a little friction for new partners; third-party detection means another processor seeing meeting media, so check your privacy and works-council position; roadmap dates move. Verify Learn and Message Centre as these features approach.

I’d suggest writing the one-paragraph “never on a call alone” rule this week and getting finance to sign it off. Once that’s in place, the new Teams warnings become a useful extra layer rather than the only thing standing between you and a very expensive afternoon.

DIGITAL SKILL WORKS LTD / 12 PANES · You ask, we answer