Published Sep 5, 2025
Microsoft Teams will roll out malicious URL protection in chats and channels starting September 2025, warning users of phishing links. The feature requires admin activation during preview and will be on by default at general availability in November 2025. It uses reputation-based scanning via Microsoft Defender.
Updated September 9, 2025: We have updated the content. Thank you for your patience.
Introduction
Microsoft Teams is introducing enhanced protection against phishing attacks by detecting and warning users about malicious URLs shared in Teams chats and channels. This feature helps users make safer decisions before clicking potentially harmful links. This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android.
This message is associated with Roadmap ID 499893.
When this will happen
How this affects your organization
When a malicious link is detected, Teams will automatically display a warning to both the sender and recipient. This helps reduce the risk of phishing attacks.
Targeted release vs. General Availability behavior:
What you can do to prepare
During Public Preview, administrators must manually enable the feature:
This setting is also available via Set-CsTeamsMessagingConfiguration
PowerShell cmdlet -UrlReputationCheck parameter.
No action is required once the feature reaches General Availability, as it will be turned on by default.
Learn more: Malicious URL Protection in Microsoft Teams
Compliance considerations
Compliance Area | Explanation |
---|---|
Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data? | URL scanning uses reputation-based detection algorithms to identify malicious links. This involves scanning user messages and performing reputation lookups against Microsoft Defender for Office's managed collection. |
Does the change include an admin control that can be scoped using Entra ID group membership? | Admins can enable or disable the feature via Teams Admin Center or PowerShell. However, scoping via Entra ID group membership is not supported. |