Hinet Computer System Logo Hinet Computer System
Microsoft 365 & Office For Microsoft 365 admins Diagnose in about 15 minutes

Nobody Can Email External Recipients and You See 550 5.7.233 in Microsoft 365: Understanding TERRL, New-Tenant Quotas and Step-by-Step Fixes

If one morning everyone in the company can't email external contacts at the same time — yet internal email still works and bounces carry 550 5.7.233 — the problem isn't Outlook or anyone's PC. It's Microsoft 365's tenant-wide external recipient limit (TERRL). Based on a real case the Hinet team handled, this guide explains what triggers it, how the quota is calculated and what to do, in order.

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
  1. What is TERRL, and why does internal email still work?
  2. Why do new tenants hit it, and how is the quota calculated?
  3. 6 steps to diagnose and fix 550 5.7.233
  4. When can we send again? The rolling 24-hour window
  5. From the Hinet field team
  6. What doesn't fix TERRL?
  7. Moving to Microsoft 365? How to avoid it
  8. When should you call an expert?
  9. 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 by LES301.1
LimitWhat it countsScopeTypical bounce code
TERRLExternal recipients, last 24 hWhole tenant (everyone combined)550 5.7.233 (trial tenants: 550 5.7.232)
Recipient rate limitAll recipients from one mailbox, last 24 hPer mailboxA message saying the sender exceeded its sending limit
Account restricted for spamAbnormal sending behaviourPer account (Restricted entities)550 5.1.8 (see the hacked-account guide below)
TERRL counts external recipients across the whole tenant Every employee sends through the same tenant. The service counts external recipients across everyone over the last 24 hours and compares it with the limit. Internal mail is delivered normally; external mail bounces with 550 5.7.233 once the total exceeds the limit. Sales team Emails customers all day Export / Accounts Replies with many CCs Automated systems Alerts / scanners Your tenant Counts external recipients over a rolling 24 hours against the TERRL limit Internal recipients Not counted · delivered External recipients Over limit = 550 5.7.233
TERRL adds up everyone's external recipients. Once the total exceeds the limit, nobody can email outside — even people who barely sent anything.

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 ageShare of normal quotaExample: Business Basic, 17 licenses
Under 31 days10%About 1,313 external recipients / 24 h
31–60 days25%About 3,283 / 24 h
Over 60 days100%About 13,133 / 24 h
Trial tenantsFixed500 / 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
Not counted: mail to your own accepted domains, automatic replies (out of office), delivery and read receipts, and Microsoft 365 system notifications such as Teams and SharePoint.

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.

  1. 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.233 and tenant external recipient rate limit, stop troubleshooting the user's PC — the problem is at the tenant level.

  2. 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.

  3. 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.

  4. 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-List

    Check Verdict, EnforcementEnabled, Threshold (the limit) and ObservedValue (the value used for enforcement).

  5. 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.

  6. 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:

EventEffect on quota
Yesterday 09:00 — 800 recipients sent800 used
Yesterday 14:00 — 513 recipients sent1,313 total — limit reached, next message bounces
Today, after 09:00Yesterday morning's 800 leave the window — sending resumes
Today 10:00 — 100 new recipientsThese stay in the window until about 10:00 tomorrow
Sending again doesn't mean the quota went up — while the tenant is under 31 days old the limit stays the same. Send as much as yesterday and you'll be blocked again.
First-hand · from the field

Real case: a 17-license organisation, freshly moved to Microsoft 365, couldn't email anyone outside

1,313External recipients / 24 h allowed for a tenant under 31 days old (Business Basic, 17 licenses)
~1.41KRolling 24-hour external recipients in the report while blocked
~570External recipients from the top 4 senders combined — normal business mail, not bulk

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 attemptWhy it doesn't help
Repair Outlook / create a new profileIt's not a client problem — Outlook on the web bounces too
Send from another account or a shared mailboxSame tenant, same shared quota
Send through Exchange Online SMTP relayStill counted against the tenant's external recipients
Raise the recipient limit or outbound spam policyA different limit; it doesn't raise TERRL
Unblock the user in Restricted entitiesThat's for accounts restricted for spam; it doesn't reset TERRL
Ask the recipient to whitelist youThe 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

Technically reviewed by the Hinet Computer System engineering team · Last updated 18 Nov 2026

Hinet IT Support

Still stuck? Let the Hinet team fix it

Send one bounce message (NDR), the number of affected users and when the problem started. Our engineers will check the quota report, find the heavy senders and liaise with Microsoft for you. We reply within 1 business day.

  • Supporting Thai businesses since 2004
  • Microsoft 365, Exchange Online and email migrations, end to end
  • Free initial assessment, no obligation

Report an IT issue

Fields marked * are required

We only use your details to follow up on this issue, per our privacy policy.

LINE Get help