check before: 2024-10-01
Product:
Teams
Platform:
Android, iOS, Mac, Online, Windows Desktop, World tenant
Status:
In development
Change type:
Admin impact, New feature, Updated message
Links:
Details:
Summary:
Microsoft Teams is introducing a block user feature allowing admins to prevent malicious users from contacting the organization again. This feature, associated with Microsoft 365 Roadmap ID 411138, will roll out in mid-January 2025 and be completed by late January 2025. Admins need to turn on this feature and configure the block list in external access settings.
Details:
Updated November 20, 2024: We have updated the rollout timeline below. Thank you for your patience.
The availability of the delete API (removeallaccessforuser API) does not stop a malicious user from resending a Microsoft Teams message to the same victim. To help prevent that, a block user feature will allow the admin to block the malicious user from reaching out again. To make this possible, we will use a similar feature as the allow/block list in federation identity credentials to block the malicious user from the entire organization.
This message is associated with Microsoft 365 Roadmap ID 411138.
[When this will happen:]
General Availability (Worldwide): We will begin rolling out mid-January 2025 (previously early December) and expect to complete by late January 2025 (previously mid-December).
Change Category:
XXXXXXX ... free basic plan only
Scope:
XXXXXXX ... free basic plan only
Release Phase:
General Availability
Created:
2024-09-13
updated:
2024-11-21
Task Type
XXXXXXX ... free basic plan only
Docu to Check
XXXXXXX ... free basic plan only
MS How does it affect me
XXXXXXX ... free basic plan only
MS Preperations
XXXXXXX ... free basic plan only
MS Urgency
XXXXXXX ... free basic plan only
MS workload name
XXXXXXX ... free basic plan only
linked item details
XXXXXXX ... free basic plan only
summary for non-techies**
XXXXXXX ... free basic plan only
Direct effects for Operations**
User Communication Disruption
If the block user feature is implemented without proper preparation, users may experience unexpected disruptions in their communication, as blocked users will be removed from existing chats, potentially leading to confusion and loss of important conversations.
- roles: End Users, IT Support
- references: https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=411138
Increased Support Requests
The sudden implementation of the block user feature may lead to an increase in support requests from users who are confused about the new functionality and its implications, overwhelming the IT support team.
- roles: IT Support, Helpdesk Staff
- references: https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=411138
Misconfiguration Risks
Without adequate preparation, there is a risk of misconfiguring the block list settings, which could inadvertently block legitimate users, impacting collaboration and productivity.
- roles: Admins, Team Leaders
- references: https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=411138
Configutation Options**
XXXXXXX ... paid membership only
Opportunities**
XXXXXXX ... free basic plan only
Potentional Risks**
XXXXXXX ... paid membership only
IT Security**
XXXXXXX ... paid membership only
explanation for non-techies**
XXXXXXX ... free basic plan only
** AI generated content. This information must be reviewed before use.
a free basic plan is required to see more details. Sign up here
A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.
change history
| Date | Property | old | new |
| 2024-11-21 | MC Last Updated | 10/10/2024 01:34:54 | 2024-11-20T23:48:44Z |
| 2024-11-21 | MC Messages | Updated October 9, 2024: We have updated the rollout timeline below. Thank you for your patience.
The availability of the delete API (removeallaccessforuser API) does not stop a malicious user from resending a Microsoft Teams message to the same victim. To help prevent that, a block user feature will allow the admin to block the malicious user from reaching out again. To make this possible, we will use a similar feature as the allow/block list in federation identity credentials to block the malicious user from the entire organization. This message is associated with Microsoft 365 Roadmap ID 411138. [When this will happen:] General Availability (Worldwide): We will begin rolling out early December 2024 (previously early November) and expect to complete by mid-December 2024 (previously mid-November). | Updated November 20, 2024: We have updated the rollout timeline below. Thank you for your patience.
The availability of the delete API (removeallaccessforuser API) does not stop a malicious user from resending a Microsoft Teams message to the same victim. To help prevent that, a block user feature will allow the admin to block the malicious user from reaching out again. To make this possible, we will use a similar feature as the allow/block list in federation identity credentials to block the malicious user from the entire organization. This message is associated with Microsoft 365 Roadmap ID 411138. [When this will happen:] General Availability (Worldwide): We will begin rolling out mid-January 2025 (previously early December) and expect to complete by late January 2025 (previously mid-December). |
| 2024-11-21 | MC End Time | 01/27/2025 09:00:00 | 2025-03-03T09:00:00Z |
| 2024-11-21 | MC Summary | Microsoft Teams is introducing a block user feature allowing admins to prevent malicious users from contacting the organization again. This feature, associated with Microsoft 365 Roadmap ID 411138, will roll out in early December 2024 and be completed by mid-December 2024. Admins need to turn on this feature and configure the block list in external access settings. | Microsoft Teams is introducing a block user feature allowing admins to prevent malicious users from contacting the organization again. This feature, associated with Microsoft 365 Roadmap ID 411138, will roll out in mid-January 2025 and be completed by late January 2025. Admins need to turn on this feature and configure the block list in external access settings. |
| 2024-10-10 | MC Last Updated | 09/14/2024 00:29:39 | 2024-10-10T01:34:54Z |
| 2024-10-10 | MC Messages | Updated September 13, 2024: We have updated the rollout timeline below. Thank you for your patience.
The availability of the delete API (removeallaccessforuser API) does not stop a malicious user from resending a Microsoft Teams message to the same victim. To help prevent that, a block user feature will allow the admin to block the malicious user from reaching out again. To make this possible, we will use a similar feature as the allow/block list in federation identity credentials to block the malicious user from the entire organization. This message is associated with Microsoft 365 Roadmap ID 411138. [When this will happen:] General Availability (Worldwide): We will begin rolling out early November 2024 (previously late October) and expect to complete by mid-November 2024 (previously early November). | Updated October 9, 2024: We have updated the rollout timeline below. Thank you for your patience.
The availability of the delete API (removeallaccessforuser API) does not stop a malicious user from resending a Microsoft Teams message to the same victim. To help prevent that, a block user feature will allow the admin to block the malicious user from reaching out again. To make this possible, we will use a similar feature as the allow/block list in federation identity credentials to block the malicious user from the entire organization. This message is associated with Microsoft 365 Roadmap ID 411138. [When this will happen:] General Availability (Worldwide): We will begin rolling out early December 2024 (previously early November) and expect to complete by mid-December 2024 (previously mid-November). |
| 2024-10-10 | MC Summary | Microsoft Teams is introducing a block user feature to prevent malicious users from contacting an organization again. This feature, associated with Microsoft 365 Roadmap ID 411138, will be available worldwide in early November 2024. Admins can block users, preventing 1:1 and group chats with them. It's off by default and can be enabled in external access settings. | Microsoft Teams is introducing a block user feature allowing admins to prevent malicious users from contacting the organization again. This feature, associated with Microsoft 365 Roadmap ID 411138, will roll out in early December 2024 and be completed by mid-December 2024. Admins need to turn on this feature and configure the block list in external access settings. |
| 2024-10-10 | MC MessageTagNames | New feature, Admin impact | Updated message, New feature, Admin impact |
| 2024-10-10 | MC End Time | 12/28/2024 09:00:00 | 2025-01-27T09:00:00Z |
| 2024-09-14 | MC Messages | The availability of the delete API (removeallaccessforuser API) does not stop a malicious user from resending a Microsoft Teams message to the same victim. To help prevent that, a block user feature will allow the admin to block the malicious user from reaching out again. To make this possible, we will use a similar feature as the allow/block list in federation identity credentials to block the malicious user from the entire organization.
This message is associated with Microsoft 365 Roadmap ID 411138. [When this will happen:] General Availability (Worldwide): We will begin rolling out late October 2024 and expect to complete by early November 2024. | Updated September 13, 2024: We have updated the rollout timeline below. Thank you for your patience.
The availability of the delete API (removeallaccessforuser API) does not stop a malicious user from resending a Microsoft Teams message to the same victim. To help prevent that, a block user feature will allow the admin to block the malicious user from reaching out again. To make this possible, we will use a similar feature as the allow/block list in federation identity credentials to block the malicious user from the entire organization. This message is associated with Microsoft 365 Roadmap ID 411138. [When this will happen:] General Availability (Worldwide): We will begin rolling out early November 2024 (previously late October) and expect to complete by mid-November 2024 (previously early November). |
| 2024-09-14 | MC Title | Microsoft Teams: Block a user for your organization | (Updated) Microsoft Teams: Block a user for your organization |
| 2024-09-14 | MC Last Updated | 09/13/2024 01:12:05 | 2024-09-14T00:29:39Z |
| 2024-09-14 | MC Summary | Microsoft 365 Roadmap ID 411138 introduces a block user feature for Teams, allowing admins to prevent malicious users from contacting the organization. Rolling out from late October to early November 2024, it requires admins to enable the feature and add users to the block list. | Microsoft Teams is introducing a block user feature to prevent malicious users from contacting an organization again. This feature, associated with Microsoft 365 Roadmap ID 411138, will be available worldwide in early November 2024. Admins can block users, preventing 1:1 and group chats with them. It's off by default and can be enabled in external access settings. |
Last updated 2 weeks ago
