Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

(Updated) Microsoft Teams: Malicious QR code detection in messages

Returned by 2 reference tenants · Corroborated by Microsoft 365 Message Center Archive by Merill Fernando

Rollout

Roadmap
576198
Platforms
Android, Desktop, iOS, Mac, Web

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions this installation saw
  • Seen 10 Nov 2026 early November 2026 → late November 2026

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, safely structured

Updated November 10, 2026: We have updated the timeline. Thank you for your patience.

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 mid-November 2026 (previously early November) and expected to complete by late November 2026 (previously mid-November)

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.

What changed

Between the versions this installation saw, newest first
    • Title Microsoft Teams: Malicious QR code detection in messages → (Updated) Microsoft Teams: Malicious QR code detection in messages
    • Notice end date 13 Dec 2026 → 31 Dec 2026
    • Tags New feature, User impact, Admin impact → Updated message, New feature, User impact, Admin impact

    Updated November 10, 2026: We have updated the timeline. Thank you for your patience.  [What and why] Microsoft Teams is extending malicious URL protection to provide … when malicious content is detected. [Rollout schedule] General Availability (Worldwide): Beginning in mid-November 2026 (previously early November 2026 November) and expected to complete in mid-Novemberby late November 2026 (previouslymid-November) [Impact on your organization] Who is affected Users who use Microsoft Teams … documentation about Teams messaging security and update it if necessary. Learn more (Both to be updated closer to rollout.) Make sure chats, links, and files are secure in Microsoft Teams | … 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.

  1. · first version seen

These are the archive's capture times. They are separate from the versions returned by our reference tenants.

Read the archive's current copy

Updated November 10, 2026: We have updated the timeline. Thank you for your patience.  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 mid-November 2026 (previously early November) and expected to complete by late November 2026 (previouslymid-November) 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.) Make sure chats, links, and files are secure in Microsoft Teams | Microsoft Support Malicious URL protection in Microsoft Teams - Microsoft Teams | Microsoft Learn Compliance considerations No compliance considerations identified. Review as appropriate for your organization.

  1. Microsoft Teams: Malicious QR code detection in messages Action date: Not supplied
  2. Microsoft Teams: Malicious QR code detection in messages Action date: Not supplied

Learn more

Links from the notice and their documentation checks

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • 2 linked pages have not been read yet.
  • Some history or links were left out of the website export to keep it within its size limits.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 13 Nov 14:14 UTC · 274 of 275 readable · 273 fully read · documentation 469/469 current