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 13:25 UTC Customize Public modeDiscuss ChangeIntel on Discord

External messaging limits for onmicrosoft.com-only organizations in Microsoft Teams

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

Rollout

Ends
23 Nov 2026

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

Microsoft's start date
28 Aug 2026
Last changed by Microsoft
28 Aug 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

What and Why

To help protect Microsoft Teams users from spam, phishing, and other abusive activity, Microsoft is introducing outbound external messaging limits for organizations that use only the default Microsoft Online Email Routing Address (MOERA) domain, such as contoso.onmicrosoft.com.

These limits are designed to reduce large-scale abuse while preserving normal collaboration scenarios. Most organizations using Teams for standard business communications are not expected to reach these limits.

Rollout Schedule

  • General Availability (Worldwide): Rollout begins in mid-September 2026 and is expected to complete by mid-September 2026.

Impact on Your Organization

Who is affected

Organizations that use only the default onmicrosoft.com domain and have not configured a custom domain.

Platforms/Services

  • Microsoft Teams
  • External chat and messaging

What will happen

  • Outbound Teams messages sent to external users will be subject to messaging limits intended to reduce abusive or high-volume activity.
  • When an applicable limit is reached, users may be temporarily unable to send messages to external users.
  • Users will see an in-product notification indicating that outbound external messaging has been temporarily limited.
  • Internal Teams messaging and collaboration within your organization will not be affected.
  • External messaging capabilities will automatically resume when activity falls below the applicable threshold.

The protection is enabled by default and does not require administrator configuration.

An optional administrator alert for throttling events will become available after the initial rollout. This post will be updated when information about enabling the alert is available.

Action Required / Recommendations

If your organization relies on the default onmicrosoft.com domain for production use, review your domain configuration before rollout.

  • Verify whether your organization uses only the default onmicrosoft.com domain.
  • If appropriate, add and configure a custom domain for your Microsoft 365 organization.
  • Inform help desk personnel and Teams administrators that users may encounter temporary outbound external messaging restrictions if applicable limits are reached.
  • Review the Teams limits and specifications documentation for additional guidance.

No action is required for organizations that already have a custom domain configured.

Additional Information

This change helps reduce spam and other abusive activity originating from tenants that use only the default onmicrosoft.com domain while maintaining normal collaboration experiences for legitimate users.

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