Quick answer
550 5.7.233 means your whole tenant has reached its limit of external recipients in the last 24 hours (the Tenant External Recipient Rate Limit, or TERRL). The limit is based on purchased email licenses, and tenants younger than 31 days get only 10% of the normal quota (25% for days 31–60). Admins can't raise or reset it. Check the Tenant Outbound External Recipients Rate report in the Exchange admin center, find the heavy senders, stop resending, and wait for the rolling 24-hour count to drop below the limit — sending resumes automatically. Then test and resend only the bounced messages.
Contents
- What is TERRL, and why does internal email still work?
- Why do new tenants hit it, and how is the quota calculated?
- 6 steps to diagnose and fix 550 5.7.233
- When can we send again? The rolling 24-hour window
- From the Hinet field team
- What doesn't fix TERRL?
- Moving to Microsoft 365? How to avoid it
- When should you call an expert?
- FAQ: 550 5.7.233 and TERRL
What is TERRL, and why does internal email still work?
TERRL (Tenant External Recipient Rate Limit) caps how many external recipients your whole company can email in a rolling 24 hours. Once it's exceeded, every user's external mail bounces with 550 5.7.233, while internal mail isn't counted and keeps flowing.
Microsoft added this limit to stop Exchange Online being used for bulk email and to contain compromised accounts sending spam. The key difference from older limits: it's counted across the whole tenant, not per person. A user who barely sends anything is blocked too if colleagues have used up the quota.
The symptoms are distinctive:
- Everyone fails to reach external recipients at once, not just one user
- Internal email still works, and Message trace shows internal recipients as Delivered
- Bounces contain
550 5.7.233 … tenant external recipient rate limit, sometimes followed byLES301.1
| Limit | What it counts | Scope | Typical bounce code |
|---|---|---|---|
| TERRL | External recipients, last 24 h | Whole tenant (everyone combined) | 550 5.7.233 (trial tenants: 550 5.7.232) |
| Recipient rate limit | All recipients from one mailbox, last 24 h | Per mailbox | A message saying the sender exceeded its sending limit |
| Account restricted for spam | Abnormal sending behaviour | Per account (Restricted entities) | 550 5.1.8 (see the hacked-account guide below) |
Why do new tenants hit it, and how is the quota calculated?
Tenants younger than 31 days get only 10% of the normal quota, so a company that has just moved its email to Microsoft 365 can hit the limit in a single ordinary working day.
Per Microsoft's announcement, the normal limit is based on purchased (non-trial) email licenses using 500 × (licenses ^ 0.7) + 9,500. Between September and November 2026, Microsoft began scaling quotas by tenant age:
| Tenant age | Share of normal quota | Example: Business Basic, 17 licenses |
|---|---|---|
| Under 31 days | 10% | About 1,313 external recipients / 24 h |
| 31–60 days | 25% | About 3,283 / 24 h |
| Over 60 days | 100% | About 13,133 / 24 h |
| Trial tenants | Fixed | 500 / 24 h regardless of license count |
The 17-license figure comes from the real case below, and it matches the limit shown in the admin report exactly. 1,313 sounds like a lot, but it runs out faster than you'd think, because of how recipients are counted:
- One email to 10 customers (including CC/BCC) = 10 units
- Five replies to the same person = 5 units (recipients aren't de-duplicated)
- One email to a distribution group with 50 external members = 50 units
- Email to another company on Microsoft 365 still counts as external, because its domain isn't in your tenant
6 steps to diagnose and fix 550 5.7.233
Confirm it really is TERRL, find the heavy senders, cut sending and wait for the rolling count to drop below the limit. Don't touch Outlook or DNS.
-
Find 550 5.7.233 in the bounce message
Ask the user for the full non-delivery report and look at Diagnostic information for administrators. If you see
550 5.7.233andtenant external recipient rate limit, stop troubleshooting the user's PC — the problem is at the tenant level. -
Open the Tenant Outbound External Recipients Rate report
In the Exchange admin center, go to Reports → Mail flow → Tenant Outbound External Recipients Rate. Check the 24-hour limit, the rolling recipient line, the Enforcement status and the Top external senders table. Take timestamped screenshots as evidence.
-
Compare internal and external results in Message trace
Go to Mail flow → Message trace and search the affected sender's mail. Internal recipients showing Delivered while external recipients show Failed matches TERRL. Note that Message trace times are in UTC.
-
Find the heavy senders and rule out compromised accounts
Look at who sends the most external mail and work out whether it's normal user work, automated systems (ERP, alerts, scanners), forwarding rules or distribution groups. If an account is mailing large numbers of strangers, follow the hacked-account steps first — but don't reset every password just because TERRL is full.
If you already have an Exchange Online PowerShell session, this read-only command shows the status (it doesn't unblock anything):
Get-LimitsEnforcementStatus | Format-ListCheck
Verdict,EnforcementEnabled,Threshold(the limit) andObservedValue(the value used for enforcement). -
Cut sending and wait for the rolling count to drop
Tell everyone it's a company-wide quota and not to keep resending — every external send is counted again. Trim unnecessary CC/BCC and pause non-urgent bulk sending. Check with system owners before pausing automated mail, since it may include invoices or critical alerts. Then wait: sending resumes automatically once the count is below the limit.
-
Send a test, then resend only bounced messages
When the report shows usage below the limit, send one test to an external mailbox you control, confirm Delivered in Message trace and have the recipient confirm. Then ask users to resend only the bounced messages, after checking who already received them.
When can we send again? The rolling 24-hour window
There's no daily reset. The system counts external recipients over the previous 24 hours at every moment; once older sends drop out of the window and the total falls below the limit, sending resumes automatically.
So the wait depends on when most of the volume was sent, not on when the first bounce arrived. A hypothetical example for a tenant with a 1,313 limit:
| Event | Effect on quota |
|---|---|
| Yesterday 09:00 — 800 recipients sent | 800 used |
| Yesterday 14:00 — 513 recipients sent | 1,313 total — limit reached, next message bounces |
| Today, after 09:00 | Yesterday morning's 800 leave the window — sending resumes |
| Today 10:00 — 100 new recipients | These stay in the window until about 10:00 tomorrow |
Real case: a 17-license organisation, freshly moved to Microsoft 365, couldn't email anyone outside
An organisation of about 17 users had moved its email to Microsoft 365 less than a month earlier. One morning they reported that no one could email external partners — partner domains and Gmail alike. We started with the bounce, found 550 5.7.233 with LES301.1, and didn't touch Outlook at all. The Tenant Outbound External Recipients Rate report showed a 1,313 limit, usage above it and enforcement on, while Message trace confirmed internal mail was Delivered and external mail Failed.
Running the formula for 17 Business Basic licenses on a tenant under 31 days old gave exactly the limit shown in the admin report. The top senders were export-operations replies with several people in CC — not marketing mail, and the messages we reviewed showed no sign of a compromised account. With only 10% of the normal quota, ordinary company-wide work was enough to hit the ceiling. We explained it was a company-wide quota, asked users to stop resending, and opened a Microsoft Support case in parallel — without promising the customer an exception.
Our take: a Microsoft 365 email migration now needs a TERRL plan from day one, especially for companies that email many external partners. Estimate real external recipient volume (including CC/BCC) before cutover, warn users about the first 60 days and watch the report daily. That beats finding out when customer emails start bouncing.
What doesn't fix TERRL?
Anything done on the user's PC or to per-mailbox policies won't help: the limit is enforced at Microsoft's service level and admins can't raise or reset it.
| Common attempt | Why it doesn't help |
|---|---|
| Repair Outlook / create a new profile | It's not a client problem — Outlook on the web bounces too |
| Send from another account or a shared mailbox | Same tenant, same shared quota |
| Send through Exchange Online SMTP relay | Still counted against the tenant's external recipients |
| Raise the recipient limit or outbound spam policy | A different limit; it doesn't raise TERRL |
| Unblock the user in Restricted entities | That's for accounts restricted for spam; it doesn't reset TERRL |
| Ask the recipient to whitelist you | The mail never left Microsoft — the recipient isn't blocking it |
Moving to Microsoft 365? How to avoid it
Estimate real external recipient volume before migrating, plan for a 10% quota in the first month, watch the report daily for the first 60 days, and keep bulk sending out of user mailboxes.
- Estimate before cutover: review outbound volume from the old system, counted as recipients (including CC/BCC), not messages, and compare it with 10% and 25% of your calculated limit.
- Warn users in advance: for the first 60 days, cut unnecessary CCs and don't send customer-wide announcements from personal mailboxes.
- Watch daily: check the Tenant Outbound External Recipients Rate report each morning. If usage passes roughly 70–80% of the limit, start looking for the source (this threshold is Hinet's own practice).
- Separate bulk sending: automated or campaign email belongs on a dedicated sending service such as Azure Communication Services or an email marketing platform, which doesn't count toward TERRL.
- Agree a fallback channel: decide with management how key partners will be contacted if email is blocked.
When should you call an expert?
If you don't have admin access, usage is below the limit but mail still bounces, you suspect a compromised account, or you're about to migrate to Microsoft 365, get an experienced administrator involved.
If usage is already below the limit and the same code persists, or 24 hours have passed and you still can't send, Microsoft needs the evidence: the bounce, Message trace, report values, and times in UTC and local time. Hinet manages Microsoft 365 Business and IT Support Outsource for SMEs, from migration planning and quota checks to working with Microsoft Support. Send us a bounce message using the form below.
FAQ: 550 5.7.233 and TERRL
What does 550 5.7.233 mean?
It's an Exchange Online bounce code meaning your tenant has reached its Tenant External Recipient Rate Limit (TERRL) for external recipients in the last 24 hours. Tenants on trial licenses see 550 5.7.232 instead.
Why can we email colleagues but not customers?
TERRL only counts recipients whose domain isn't an accepted domain in your tenant, so internal mail isn't counted or blocked. If internal mail works but every user's external mail bounces at the same time, suspect TERRL first.
Can an admin raise or reset the TERRL quota?
No. The limit is calculated automatically from purchased email licenses and tenant age. Admins can only view it in the Exchange admin center report or with Get-LimitsEnforcementStatus. Exceptions require Microsoft Support and aren't guaranteed.
How long until we can send again?
There's no fixed time. The system counts external recipients over a sliding 24-hour window; once older sends fall out of the window and the total drops below the limit, sending resumes automatically. That can be a few hours or close to 24, depending on when most of the volume was sent.
How is one email to 10 customers counted?
As 10 external recipients. Sending to the same person five times counts as five, because TERRL doesn't count unique recipients. External members of a distribution group are counted individually.
Will buying more licenses help?
It raises the base, but not by much: the formula uses license count to the power of 0.7, and new tenants are still multiplied by 10% or 25%. Do the math before buying licenses as an emergency fix.
Can an established tenant hit TERRL?
Yes, if it exceeds the full quota — usually because of automated or bulk sending, or a compromised account sending spam. Move high-volume sending to a dedicated email service.
References
- Microsoft Exchange Team — Introducing Exchange Online Tenant Outbound Email Limits (TERRL)
- Microsoft 365 Message Center MC1454397 — TERRL quotas for new, trial and EDU tenants
- Microsoft Learn — Outbound sending limits in Exchange Online
- Practical365 — Get-LimitsEnforcementStatus and tenant-wide external recipient limits
- Microsoft Learn — Azure Communication Services (email for high-volume sending)
Related guides
Technically reviewed by the Hinet Computer System engineering team · Last updated 18 Nov 2026