MC1526651 - Microsoft Teams: Malicious QR code detection in messages
Microsoft 365 Message Center announcement MC1526651.
MS Message Center's Summary
Microsoft Teams is introducing malicious QR code detection in chats and channels starting in early November 2026 and completing by mid November 2026. This feature automatically scans QR code destinations for phishing and fraud threats and displays security warnings. It relies on the existing malicious URL protection setting which is enabled by default. Administrators should inform help desks and users about the upcoming warning messages.
- Administrator impact
- No direct administrator action is required.
- End user impact
- Users will see security warnings when Microsoft Teams detects malicious QR codes in messages.
- Importance
- 4/10: This is a security enhancement with default activation and no required configuration.
Make sure chats, links, and files are secure in Microsoft Teams
Microsoft Summary
Microsoft Teams will detect malicious QR codes in messages, providing warnings for phishing or fraud threats starting November 2026. This applies to chats and channels, with QR code blurring for external senders. The feature is enabled by default via Malicious URL protection, requiring no admin action.
- Message Center ID
- MC1526651
- Category
- stay Informed
- Severity
- normal
- Services
- Microsoft Teams
- Tags
- New feature, User impact, Admin impact
- Roadmap ID
- 576198
- Platforms
- Android, Desktop, iOS, Mac, Web
- Published
- 2026-10-26
- Last updated
- 2026-10-26
- Expires
- 2026-12-13
[What and why] Microsoft Teams is extending malicious URL protection to provide near-real-time detection of malicious destinations embedded in QR codes shared in messages. Teams will analyze QR code destinations to identify potential phishing and fraud threats and display an additional warning when malicious content is detected. [Rollout schedule] General Availability (Worldwide): Beginning in early November 2026 and expected to complete in mid-November 2026 [Impact on your organization] Who is affected Users who use Microsoft Teams messaging Platforms and services Microsoft Teams chats, meeting chats, and channels What will happen Teams will decode and evaluate QR code destinations in inline images shared in 1:1 chats, group chats, meeting chats, and channels. Detection applies to internal and external communications. Images containing QR codes from external senders are already blurred by default. When Teams identifies a malicious QR code, users will also see the warning, “ This message contains a link that might be harmful, ” and a “ Learn about file and link safety ” link. QR code images from internal senders are not blurred by default. The same warning will appear when Teams detects a malicious QR code. For users on Teams mobile in China, QR code images are blurred by default regardless of whether the sender is internal or external, and any messages containing malicious QR code will be blocked. Malicious QR code detection is managed by the existing Malicious URL protection setting. The setting is enabled by default. Organizations with Malicious URL protection enabled will automatically receive malicious QR code detection as the feature rolls out. No separate configuration is available or required for malicious QR code detection. [Action required and recommendations] No admin action is required. Admins can review or change the existing Malicious URL protection setting in Teams admin center > Settings and policies > Messaging Safety . We recommend that you: Inform users and help desk staff about the additional warning for detected malicious QR codes. Clarify that QR code blurring is a separate precautionary experience and does not mean that Teams has identified a QR code as malicious. Review internal documentation about Teams messaging security and update it if necessary. Learn more Make sure chats, links, and files are secure in Microsoft Teams | Microsoft Support Malicious URL protection in Microsoft Teams - Microsoft Teams | Microsoft Learn (Both to be updated closer to rollout.) [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization.