Recommended Free Tools
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Microsoft canceled the planned mailbox-level External Recipient Rate Limit (ERR) on January 6, 2026. The proposed cap of 2,000 external recipients per mailbox in a rolling 24-hour period was never implemented, so administrators do not need to change configurations or migrate mail solely because of that announcement.
However, Exchange Online still enforces a 10,000-recipient mailbox limit, a tenant-wide external-recipient quota, message-rate controls, and additional domain and anti-abuse protections.
The short answer
The 2,000-recipient limit was part of Microsoft’s April 15, 2024 proposal to add a mailbox-level External Recipient Rate (ERR) limit. The later version of Microsoft’s announcement said enforcement would begin in April 2026, but Microsoft canceled the rollout indefinitely on January 6, 2026, before it took effect. Microsoft’s cancellation notice says the policy “will not go into effect.”
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →That cancellation applies only to the proposed mailbox ERR. It did not remove Exchange Online’s existing mailbox Recipient Rate Limit, Tenant External Recipient Rate Limit (TERRL), message throttles, or anti-spam controls.
#1 Best Overall
What Microsoft originally announced
In its April 2024 announcement, Microsoft proposed limiting each user or mailbox to 2,000 external recipients in a rolling 24-hour period. An external recipient was an address outside the tenant’s accepted domains. The proposed ERR would have been a sub-limit within the existing 10,000-recipient mailbox limit, not an additional 2,000 recipients on top of it.
Microsoft said the measure was intended to reduce abuse and prevent line-of-business applications from using ordinary Exchange Online mailboxes as bulk-mail infrastructure. The announcement also reiterated that Exchange Online is designed for normal business correspondence, not high-volume commercial or transactional delivery.
The historical announcement contains references to different rollout dates as it was revised. The later wording specified April 2026; January 2025 should not be presented as the final implementation date.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →What changed on January 6, 2026
Microsoft withdrew the cloud-hosted mailbox ERR indefinitely. The planned 2,000-external-recipient threshold was therefore never enforced in Exchange Online. Treating it as an active April 2026 quota is incorrect.
“Indefinitely canceled” is more precise than “permanently abolished”: Microsoft has not promised that no similar policy will ever be considered. It has, however, clearly stated that this implementation will not go into effect.
Rank #2
Limits that still apply
| Control | Current position |
|---|---|
| Mailbox External Recipient Rate Limit | Proposed 2,000 external recipients per 24 hours; canceled and not implemented |
| Mailbox Recipient Rate Limit | 10,000 total recipients per rolling 24 hours for the plans listed in Microsoft’s documentation |
| Tenant External Recipient Rate Limit (TERRL) | Tenant-wide external-recipient quota; value depends on licensing and tenant circumstances |
| Single-message recipient limit | Configurable within Microsoft’s supported range, up to 1,000 recipients |
| Message rate | 30 messages per minute for the listed Exchange Online plans |
Default onmicrosoft.com sending |
100 external recipients per organization in a rolling 24-hour period |
| Meeting messages | Separate maximum of 5,000 recipients |
See Microsoft’s current Exchange Online limits documentation for plan-specific qualifications and changes.
The 10,000-recipient mailbox limit
The existing Recipient Rate Limit counts total recipients—internal and external—over a sliding 24-hour window. It is not a midnight-to-midnight allowance.
Free tools Windows power users keep installed
One-click scans. No signup required.
For example, a mailbox that sends to 5,000 recipients at 9:00 a.m., then 2,500 at 10:00 a.m. and another 2,500 at 11:00 a.m. reaches 10,000. It cannot send additional recipients until the first batch falls outside the rolling window at 9:00 a.m. the following day.
Delegated sending is attributed to the user or delegate with the sending permission, rather than simply the mailbox displayed in the From field. An organization address-book distribution group counts as one recipient for this mailbox limit; personal distribution lists and contact-folder groups count their members individually.
The tenant-wide external-recipient limit
TERRL is separate from the canceled mailbox ERR. It limits external recipients sent by the entire tenant during a rolling 24-hour period. The threshold is license-dependent, and trial tenants are capped at 5,000 external recipients per day.
Administrators can inspect the tenant’s current position in Exchange admin center → Reports → Mail flow → Tenant Outbound External Recipients. A tenant can hit TERRL even when no individual mailbox is near 10,000 recipients.
Microsoft classifies a recipient as external when its domain is not an accepted domain in the tenant. This includes recipients in another organization’s Microsoft 365 tenant—not only Gmail, Yahoo, or other consumer services.
Distribution groups can consume the tenant quota quickly
The counting rules differ by control. For TERRL, external distribution-group members are counted individually after groups and nested groups are expanded. A group containing 1,000 external members can therefore consume 1,000 units of the tenant’s external-recipient allowance.
This matters for partner lists, guest-heavy company announcements, dynamic groups, nested groups, and applications that send to a group instead of enumerating recipients. Adding an unrelated domain as an accepted domain is not a legitimate way to bypass anti-abuse controls.
Other restrictions administrators should not confuse with ERR
- 30 messages per minute: message-rate throttling is distinct from recipient quotas.
- 1,000 recipients in one message: this is a per-message ceiling, not a daily allowance.
- Encrypted messages: Microsoft documents an approximate 200-recipient maximum, depending on address length and encryption policy.
- Meeting invitations and updates: these have a separate 5,000-recipient maximum.
onmicrosoft.comthrottle: sending from the default domain is limited to 100 external recipients per organization in a rolling 24-hour period. Throttling can produce NDR code550 5.7.236.
How to diagnose a sending failure now
- Check tenant usage: open the Tenant Outbound External Recipients report in the Exchange admin center.
- Check mailbox activity: calculate total recipients sent by the relevant sender over the preceding rolling 24 hours, including internal recipients.
- Inspect message trace and the NDR: identify whether the failure is a quota, message-rate, domain, recipient-count, spam, or abuse decision.
- Review group expansion: determine how many external members nested or dynamic groups produce.
- Check the sending domain: confirm whether the application is using a default
onmicrosoft.comaddress. - Allow for sliding windows: a quota does not necessarily reset at midnight; earlier activity must age out.
If the problem persists after published limits are ruled out, treat it as a possible reputation, compromise, policy, or anti-abuse issue rather than assuming the canceled ERR is responsible.
Should you move bulk or application email elsewhere?
Cancellation does not make Exchange Online a bulk-email platform. Ordinary employee correspondence and occasional business announcements remain appropriate workloads, but recurring newsletters, marketing, password resets, receipts, alerts, and customer notifications should normally use a specialized sending service.
Do not distribute one campaign across many ordinary user mailboxes to evade limits. That approach complicates auditing and compliance, can damage sender reputation, and may trigger abuse detection or account restrictions.
Azure Communication Services Email
Azure Communication Services is the natural option for Azure-first organizations sending application-generated mail through an API. It is a separate service—not an Exchange quota extension—and still requires domain authentication, consent controls, bounce processing, and deliverability management. See the email quickstart and verify current regional pricing on Microsoft’s pricing page.
Other email service providers
AWS-native teams may evaluate Amazon SES; teams needing broader templates, analytics, and campaign tooling may consider Twilio SendGrid; and developer-focused teams may evaluate Mailgun. Their pricing, quotas, terms, and deliverability requirements change, so consult each provider directly. None guarantees inbox placement or removes legal, consent, suppression-list, or abuse obligations.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsQuick Recap
Administrator action plan
- Do not migrate solely because of the canceled 2,000-recipient ERR.
- Record the tenant’s TERRL and monitor the Tenant Outbound External Recipients report.
- Inventory CRM systems, scripts, multifunction devices, applications, and workflows that send through Exchange Online.
- Measure both per-mailbox total recipients and tenant-wide external recipients.
- Review group expansion and external members.
- Replace default
onmicrosoft.comsending with an appropriately configured custom domain where required; do not treat this as a quota bypass. - For recurring or high-volume external mail, design an approved sending architecture with retry, bounce, unsubscribe, suppression, authentication, and compliance handling.
- Monitor future Microsoft announcements: the ERR was canceled indefinitely, while anti-abuse controls remain active.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
