Public mode

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

Some sources or documents need attention: 253/255 feeds/APIs · 417/444 docs · checked 12:24 UTC Customize Public modeDiscuss ChangeIntel on Discord

(Updated) Microsoft Teams: QR code protection for messages from external users

Versions captured by this deployment. Earlier versions and notices may be missing; first observed is not first published.

Rollout

Ends
30 Nov 2026
Roadmap
570439
Platforms
Android, Desktop, iOS, Mac, Web

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

Microsoft's start date
10 Sep 2026
Last changed by Microsoft
6 Oct 2026
First seen here
19 Oct 2026
Versions seen
1

What the notice says

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

Updated October 6, 2026: We have updated the timeline. Thank you for your patience.

What and why

Microsoft Teams is introducing additional protection for QR codes shared by external users in Teams messages. To help reduce the risk of phishing and fraud, images containing QR codes from external senders will be obscured by default. Users can choose to reveal the image before viewing or scanning the QR code.

This security enhancement promotes safer interactions with content received from external users while maintaining flexibility for trusted communications.

Rollout schedule

  • Targeted Release: Beginning in mid-October 2026 (previously early October) and expected to complete in mid-October 2026 (previously early October)
  • General Availability (Worldwide): Beginning in late October 2026 (previously mid-October) and expected to complete by late October 2026 (previously mid-October)

Impact on your organization

Who is affected

  • Organizations that allow communication with external users in Microsoft Teams.
  • Users who receive Teams messages from external senders.
  • Teams administrators and support teams that manage external collaboration policies.

Platforms and services

  • Microsoft Teams
  • Teams desktop
  • Teams web
  • Teams mobile

What will happen

  • Images containing QR codes sent by external users will be blurred by default in Teams messages.
  • Users can reveal the image if they trust the sender and want to view or scan the QR code.
  • The blurred image does not indicate that Microsoft Teams has determined the QR code to be malicious.
  • The protection is applied automatically to QR code images received from external senders.
  • No administrator configuration or policy changes are required.
  • The feature will be enabled by default as part of the rollout.

Action required and recommendations

No admin action is required before rollout.

We recommend that administrators:

  • Inform users that QR code images from external senders may appear blurred by default.
  • Remind users to verify the sender before revealing or scanning QR codes.
  • Review existing user education materials related to phishing awareness, QR code safety, and external collaboration.
  • Update internal help desk documentation to reflect the new user experience.

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 12:24 UTC · 253 of 255 readable · 252 fully read · documentation 417/444 current