Microsoft is tightening presenter access for Teams events. Starting April 2026, external presenters who join a webinar or town hall anonymously will need to verify their identity with a one-time passcode sent to their email. The new requirement, published on the Microsoft 365 Roadmap, applies to the Teams desktop client and closes a gap that could let uninvited speakers take control of an event.

How the new verification works

Today, event organizers can share a join link with external presenters. That link alone grants presenter privileges with no further identity check. The upcoming feature flips that model.

When an organizer enables the setting for an event, any external participant marked as a presenter will face an additional step: as soon as they click the link, Teams will prompt them to enter a passcode. That code is delivered to the email address the organizer used when scheduling the event. Enter it correctly, and they’re in—with full presenter rights. Fail to enter it, and they’re blocked entirely.

The change is tracked under a Microsoft 365 Roadmap entry that classifies it as a general-availability release for April 2026. Microsoft’s roadmap note describes it as “one-time email passcodes for anonymous external presenters in Teams events.” The feature is cloud-delivered, so no client update will be required beyond what the standard release channel already provides.

Organizers will see a toggle in the meeting options or event setup pane. The default state is not yet confirmed, but admins should expect the ability to mandate the check via policy. Microsoft has not said whether this will later become mandatory for all external presenters.

Impact across your organization

For IT administrators and compliance officers, the feature is a direct line to stronger identity governance in live events. Today, an external presenter who is accidentally forwarded a join link—or who steals one—can appear on screen as a trusted speaker. With email passcodes, that risk shrinks dramatically because the passcode is tied to a specific email address the organizer controls.

Event organizers gain a straightforward checkbox to enforce. No need to manage guest accounts or fuss with external identity providers. For executive communications, investor calls, or customer-facing webinars where a rogue presenter would be catastrophic, this is a no-brainer.

External presenters will feel the extra step, but it’s quick: open the email, copy the code, paste it into Teams. The passcode is one-time and session-specific, so even if an invitee’s email is later compromised, the code is useless outside that event.

Attendees attending town halls or webinars won’t notice any change. The passcode only applies to external people with the presenter role. Standard anonymous attendees continue to join with the event link or registration, depending on the event type.

The feature is desktop-only at launch. Mobile and web clients may follow later, though the roadmap is silent on that. This could create temporary friction for presenters who prefer joining from a phone or browser, but most business presenters likely use a laptop or desktop anyway.

The roadmap to safer events

Microsoft Teams has layered on security feature after feature since its pandemic-era breakout. Meeting lobby settings, end-to-end encryption for ad hoc calls, meeting ID and passcode updates for standard meetings, and registration-based webinars all arrived in the last few years. But the presenter role remained relatively unprotected.

The gap wasn’t theoretical. “Zoombombing” incidents—where uninvited users joined meetings and disrupted them—plagued the industry early in the remote-work boom. Most platforms responded by tightening attendee access. Presenter hijacking never reached the same volume, but as companies ran high-profile town halls and earnings calls on Teams, the risk of an impersonation became too large to ignore.

Microsoft’s own Ignite and Build conferences rely on Teams Live Events and, more recently, town halls, making the company acutely aware of the threat surface. This passcode feature is the latest in a string of identity-hardening moves that include mandatory multifactor authentication for Microsoft 365 admin portals and more granular meeting role management.

The competitive landscape also matters. Zoom already offers “authenticated presenters” as part of its webinar product, and Cisco Webex requires host authentication for sensitive meetings. Teams is now catching up on the presenter front.

Getting ready for the change

There’s no immediate action required. April 2026 is still far out, but a little preparation now saves confusion later.

IT admins should:
- Watch for the Microsoft 365 Admin Center notification that confirms the rollout timeline.
- Evaluate whether to enforce the passcode check by default across your tenant. Consider piloting with a small group of frequent event organizers.
- Update internal documentation and training so organizers know what to expect and how to guide external presenters.
- Remind help-desk staff that a spike in “presenter can’t join” tickets may arrive the first week after release.

Event organizers should:
- Start including a note in event communications once the feature is live in your tenant. Something as simple as “You will receive a one-time passcode to verify your identity before presenting” sets expectations.
- Test the flow with a mock event. The experience for the external presenter is straightforward, but walking through it once removes anxiety.

Microsoft has not announced any deprecation of the older “open link” presenter experience, but the writing is on the wall. Once an email-verified presenter option exists, many organizations will mandate it for compliance reasons.

What’s next for Teams security

The April 2026 release is likely a stepping stone. Microsoft’s broader identity roadmap includes passwordless authentication, conditional access based on presenters’ tenant properties, and deeper integration with Microsoft Entra Verified ID. It’s easy to imagine a future where an external presenter is not only verified by email but also by their organization’s identity provider, all without a guest account.

For now, the one-time email passcode is a practical, low-friction way to raise the bar. It doesn’t require external users to have a Microsoft account, doesn’t force them to install extra software, and doesn’t stall the event with cumbersome registration forms. That balance of security and simplicity is what makes the feature likely to stick—and to expand.