Wednesday, May 17, 2023

How to block Teams Meeting chat Read and Write access to anonymous attendees

If your organization has concerns about anonymous users starting or joining Teams meetings, there's a way to address it. By disabling the option in the Teams Meeting policy and assigning it to the user, you can prevent anyone from joining as an anonymous user. It's a straightforward solution that can help ensure the security and privacy of your meetings.



In case your organization permits anonymous users to join the call without starting the meeting, and only the organizer wishes to let them in, configuring the meeting policy can be a viable option.

If you are hosting a Teams meeting with external or anonymous participants, you should prevent them from accessing the meeting chat. This can help you avoid unwanted messages or spam from unknown users. 


By default, anonymous users joining a meeting can view & send chat messages. However, you can disable their read access by following these steps:


1. Go to the Teams admin center (https://admin.teams.microsoft.com/) and sign in with your admin credentials.

2. In the left navigation, go to Meetings > Meeting policies.

3. Select the policy that you want to edit or create a new one.

4. Scroll to the Meeting engagement section and set Chat in meetings to On for everyone but anonymous users. This will block anonymous users from both writing and reading the chat messages.

5. Select Save to apply the changes.


Please note that this particular setting is only applicable to meetings that are not hosted in a channel. In the case of channel meetings, you have the ability to manage and determine who is authorized to post messages within the channel settings.




To configure this setting, PowerShell can come in handy. Simply use the -ChatInMeetings parameter in Set-CsTeamsMeetingPolicy. If you want to set this parameter to On for all users except anonymous ones in the global policy, you can execute this command:


Set-CsTeamsMeetingPolicy -Identity Global -ChatInMeetings EveryoneInCompany



No comments:

Post a Comment