MC918575 - Microsoft Teams: Watermark for anonymous meeting join

Service

Microsoft Teams

Published

Oct 25, 2024

Tag

Feature update
User impact
Admin impact

Summary

Microsoft Teams will soon allow anonymous users to join meetings with watermarked access to all content. Rollout begins early November 2024, with full availability by mid-November. Admins' watermark policies remain unchanged, while users will see a watermark of their entered guest name. The feature is default but can be altered via PowerShell script.

More information

Coming soon to Microsoft Teams: Anonymous unauthenticated users will be able to join watermarked meetings and have access to all meeting content, including video. This message applies to Teams on Windows desktop, Teams on the web, Teams for Android/iOS, and Teams Rooms.

When this will happen:

General Availability (Worldwide): We will begin rolling out early November 2024 and expect to complete by mid-November 2024.

How this will affect your organization:

Before this rollout: Unauthenticated users who join a watermarked meeting can hear the meeting audio only.

After this rollout:

  • Admins: The watermark policy in the Teams admin center will remain the same as it is now, because anonymous guest support will not be tied to a policy.
  • Users: Anonymous users can join as before the rollout. They will see a watermark of their guest name they entered on the pre-join screen and will be able to access all meeting content.

An anonymous user will be asked to enter their name on the pre-join screen:

user controls

After the anonymous user joins the meeting, they see the name they entered on the pre-join screen as the watermark:

user controls

What you need to do to prepare:

This feature will be on by default. If you do not want guest name as the watermark for anonymous users, you can run a Microsoft PowerShell script for these guests to have access to audio only in meetings.

Learn more: Require a watermark for sensitive Teams meetings - Microsoft Teams | Microsoft Learn (will be updated before rollout)