Microsoft 365 Outbound Email Limits: What Your Tenant Can Send

Your Microsoft 365 tenant has a hard ceiling on how many outside people it can email in a day, and it's smaller than most owners assume. A 25-seat tenant can reach roughly 14,000 external recipients per rolling 24 hours. Cross it and Microsoft starts bouncing mail with a 550 5.7.233 error until the window clears.

Most small businesses never come close. The ones that get burned are the ones running a newsletter, a client mailing, or a billing blast out of Exchange Online instead of a proper sending platform.

What is the Tenant External Recipient Rate Limit?

TERRL is a tenant-wide cap on external recipients per 24-hour sliding window. Microsoft defines it as "the maximum number of external recipients a tenant can send to per day," where external means any address whose domain isn't an accepted domain in your tenant (Microsoft Exchange Online limits).

It counts recipients, not messages. One email to 300 people costs you 300.

The cap scales with how many email licenses you've bought. The formula is 500 × (non-trial email licenses^0.7) + 9,500, confirmed by both Practical 365 and KnowBe4.

Run the numbers and the shape becomes obvious:

• 10 licenses: about 12,000 external recipients per day
• 25 licenses: about 14,300
• 50 licenses: about 17,200
• 100 licenses: about 22,100

Notice how flat that curve is. Quadrupling your seat count from 25 to 100 raises the ceiling by only about 55%.

The 9,500 baseline does most of the work for a small tenant. That's generous, until you try to use it as a marketing list.

What happens when you hit the limit?

Microsoft stops delivering. Messages past the threshold bounce with a non-delivery receipt carrying error code 550 5.7.233 on a paid tenant, or 550 5.7.232 on a trial.

Nothing queues and retries later. The mail is rejected.

That's the part that hurts. If your invoicing run trips the cap halfway through, the second half of your customers simply don't get invoiced, and the only signal is a pile of NDRs in one mailbox. Nobody notices until someone asks why they weren't billed.

What about the per-mailbox limit that was coming?

It's dead. Microsoft spent two years threatening a Mailbox External Recipient Rate Limit of 2,000 external recipients per mailbox per day, pushed it from January 2025 to April 2026, then cancelled it outright on January 6, 2026.

So a single mailbox can still burn the entire tenant allowance by itself. The per-mailbox guardrail everyone was told to plan for never shipped. The tenant ceiling is the only ceiling.

The separate recipient rate limit of 10,000 recipients per mailbox per day still applies, and it counts internal and external recipients together.

Who actually runs into this?

Four patterns account for nearly all of it.

Newsletters sent from Outlook. A 3,000-contact list mailed twice a week is 6,000 recipients, and that's before normal business email. On a 10-seat tenant you're at half the ceiling before anyone sends a quote.

Billing and statement runs. Accounting software authenticated against your tenant with SMTP or Graph counts against the same pool.

Appointment and reminder automation. Scheduling tools that relay through Microsoft 365 quietly add up, especially in practices sending confirmations, reminders, and follow-ups for the same appointment.

A compromised mailbox. An attacker who gets into one account and blasts phishing to a harvested list will hit your ceiling in minutes. If you're watching the Tenant Outbound External Recipients report in the Exchange admin center, that spike is one of the fastest breach signals you'll get.

What should you do about it?

Move bulk mail off Exchange Online. Marketing lists, newsletters, and anything going to more than a few hundred people at once belong on a dedicated sending platform with its own reputation, its own IPs, and unsubscribe handling built in. Exchange Online is built for person-to-person mail and Microsoft has been steadily making that clearer.

Then do three things this week:

1. Open the Exchange admin center, go to Reports, Mail flow, and find the Tenant Outbound External Recipients report. It shows your actual limit and your daily usage against it. Look at the trend, not just today.
2. Inventory every app and device authenticating to your tenant to send mail. Copiers, CRMs, accounting packages, appointment tools. Most businesses find one they forgot about.
3. Set up alerting on outbound volume so a spike reaches a human before it reaches your ceiling.

If you're separating bulk mail from transactional mail, do it with a subdomain and its own authentication records. Our guide to SPF, DKIM, and DMARC covers how to split those without breaking delivery for your main domain.

And watch the other direction too. Direct Send abuse lets attackers push mail into your tenant without credentials, which is the mirror image of this problem.

Frequently asked questions

Does the limit count messages or recipients?

Recipients. One message to 500 external addresses uses 500 of your allowance, which is why distribution lists and BCC blasts eat the ceiling so fast. Internal recipients don't count toward TERRL, though they do count toward the separate per-mailbox recipient rate limit of 10,000 per day.

Can I request a higher limit from Microsoft?

Not as a standard change. The cap is calculated from your license count, and the intended answer to needing more is to use a bulk email service rather than Exchange Online. Buying seats purely to raise the ceiling is poor economics given how flat the formula's curve is.

How do I know if we're close?

The Tenant Outbound External Recipients report in the Exchange admin center, under Reports then Mail flow, shows your tenant's limit and daily external recipient count. Check it monthly. If you're regularly above half your ceiling, you're one mailing away from bounced customer email.

Do shared mailboxes and distribution groups have their own allowance?

No. Everything sending through your tenant draws from the same tenant-wide pool. A shared mailbox, a group, a service account, and a user mailbox all count against the same daily number.

What does a 550 5.7.233 bounce mean?

Your tenant exceeded its external recipient limit for the current 24-hour window. The message was rejected, not queued. Sending resumes as the sliding window clears older recipients, but the rejected mail is gone unless you resend it.

If you're not sure what your tenant is sending, or you've seen NDRs you can't explain, get in touch for a complimentary review of your mail flow and Microsoft 365 configuration. We also handle this as part of ongoing Microsoft 365 management.