Microsoft Teams: Block a user for your organization

Microsoft Teams is rolling out a block user feature to protect organizations from unwanted contact by malicious users. This feature will be available worldwide in early November 2024 and will be associated with Microsoft 365 Roadmap ID 411138. Admins will have the ability to block users, preventing 1:1 and group chats with them. The feature will be off by default and can be enabled in the external access settings. This new feature will leverage the allow/block list in federation identity credentials to block a malicious user from the entire organization, making it impossible for the user to reach out again. In the event that a blocked user has ongoing chats with the organization, they will be removed from those chats. Admins can add users to the block list by navigating to external access organization settings. It is important to note that the delete API does not prevent malicious users from resending a Teams message to the same victim.
If you are an admin, it is recommended that you activate this feature to protect your organization from unwanted contact from malicious users. The rollout will take place in early November 2024 and is expected to be completed by mid-November 2024. This post is associated with Microsoft 365 Roadmap ID 411138 and the message ID is MC888879.
The post Microsoft Teams: Block a user for your organization originally appeared on M365 Admin.
Published on:
Learn moreRelated posts
Microsoft Teams: Block a user for your organization
In order to prevent malicious users from contacting a victim repeatedly, Microsoft Teams is introducing a new "block user" API for admins to u...
Microsoft Teams: Block users from joining externally hosted Teams meetings
Microsoft Teams is introducing a new feature that allows tenant admins to regulate whether certain users in their organization can join extern...
Microsoft Teams Connect chat – Extended Directory
Microsoft Teams is introducing an extended directory for Teams Connect chat which allows IT admins to create an external directory of known co...
Microsoft Teams: Chat between multi-tenant organization contacts will default to external chat
Microsoft Teams is introducing a new default setting for 1:1 chat between contacts in a multi-tenant organization (MTO). This change will crea...
Microsoft Teams: App centric management in Teams Admin Center to manage the Apps access for tenants, end-users, and groups
Microsoft Teams has introduced new admin settings to provide app-centric management for Teams app store. Admins can now control who in the ten...
Microsoft Purview compliance portal: Communication Compliance – User scoping role-based access control (RBAC)
Microsoft has added new role-based access control (RBAC) to their Purview compliance portal, allowing for delegate management of communication...
Microsoft Teams: Block Anonymous Users’ Meeting Chat Read Access in Addition to Current Write Access
Microsoft Teams has introduced a new feature that allows IT admins to block anonymous users from accessing the chat in internally hosted meeti...
Microsoft Purview Data Lifecycle Management: Retention policy support for Microsoft Teams control messages
Microsoft Teams control messages are system-generated artifacts that contain information about actions taken in Teams, such as adding or remov...
Microsoft Viva: Feature Access Management
With Microsoft Viva, administrators can now manage designated Viva Engage features for specific users through the Microsoft 365 admin center. ...
Microsoft Teams: Group Chat Invitations From Unmanaged Users
Microsoft Teams is rolling out a new feature related to external access. Users receiving group chat invitations from an unmanaged Teams user w...