Posted inMicrosoft Teams

MC1526651: Microsoft Teams Adds Malicious QR Code Detection to Messaging Security

4 minutesPosted inMicrosoft Teams
MWPRO IMPACT SCORE
OPERATIONAL IMPACT
45
0 25 50 75 100
MODERATE IMPACT • ASSESS BUSINESS IMPACT
Recommended Action:
Take a look and decide whether this affects your tenant, users or support teams.
▶ What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

Teams AdminsMicrosoft 365 AdminsSecurity TeamsIT ManagersService Owners
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
This is an upcoming security enhancement to Teams that extends existing malicious URL protection to include QR codes. Admins do not need to enable or configure anything, but awareness and staff communication are recommended. Users will see new warnings when malicious QR codes are detected, so help desks and documentation may need updates before rollout. The impact is mainly on awareness and user experience rather than configuration or policy changes.
45
🛡️ Admin Impact
MEDIUM
35
👥 User Impact
MEDIUM
55
⚡ Urgency
HIGH
30
🔧 Effort
MEDIUM
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Teams will now detect and warn users about malicious QR codes in messages, extending existing malicious URL protection for safer communication.
👥

END USERS

Users may see warnings when a shared QR code is detected as unsafe in chats or channels.
🛡️

IT ADMINS

Review the Malicious URL protection setting and inform users and help desk teams about new QR code safety warnings.
📅

ROLLOUT TIMELINE

Upcoming:
Early–mid Nov 2026

📢 Official Microsoft Message Center Announcement

Microsoft Teams: Malicious QR code detection in messages
Message ID: MC1526651

[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

(Both to be updated closer to rollout.)

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

Source: Microsoft Message Center • Analysed by MWPro

Share This Update
Tags: