Microsoft’s release communications records show two Teams meeting items, both listed for November 2026: Impersonation Protection for Teams meetings (roadmap ID 573157) and third-party synthetic audio and video detection (ID 573451). Both are aimed at the same problem: someone joining a meeting while pretending to be a person you trust. Any business that approves payments, password resets or vendor changes over Teams calls should read on.
What Microsoft has announced
For Impersonation Protection, Microsoft’s record says the feature helps users identify potentially deceptive participants and meeting organizers. When Teams detects a potential impersonation attempt, it shows warnings and risk indicators so users can judge suspicious identities before joining or taking part in a meeting. The record covers Android, desktop, iOS, Mac and web, and is marked in development. Microsoft lists November 2026 and gives no separate general availability date.
For synthetic media detection, the record says organizations can use detection solutions from certified third-party providers. Those solutions analyze meeting media for signs of synthetic or manipulated audio and video and send detection signals to Teams, which surfaces them in the meeting. Microsoft states plainly that the detection is performed by the third-party provider. This item is listed for desktop, Mac and web, and Microsoft again lists November 2026 with no separate general availability date.
Both entries are marked in development, so the November 2026 listing may change. The records we read give no licensing details, no admin settings and no list of the certified providers. We will not guess at those, and you should not plan around them until Microsoft publishes more.
Who is affected
Any organization that holds meetings in Microsoft Teams with people outside the company: customers, vendors, banks, outside accountants, or a prime contractor. The risk is not new software on your network. It is a person, or a convincing imitation of one, on a video call asking for something.
Owners and office managers who approve wire transfers, change vendor bank details, or reset access for staff by voice or video are the people most exposed to this kind of deception. In our view, defense subcontractors have the same exposure when a call touches contract or technical data.
What these features do not replace
In our view, warnings and risk indicators help a person decide, but they do not replace an approval rule. A detection signal from a provider is also a signal, not proof. A call that passes every automated check can still be a request you should not honor, and a real colleague can be flagged by mistake. The rules below work with or without the new features.
What to do: a checklist
- Write a call-back rule for money and access. Any request to move money, change bank details, share credentials or grant access that arrives on a call is confirmed through a second channel you already trust, such as a phone number from your own records, never one given during the call.
- Decide who can approve what. Name the people who may authorize payments and account changes, and state that a meeting request alone is never enough. Put it on one page and share it with everyone who answers calls or handles invoices.
- Review who can join your meetings. Look at your Teams meeting options for who bypasses the lobby and who can present. Keep outside guests in the lobby so the organizer sees each name before admitting them.
- Check display names against the invitation. If someone you expect joins under an unfamiliar name or from an unexpected address, ask them to rejoin through the original invitation before discussing anything sensitive.
- Tell staff what a warning means. When these features reach your tenant, a warning should pause the conversation and trigger the call-back rule. It should not be dismissed as a glitch.
- Put the rollout on your change calendar. Microsoft lists November 2026 for both records. Have whoever administers Microsoft 365 watch the Message center and items 573157 and 573451 for settings, licensing and provider details before the rollout reaches you.
- Ask your vendors the plain question. If you rely on a bank, payroll provider or supplier that verifies requests by video call, ask how they confirm who is on the line.
What can wait
You do not need to buy a third-party detection product yet. Microsoft’s record says the detection itself is performed by certified third-party providers, and the records we read do not name them. Waiting for details costs you nothing, while the call-back rule in step one costs nothing and works immediately.
You also do not need to change how you hold ordinary internal meetings. The concern is outside participants and requests that involve money, credentials or sensitive data.
A common mistake
The most common mistake is to treat a familiar face or voice as verification. That is our guidance, not Microsoft’s: a familiar face or voice is not proof of identity. Microsoft’s record 573451 describes third-party providers analyzing meeting media and sending detection signals to Teams. Until a control you have tested is in place, assume that what you see and hear on a call is not by itself proof of identity.
When to get help
If you are unsure how your Teams meeting options are set, who in your tenant can change them, or how to write an approval rule your staff will follow, that is a short piece of work. Our Microsoft 365 management covers configuration, and our cybersecurity services cover staff procedures like the call-back rule. Summit Networks can review your Teams settings and draft the approval rule with you; contact us to start.