Microsoft is rolling out new Teams messaging limits for organizations that still run on the default onmicrosoft.com domain, and if that sounds like your tenant, you have a few weeks to get ready.
Starting mid-September 2026, Microsoft Teams will apply outbound external messaging limits to any tenant that has never configured a custom domain and still relies solely on the default Microsoft Online Email Routing Address, better known as onmicrosoft.com. This is a straightforward anti-abuse measure, not a licensing change, and it will not touch a single message sent inside your own organization. But if your business still uses Teams and Outlook on the default domain for real production work, the new Teams messaging limits can catch you off guard the first time someone on your sales or support team tries to message an external contact and gets blocked.
What Are the New Teams Messaging Limits
Microsoft’s stated goal is simple: reduce the spam, phishing, and large-scale abuse that comes from tenants using only the default onmicrosoft.com domain. Attackers spin up free or trial Microsoft 365 tenants constantly, and because those tenants never bother adding a custom domain, they have historically been an easy way to blast external messages at scale through Teams. The Teams messaging limits close that gap.
Here is what actually changes:
- Outbound Teams messages sent to external users become subject to limits designed to catch abusive or high-volume activity.
- Once a tenant crosses the applicable threshold, users may be temporarily unable to send new messages to people outside the organization.
- Affected users see an in-product notification explaining that outbound external messaging has been temporarily limited.
- Internal Teams messaging and collaboration inside your own organization is not affected in any way.
- External messaging capability comes back automatically once activity drops back under the threshold.
- The protection is on by default. There is nothing to configure to receive it.
Microsoft has also confirmed that an optional administrator alert for throttling events is coming after the initial rollout, though details on enabling it were not yet available at time of writing.
Who Is Affected by the Teams Messaging Limits
This one is easy to check. If your Microsoft 365 tenant has a custom domain configured (think yourcompany.com instead of yourcompany.onmicrosoft.com) and your users send and receive mail and Teams messages from that domain, none of this applies to you. The Teams messaging limits only apply to organizations that rely exclusively on the default onmicrosoft.com domain.
The tenants that should pay attention fall into three buckets:
- Small organizations that set up Microsoft 365 quickly and never got around to adding a verified custom domain.
- Test, dev, or sandbox tenants that were later pressed into production use.
- Any organization where a custom domain was purchased but never actually connected in the Microsoft 365 admin center.
If you are not sure which bucket you are in, check now, not in September.
Rollout Schedule
| Phase | Timing | Availability |
|---|---|---|
| General Availability (Worldwide) | Mid-September 2026 to late-September 2026 | Automatic, no opt-in required |
There is no separate Preview phase for this change. This should be rolling out in September 2026 (General Availability) according to Microsoft.
How to Prepare Before the Teams Messaging Limits Roll Out
You have a short window before this goes live. Here is exactly what to do with it.
Step-by-Step: Fix Your Domain Before the Teams Messaging Limits Apply
- Open the Microsoft 365 admin center and go to Settings > Domains.
- Check whether onmicrosoft.com is your only listed domain. If you see a verified custom domain alongside it, you are already covered.
- If you only have the default domain, decide whether that is intentional. For a genuine test tenant, it may not matter. For anything used in production, it almost certainly does.
- Add and verify a custom domain if your organization needs one. Microsoft’s own domain setup guide walks through DNS verification and record configuration.
- Update your Exchange and Teams settings to use the new domain for outbound identity where relevant.
- Brief your help desk. Make sure whoever handles Teams and Outlook tickets knows that a blocked outbound external message could now be a symptom of these Teams messaging limits, not a bug.
Admin Tips
- Do not wait for a user complaint to discover you are on the default domain. Pull your domain list today, it takes two minutes.
- If you run multiple tenants (agencies, MSPs, holding companies, this one is for you), check every tenant individually. Domain configuration does not roll up.
- Document which tenants are intentionally onmicrosoft.com-only (true sandboxes) so nobody fixes them by accident later.
- Loop in your Teams admins and help desk before mid-September so a legitimate spike in outbound messages, a marketing send or a big onboarding wave, is not mistaken for the new Teams messaging limits kicking in unnecessarily.
Licensing for the Teams Messaging Limits
There is nothing to buy or license here. This protection is a platform-level control that Microsoft applies automatically to any tenant using only the default onmicrosoft.com domain, regardless of your Microsoft 365 or Teams license tier. No admin toggle exists to turn it off; the only way to sidestep the Teams messaging limits is to configure and use a proper custom domain, which is good practice regardless.
The Paul-Take
I still walk into client environments, years into their Microsoft 365 journey, that never got around to adding a custom domain. Usually it is a small business that started on a trial, never circled back, and now runs real client communication through onmicrosoft.com without realizing it. This change will not hurt anyone doing that intentionally in a sandbox. It will absolutely catch the businesses that quietly built production workflows on a domain they never meant to keep.
My advice: treat these Teams messaging limits as a free audit trigger. Go check your domain setup this week. If you find a tenant still on the default domain doing real work, fix it before Microsoft’s throttling does it for you in the middle of a busy week. This should be rolling out in September 2026 (General Availability) according to Microsoft, so there is no reason to leave this until the last minute.
Related reading: If domain and access governance is on your radar, two other recent changes are worth your time. The new Teams Communicator app makes compliance notifications and acknowledgment tracking far easier to manage across the organization. And if oversharing rather than external messaging keeps you up at night, the SharePoint oversharing report gives admins the item-level visibility that has been missing for years.
MVP Reference List:
- Message Center post: MC1463510, “External messaging limits for onmicrosoft.com-only organizations in Microsoft Teams,” published August 28, 2026.
- Microsoft Learn: Limits and specifications for Microsoft Teams
- Microsoft Learn: Add a custom domain to Microsoft 365