550 5.7.236: daily limit for external mail from onmicrosoft.com domains
Your tenant sent to more than 100 external recipients in 24 hours from its default onmicrosoft.com domain. Microsoft throttles that domain, so further external mail from it bounces.
Your message can't be sent because your tenant has exceeded its daily limit for sending email to external recipients from your tenant's onmicrosoft.com domains
The description for 5.7.236 in Microsoft's Exchange Online NDR reference.
What 550 5.7.236 means
Every Microsoft 365 tenant gets a default domain ending in onmicrosoft.com, which Microsoft calls the MOERA domain. Microsoft says these domains are intended only for testing, and shouldn't be used for regular email. It enforces a throttling policy: outbound mail from onmicrosoft.com domains is limited to 100 external recipients per organization within a 24-hour rolling window. Once the tenant is throttled, senders get NDRs with 550 5.7.236 for any attempt to send to external recipients.
Two details matter when you count. External recipients are counted after any recipient list expansion, so a group with many external members counts each one. And the limit is per tenant, not per user, so one mailbox sending from the onmicrosoft.com address can use up the allowance for everyone. Inbound email isn't affected.
Microsoft's fix is to buy a custom domain, migrate to it, and make sure only the custom domain is used to send to external recipients. In practice that means adding and verifying your domain, setting it as the default, and changing users' primary addresses, including shared mailboxes and apps that still send as the onmicrosoft.com address. Two related codes cover a different limit: 5.7.232 (trial tenants) and 5.7.233 mean the tenant exceeded its overall daily external recipient rate limit. Microsoft's own figures for trial tenants disagree at the time of writing (November 2026): Microsoft Learn says trial tenants are capped at 5,000 external recipients a day, while the Exchange Team's tenant limits post, updated in August 2026, says 500. Plan around the lower figure.
Likely causes
- Users, shared mailboxes or apps still send with an onmicrosoft.com address as the From or primary address.
- A new tenant hasn't added and verified its own domain yet.
- A message to a large group expanded to many external recipients.
How to fix it
If you sent the message
- Add and verify your own domain in Microsoft 365 and set it as the default domain.
- Change the primary SMTP address of mailboxes, shared mailboxes and app accounts to the custom domain.
- Wait for the 24-hour rolling window to fall below the limit for already-throttled mail.
- Set up SPF, DKIM and DMARC for the custom domain before you move sending to it.
If you're the recipient or their admin
- No action needed: the throttle applies to the sender's Microsoft 365 tenant.
Frequently asked questions
How many external recipients can an onmicrosoft.com domain send to?
Microsoft limits outbound mail from onmicrosoft.com domains to 100 external recipients per organization in a 24-hour rolling window, counted after group expansion. Above that, external mail from those domains bounces with 550 5.7.236.
Does the 5.7.236 limit apply to my custom domain?
No. It applies to mail sent from the tenant's onmicrosoft.com domains. Microsoft's fix is to send only from a custom domain. Separate tenant-wide limits for external recipients still exist and use codes 5.7.232 and 5.7.233.
Sources
- Exchange Online limits: sending limits (Microsoft Learn)
- Email nondelivery reports (NDRs) and SMTP errors in Exchange Online (Microsoft Learn)
Provider messages are quoted as the provider publishes them. Servers can change their wording, so the bounce you received may differ slightly.
Related codes
- 550 5.7.750 550 5.7.750: client blocked from sending from unregistered domain
- 550 5.7.708 550 5.7.708: access denied, traffic not accepted from this IP
- 550 5.1.8 550 5.1.8: access denied, bad outbound sender
- 550 5.7.703 550 5.7.703: messages blocked by your organization using Tenant Allow Block List
- 550 5.7.367 550 5.7.367: remote server returned not permitted to relay
- 550 5.7.64 550 5.7.64 TenantAttribution; Relay Access Denied
- 550 5.7.12 5.7.12: sender was not authenticated by organization
Related guides
How do you set up DMARC for your onmicrosoft.com domain?
Why your onmicrosoft.com (MOERA) domain needs its own DMARC record, how to add it in the Microsoft 365 admin center, how DKIM works for it, and how to check it.
8 min read Running email day to dayWhat are the email sending limits in Microsoft 365 and Google Workspace?
Microsoft 365 and Google Workspace email sending limits per user and tenant, the bounce codes you get when you exceed them, and how to send bulk email instead.
11 min read Setup guidesHow do you set up email on a new business domain?
Setting up email on a new business domain? Follow this checklist: MX, SPF, DKIM, DMARC from p=none to enforcement, optional MTA-STS and BIMI, PTR and warm-up.
10 min read SPF, DKIM & DMARCHow to set up DKIM in Microsoft 365 and Google Workspace
Step-by-step DKIM setup for Microsoft 365 (two CNAME selectors) and Google Workspace (one TXT key): 2048-bit keys, key rotation and how to verify it works.
9 min read