Public mode

No tenant, Graph, or device access. Every item links to its source. What this means

Some sources or documents need attention: 257/260 feeds/APIs · 416/444 docs · checked 15:16 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Defender for Office 365: Post-delivery protection for malicious QR codes in Microsoft Teams

Rollout

Ends
2 Dec 2026

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

What the notice says

Microsoft's text, with its sections, lists and tables; source markup removed

What and why

We're extending Microsoft Teams URL protection in Microsoft Defender for Office 365 to detect and respond to malicious URLs embedded in QR codes. As attackers increasingly use QR codes to conceal malicious destinations, this update helps protect users by analyzing URLs extracted from QR codes after message delivery and applying post-delivery protections when malicious content is identified.

For organizations using Microsoft Defender for Office 365, this enhancement builds on existing Teams URL protection capabilities and improves visibility for security operations teams investigating QR-code-based threats. Security teams will also be able to identify QR code URL detections in Advanced Hunting through the MessageUrlInfo table.

Rollout schedule

  • General Availability (Worldwide): Beginning in early October 2026 and expected to complete by early November 2026

Impact on your organization

Who is affected

  • Organizations using Microsoft Teams with Microsoft Defender for Office 365
  • Organizations using Microsoft Teams
  • Organizations licensed for Microsoft Defender for Office 365
  • Security operations teams that use Microsoft Defender XDR Advanced Hunting
  • Organizations that have Zero-hour Auto Purge (ZAP) for Teams enabled can receive additional protection for eligible internal messages

Platforms and services

  • Microsoft Teams
  • Microsoft Defender for Office 365
  • Microsoft Defender XDR Advanced Hunting

What will happen

  • Teams messages containing QR codes will be analyzed after message delivery.
  • URLs extracted from QR codes will be evaluated for malicious content.
  • When a malicious URL is identified in an external conversation, users will see a warning on the affected Teams message.
  • When a malicious URL is identified in an internal conversation, users will see a warning on the affected Teams message.
  • Organizations with Microsoft Defender for Office 365 Plan 1 or Plan 2 and Teams ZAP enabled may have eligible malicious internal messages blocked through existing post-delivery protection mechanisms.
  • Security teams will gain visibility into QR code URL detections through Advanced Hunting.
  • URLs extracted from QR codes will appear with QRCode in the UrlLocation column of the MessageUrlInfo table.
  • The feature is enabled as part of existing Teams URL protection capabilities. No separate end-user configuration is required.

Screenshot 1 - QR-code-blocking:

Screenshot 2 - QR-warning-protection:

Screenshot 3 - QR-Code Advanced Hunting:

Action required and recommendations

No action is required.

We recommend that administrators:

  • Review existing Microsoft Defender for Office 365 Teams protection settings and Teams ZAP configuration to understand how blocking behavior applies in your organization.
  • Inform security operations teams that QR code URL detections will become available in Advanced Hunting.
  • Review your incident investigation and threat hunting processes to incorporate QR code detections where applicable.

Learn more

Compliance considerations

No compliance considerations identified, review as appropriate for your organization.

What changed

Between the versions this installation saw, newest first

This installation has seen one version of this notice, first on 19 Oct 2026. Later changes will show here.

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

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.
  • Versions before 19 Oct 2026: this installation first saw the notice after Microsoft posted it.
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 19 Oct 15:16 UTC · 257 of 260 readable · 255 fully read · documentation 416/444 current