Microsoft Online Email Routing Address (MOERA) domains, like contoso.onmicrosoft.com, are designed to let organizations get started quickly and test a new tenant in Microsoft 365. They don’t reflect a brand’s identity and shouldn’t be used for regular email traffic. On top of that, spammers often exploit new onmicrosoft tenants to send bursts of spam, degrading the reputation of the shared domains.
To protect brand trust and improve email deliverability, Microsoft is now introducing new limits on the use of onmicrosoft.com domains for sending emails. Let’s dive into these outbound email limits in Microsoft 365, how they work, and the actions admins need to take to prepare for this update.
New Throttling Enforcement for Sending Emails from Onmicrosoft Domains
Until now, Microsoft has not imposed limits on the use of MOERA domains for email delivery, even though they are not suitable for regular messaging and are mainly intended for testing mail flow. However, as misuse of these domains has increased, Microsoft is now setting throttling limits for sending emails to external recipients.
Here’s what you need to know about the new throttling limits and how they apply:
- External emails sent from MOERA domains are now limited to 100 recipients per organization per 24-hour rolling window.
- No limit for internal and inbound email traffic, so messages within your organization or received from external MOERA domain senders are unaffected by the throttling.
- If a sender exceeds the limit, they will receive a Non-Delivery Report (NDR) with error code 550 5.7.236.
- When sending to a group, all external recipients in the group are counted individually. For example, if you send an email to a group with 25 external members, it counts as 25 external recipients.
- Journaling Reports in Exchange Online use a fixed Microsoft system address that admins can’t change. So, they won’t be affected by the new throttling limits.
- In hybrid setups, MOERA addresses (like mail.onmicrosoft.com) might still appear in scenarios like out-of-office replies. These cases won’t be throttled either, as long as the domain isn’t used for sending original emails.
Rollout Timeline for Outgoing Email Throttling in Microsoft 365
The general availability of the new throttling begins mid-October 2025 and will be completed by early June 2026 worldwide. The timing will vary for organizations based on the number of licensed mailboxes in Exchange Online. This change will be on by default in all Microsoft 365 organizations.
For a detailed breakdown, refer to the table below.
Number of Exchange Online seats | Onmicrosoft Outgoing Email Throttling Starts |
Trial | October 15, 2025 |
<3 | December 1, 2025 |
3-10 | January 7, 2026 |
11-50 | February 2, 2026 |
51-200 | March 2, 2026 |
201-2,000 | April 1, 2026 |
2,001-10,000 | May 4, 2026 |
10,001+ | June 1, 2026 |
Microsoft will announce the rollout for each stage one month in advance via Message Center to all customers meeting the licensed mailbox count criteria.
Prepare Your Organization for Onmicrosoft Domain Usage Limits for Sending Emails
If your organization uses MOERA domains to send emails, follow these steps to prevent potential issues:
- Purchase and configure a custom domain to ensure it represents your brand identity.
- Use Message Trace in Exchange admin center to identify all mailboxes sending emails externally from MOERA domains. Enter the onmicrosoft.com domain (e.g., @contoso.onmicrosoft.com) in the Senders field. This will capture both internal and external messages. However, you can filter out internal emails by specifying an external domain in the Recipient field.
- Configure your custom domain as the default domain in the Microsoft 365 admin center. This prevents scenarios where the Sender Rewriting Scheme (SRS) uses the MOERA domain as a fallback if it remains the default.
- Add aliases to each mailbox with the new custom domain. Also, set the new alias as the primary SMTP address for outgoing emails.
- Check and update authentication credentials on all devices and apps that currently use MOERA-based usernames.
- Configure Bookings and other apps to use the custom domain for sending invites.
- Set up the custom domain to send notifications from Microsoft 365 products.
- For customers with Federated Domains, add a non-Federated custom domain in Microsoft 365 to act as the default domain, since Federated domains cannot serve that role.
This new throttling enforcement gives Microsoft 365 admins a smarter way to manage outbound emails and protect the organization’s brand reputation. By moving from MOERA to a custom domain, you can ensure your messages are delivered reliably and securely. Start planning your migration today to stay ahead of potential issues.
If you have any doubts, please share them in the comments. We’re happy to help! Stay tuned with us for all the latest Microsoft 365 updates!