Public mode

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

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 20:54 UTC Customize Public modeDiscuss ChangeIntel on Discord

Teams admin center: Messaging safety defaults changing to "On" by default

From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

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, safely structured

Introduction

We’re improving messaging security in Microsoft Teams by enabling key safety protections by default. This update helps safeguard users from malicious content and provides options to report incorrect detections, reducing risk and improving collaboration security.

When this will happen

Starting January 12, 2026, as announced in MC1148540, MC1148539, and MC1147984.

How this affects your organization

Who is affected

  • Tenants that have not previously modified messaging safety settings and are still using the default configuration.

What will happen

  • The following settings in Teams admin center Messaging Settings will be turned ON by default:
    • Weaponizable file type protection
    • Malicious URL protection
    • Report incorrect security detections
  • End users may:
    • See warning labels on messages containing malicious URLs.
    • Have the option to report false positives.
    • Experience blocked messages if they contain weaponizable file types.
  • If you have already customized and saved these settings, your preferences will remain unchanged.

What you can do to prepare

  • Review current values for these settings in Teams admin center > Messaging > Messaging settings > Messaging safety.
  • If you do not want the new defaults to apply, adjust settings and click Save before January 12, 2026.
  • Communicate this change to helpdesk staff and update internal documentation if necessary.

Learn more

Compliance considerations

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

What changed

Between archive captures, newest first

The archive supplies one version of this notice.

Learn more

Links from the notice and their documentation checks
Other posts named in this one

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

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.
  • 3 linked pages have not been read yet.
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 27 Oct 20:54 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current