*For this entry exists the more relevant or more recent entry MC888879
check before: 2025-01-01
Product:
Teams
Platform:
Android, iOS, Mac, Windows Desktop, World tenant
Status:
Launched
Change type:
Links:

Details:
With the availability of the delete API (removeallaccessforuser API), it does not stop the malicious user from resending the message to the same victim. To help prevent that, a block user API will allow the admin to block the malicious user from reaching out again. To make this even more effective, we will utilize a similar feature as the allow/block list in federation to block the malicious user from the entire organization.
Change Category:
XXXXXXX ... free basic plan only
Scope:
XXXXXXX ... free basic plan only
Release Phase:
General Availability
Created:
2024-08-13
updated:
2025-02-08
Docu to Check
XXXXXXX ... free basic plan only
MS workload name
XXXXXXX ... free basic plan only
Direct effects for Operations**
- Direct Impact on IT Operations
- Increased administrative workload for IT administrators
- Need for training on the new block user API and its implementation
- Potential for increased support tickets related to user blocking and unblocking
- Changes in user management processes
- Updates to existing user access policies and procedures
- Coordination with security teams to ensure compliance with data protection regulations
- Impact on IT Services
- Potential downtime or service interruptions during the implementation of the block user API
- Risk of affecting other Teams functionalities while the API is being integrated
- Dependencies on other Microsoft services (e.g., Azure Active Directory) that may be impacted during the change
- Changes in user experience for Teams users
- Users may experience delays in communication if blocked users are not immediately removed from contact lists
- Possible confusion among users regarding the new blocking feature and its implications
- Impact on IT Users
- Enhanced security for end-users
- Users will have a safer environment as malicious users can be blocked organization-wide
- Increased trust in the platform, leading to higher user satisfaction
- Potential for user frustration
- Users may inadvertently block legitimate contacts if not properly trained on the new feature
- Misunderstandings about the blocking process could lead to communication breakdowns
Roles Most Impacted:
- IT Administrators
- Security Teams
- End Users (Employees using Microsoft Teams)
References:
- Microsoft Teams Documentation: [Block a user for your organization](https://docs.microsoft.com/en-us/microsoftteams/block-a-user)
- Microsoft 365 Compliance Center: [Managing user access](https://docs.microsoft.com/en-us/microsoft-365/compliance/manage-user-access)
Opportunities**
- Implement User Blocking API in Microsoft Teams
- Leverage the new block user API to enhance security and user experience by preventing malicious users from re-engaging with victims within the organization.
- Major roles benefiting: IT Security Team, Compliance Officers
- Create a centralized management dashboard for monitoring blocked users and their activities, allowing for quick response to potential threats.
- Major roles benefiting: IT Operations, IT Administration
- Enhance User Education and Awareness Programs
- Develop training sessions focused on recognizing and reporting malicious behavior in Teams, utilizing the new blocking feature as a key point in the curriculum.
- Major roles benefiting: HR Training Coordinators, Team Leaders
- Distribute regular updates and best practices on using Teams securely, including how to effectively use the block feature.
- Major roles benefiting: All employees, IT Support Staff
- Optimize Licensing and Cost Management
- Review current licensing agreements for Microsoft Teams to identify potential savings by consolidating licenses or downgrading unused features, especially in light of the new API functionalities.
- Major roles benefiting: Finance Department, IT Administration
- Explore alternative communication tools that may offer similar functionalities at a lower cost, while ensuring they meet security and compliance standards.
- Major roles benefiting: IT Operations, Procurement Team
References:
- Microsoft Teams User Blocking API: [Microsoft Documentation](https://docs.microsoft.com/en-us/microsoftteams/platform/overview)
- Security Best Practices for Microsoft Teams: [Microsoft Security Blog](https://techcommunity.microsoft.com/t5/security-compliance-identity/best-practices-for-securing-microsoft-teams/ba-p/123456)
Potentional Risks**
XXXXXXX ... paid membership 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 |
2025-02-08 | RM Status | Rolling out | Launched |
2025-01-28 | RM Status | In development | Rolling out |
2024-11-21 | RM Release | December CY2024 | January CY2025 |
2024-10-09 | RM Release | November CY2024 | December CY2024 |
2024-09-13 | RM Release | October CY2024 | November CY2024 |
Last updated 6 days ago