Blog Post

Exchange Team Blog
9 MIN READ

Introducing Exchange Online Tenant Outbound Email Limits

The_Exchange_Team's avatar
The_Exchange_Team
Platinum Contributor
Feb 24, 2025

Update 7/14/2025: Updated the FAQ.

As with all cloud services, Exchange Online imposes service limits to prevent misuse of Exchange Online resources and ensure availability for all users. For example, aside from the High-volume Email offering, Exchange Online doesn’t support bulk or high-volume email, yet until now we’ve mostly used only a per-mailbox daily send limit (known as the Recipient Rate Limit or RRL) to enforce this.

Going forward, we’re introducing new tenant-level outbound email limits (also known as the Tenant External Recipient Rate Limit or TERRL) that are calculated based on the number of email licenses a tenant has or if a tenant has only trial licenses. Enforcement for trial-only and single-seat tenants is already enabled. We’ll continue to enable enforcement for all other tenants in the Exchange Online multitenant standard environment in March, starting with tenants with a small number of licenses, then gradually including all multitenant standard tenants by end of April. Enforcement for the GCC environment will start at the end of June.

TERRL rollout schedule

For tenants in WW environment:

Phase

Enable enforcement for tenant group

Rollout start date

1

Tenants with <= 25 email licenses

April 3, 2025

2

+ additional tenants with <= 200 licenses

April 18, 2025

3

+ additional tenants with <= 500 licenses

April 28, 2025

4

+ all remaining tenants

Paused

For tenants in the GCC environment:

EAC report enabledJune 30, 2025
Enforcement enabledJuly 30, 2025

Please note that GCC customers might have inconsistent experience with trying to access the report before end of May (report is blank, report is not available at all).

We will roll out the TERRL to GCCH, DoD, and Gallatin environments in the second half of this year.

Based on service telemetry, most Exchange Online customers won’t be impacted. A new report (Tenant Outbound External Recipients) will be made available in the EAC by late-February that will show your tenant’s limit (by late May for GCC tenants). If your organization needs to send more email to external recipients than your limit allows, we recommend using Azure Communication Services email for bulk or high-volume emailing to external recipients.

More Information

The Tenant External Recipient Rate Limit (TERRL) is the maximum number of external recipients a tenant in good standing can send to per day (24-hour sliding window). External recipients are those whose email address domains are not an accepted domain in the tenant. The TERRL establishes base-line outbound sending limits for all tenants, but additional current and future restrictions can also occur due to factors like suspicious sending behavior, sending spam, fraudulent or excessively late payments, etc.

Below are the new maximum tenant external recipient rate limits:

  • Trial tenants: Limited to 5,000 total external recipients per day, regardless of license count.
  • Non-trial tenants: Daily outbound limit is based on the tenant’s email licenses (any Exchange Online or Exchange Online Protection license). More licenses increase the number of external recipients your tenant can send to per day, but at a decreasing rate per license. By late February you’ll find your tenant’s TERRL in the Tenant Outbound External Recipients report in the EAC Reports > Mail flow section. You can also use the following formula to determine your tenant’s TERRL:
500 * (Number of Non-trial Email Licenses^0.7) + 9500

Sample limits for tenants with various license counts are shown below:

Number of Non-trial Email Licenses

Tenant External
Recipient Rate Limit

1

10,000

2

10,312

10

12,006

25

14,259

100

22,059

1,000

72,446

10,000

324,979

100,000

1,590,639

If your tenant exceeds its daily outbound sending limit subsequent messages sent to external recipients will be blocked and senders will receive one of the following bounce messages (also known as Non-Delivery Receipts or NDRs):

  • Trial tenants: 550 5.7.232 - Your message can't be sent because your trial tenant has exceeded its daily limit for sending email to external recipients (tenant external recipient rate limit)
  • Non-trial tenants: 550 5.7.233 - Your message can't be sent because your tenant exceeded its daily limit for sending email to external recipients (tenant external recipient rate limit)

What is a “24-hour sliding window”?

Daily outbound email volume and quota are tracked using a 24-hour sliding window. If you exceed your limit, subsequent outbound messages will be blocked until your volume of external recipients from the last 24 hours drops below the limit. This could take minutes or up to 24 hours, depending on your email sending pattern. Here’s an example of how this works:

Example: A single-seat tenant with 10k external recipients per day limit. Tenant sends two large messages to external recipients:

  • Message 1, sent to 6K external recipients at 6:00AM on Day 1
  • Message 2, sent to 4K external recipients at 3:00PM on Day 1
Illustration of TERRL 24-hour 'sliding window'

To help admins plan and track their outbound email volume, starting in late February you’ll find a new report in the Exchange admin center: EAC > Reports > Mail flow > Tenant Outbound External Recipients Rate. This report will show the current volume of external recipients, your tenant’s daily quota, how much of the quota is used, and the number of recipients that were blocked if the limit was exceeded. The report will also show if enforcement for the limit is enabled or disabled. For example, for tenants who have more than 500 email licenses it will show “Disabled” until May 1, the day we’ll start to enable enforcement for tenants who have more than 500 licenses.

Sample report in EAC

Frequently Asked Questions

What makes a recipient an “external recipient”?
Any recipient with a domain that is not an accepted domain in your tenant is considered an external recipient and when a message is sent to them it will count against your quota (exceptions to this are noted below). This includes messages sent to recipients in other Microsoft 365 tenants.

Note: Email sent to the sub-domain won't be automatically treated as Internal. There are two conditions where we will treat email sent to subdomain as Internal:

  1. The subdomain is explicitly added as Accepted Domain.
  2. The Root accepted domain has "Accept mail for all subdomains" option enabled. Remember, this is possible only when the root accepted domain type is Internal relay.

Will journaling or Out of Office messages count against this quota?
No, journaling messages using Exchange Online journaling rules will not be counted against the quota. Several types of messages sent to external recipients from your tenant won’t get counted against your tenant’s TERRL quota, including the following:

  • Journaling messages using Exchange Online journaling rules (see Manage journaling in Exchange Online | Microsoft Learn)
  • Automatic Replies (including Out of Office)
  • DSNs (NDRs, Delivery Receipts, Read Receipts)
  • Messages sent using Azure Communication Services email and Exchange Online High-volume Email offerings
  • Email notifications from Microsoft cloud applications e.g. SharePoint, Teams, Yammer

What email licenses are used to calculate my tenant’s quota?
Licenses for, or that include, Exchange Online or Exchange Online Protection count towards the license count that is used to calculate your tenant’s quota.

Are the TERRL limitations based on the total number of email licenses (Exchange Online or EOP), or the total number of assigned licenses?
TERRL is based on the total number of email licenses.  For example, a tenant with 1000 licenses would be able to send 72,446 messages regardless of assigned seats (included non-licensed shared mailboxes).

Are messages to external recipients that are relayed through my tenant from my on-premises environment counted against the quota?
Yes. All messages sent outbound to external recipients from your tenant qualify for counting against your tenant’s quota, regardless of whether they originate from on-premises, from Exchange Online mailboxes, or from the Internet.

Are messages sent to my users’ on-premises mailboxes in an official Hybrid configuration counted against the quota?
So long as the mailboxes have email addresses that include an accepted domain in your tenant then these won’t count against your quota.

All my tenant’s email to internal Exchange Online mailboxes is sent out to a 3rd party service for processing before it comes back into Exchange Online to be delivered to those internal recipients. Will these messages count against my quota?
No. If the recipient’s domain is an accepted domain in your tenant messages to them won’t get counted against the tenant external recipient rate limit, even if they are routed out then back into Exchange Online.

If I send a message to an external recipient but it routes out to a signature service or on-premises for processing, then comes back into Exchange Online to be sent out to the external recipient, will that get counted twice?
To reduce the risk of bad actors spoofing on-premises systems to send spam, we are currently counting these messages more than once. Our telemetry shows only a relatively small number of tenants are currently exceeding their quota, so it’s highly unlikely this will be an issue for your tenant. That said, we’re investigating alternative ways to prevent this type of spoofing that won’t double-count such messages.

Are cross-tenant messages within my multitenant organization treated as external messages?
At this time, yes.

If I send 1,000 messages to the same external recipient in a day does that count as 1 external recipient or 1,000 external recipients?
It counts as 1,000. The tenant external recipient rate limit doesn’t track unique external recipients.

If I send a message to a Distribution Group (DG) in my tenant that in turn has 1,000 external recipients on it will that get counted as 1 external recipient or 1,000 external recipients?
It counts as 1,000. The counting of external recipients happens after the DG (and its nested groups) is fully expanded to individual recipients.

Will outbound messages sent using the Exchange Online High-volume email (HVE) offering get counted against the TERRL quota?
No. HVE is designed for sending high-volume email to internal recipients, not external recipients.

How can I identify the top senders in my tenant?
You can use the “Top senders and recipients” report in the Microsoft Defender portal (Microsoft Defender > Email & collaboration reports > Top senders and recipients) or use Message Trace in the EAC to aggregate a list of your top senders. We’re also considering adding a top senders list to the Tenant Outbound External Recipient Rate report later this year.

The report shows Enforcement is Disabled. What does that mean?
When Enforcement shows Disabled blocking is not happening, even if the report shows you’ve exceeded your quota, and it shows external recipients are getting blocked. The Disabled state will be shown during the initial rollout schedule for tenants for whom enforcement hasn’t yet been enabled (see the rollout schedule above). Once the feature is fully rolled out and enabled for all tenants by May, Enforcement will typically always show as Enabled and blocking will occur if the quota is exceeded.

Is there any type of notification or alert I’ll get when my outbound email volume exceeds my quota?
No, not at this time. We plan to add a system alert later this year that will notify admins when their outbound email volume exceeds 80% of the quota.

Will there be a cmdlet or Graph API to retrieve the data shown in the EAC report?
You can use the below Exchange Online PowerShell cmdlet to retrieve information about your Tenant External Recipient Rate Limit:

Get-LimitsEnforcementStatus

Sample output:

Verdict : Block
EnforcementEnabled: True
Threshold: 95980
ObservedValue: 243418

Property

Description

Verdict

Possible values: Block | None
Block: The tenant has exceeded the TERRL, and subsequent messages to external recipients will be blocked until the external recipient’s volume over the last 24 hours drops below the threshold. Tip: If Verdict is Block and EnforcementEnabled is False messages are not getting blocked but will still appear on the report as if they’ve been blocked. Always check the Enforcement status in the report or EnforcementEnabled property in the cmdlet output to determine whether external recipients are getting blocked or not.
None: The current external recipients count against the TERRL is below the threshold (quota) and messages to external recipients are currently not subject to blocking.

EnforcementEnabled

Possible values: True | False

True: Equivalent to “Enforcement is Enabled” in the report. If a tenant exceeds the TERRL the Verdict will be Block and further external messages will be blocked until the external recipient’s volume over the last 24 hours drops below the quota.

False: Equivalent to “Enforcement is Disabled” in the report. Messages will not be blocked regardless of if the TERRL quota has been exceeded.

Threshold

Your tenant’s Tenant External Recipient Rate Limit (TERRL) quota based on the number of non-trial email licenses. The formula for calculating this is as follows:

                  500 * (number of Non-trial Email Licenses^0.7) + 9500

ObservedValue

The number of external recipients sent to by your tenant over the last 24 hours.

A Graph API is under consideration for a future update.

Recent changes to this blog post:

  • 3/31/2025: Corrected the FAQ on "cross-tenant messages within multitenant organization"
  • 3/19/2025: Clarified the status of Exchange Online journaling messages in the FAQ

Microsoft 365 Messaging Team

Updated Jul 14, 2025
Version 18.0

231 Comments

  • marconovelli's avatar
    marconovelli
    Copper Contributor

    A HUGE company with 100.000 users is allowed 15 email per day per user

    Nice! 😂

    • marcomas's avatar
      marcomas
      Icon for Microsoft rankMicrosoft

      Not correct, in that case the limit is 15 recipients not email :-)

      • RonHite67's avatar
        RonHite67
        Copper Contributor

        marcomasis that accurate?  It seems "recipient" is not the true measure, but actually external messages.  The FAQs states: If I send 1,000 messages to the same external recipient in a day does that count as 1 external recipient or 1,000 external recipients?
        It counts as 1,000. The tenant external recipient rate limit doesn’t track unique external recipients.

    • Kenneth650's avatar
      Kenneth650
      Copper Contributor

      Not that I am a fan of rate limiting, but to be clear, 15 external mails per day per user. Internal mails are not affected, or well anything to an accepted domain. 
      I believe this is a big difference, at least it is for the tenants that I manage.

    • marconovelli's avatar
      marconovelli
      Copper Contributor

      The sweet spot is in the 10-25 mailbox range, so they just need to fire 99.975 people. Call DOGE!

      • Nino_Bilic's avatar
        Nino_Bilic
        Icon for Microsoft rankMicrosoft

        Both MERRL and TERRL will exist as their own separate limits. One is on the mailbox and one on tenant level.

  • stukey's avatar
    stukey
    Iron Contributor

    KevinShaughnessyWe route all our external outbound email from EXO to our on-premises ProofPoint servers; no email ever leaves EXO and is delivered direct to external recipients. Would this new TERRL limit still apply in our scenario? Also, introducing these new limits with only 1 months’ notice is really not acceptable. The impact of this change and the possible administrative overhead is enormous!

    • KevinShaughnessy's avatar
      KevinShaughnessy
      Icon for Microsoft rankMicrosoft

      stukey as noted above if the recipient's email address domain is NOT an accepted domain in the tenant then it counts as an external recipient even if it routes to your on-prem over a connector. 

      The number of legitimate tenants that will be impacted by this is very small. As noted in the last FAQ above you can run the cmdlet Get-LimitsEnforcementStatus to find your quota and current volume (Threshold and ObservedValue). 

      • woods_sj's avatar
        woods_sj
        Copper Contributor

        What span of time does the 'ObservedValue' represent?

  • BoBeB's avatar
    BoBeB
    Brass Contributor

    How can MS enforce a limits which is only a month away, however yet again not having the tools available to identify whether this will impact its customers?

    The report is still not available? 

    I`m curious to learn how using ACS prevents misuse of Exchange Online resources and ensure availability for all users and differently that ExO - the cynic in me might wonder whether this is just a profiteering scheme by MS as ACS is chargeable (although wasn't in GA last I checked and the costing not defined)

    • BoBeB As noted in the last FAQ above you can run the EXO PowerShell cmdlet Get-LimitsEnforcementStatus to find your quota and current volume (Threshold and ObservedValue). We expect the report to go live later this week. 

      ACS emails are processed differently than mail generated by/thru EXO. 

      • IulianG28's avatar
        IulianG28
        Copper Contributor

        Get-LimitsEnforcementStatus
        Write-ErrorMessage : ||Parameter set cannot be resolved using the specified named parameters. Default mandatory paramet
        ers not satisfied. TenantId
        At C:\Users...\AppData\Local\Temp\tmpEXO_45czvo4z.igl\tmpEXO_45czvo4z.igl.psm1:1189 char:13
        +             Write-ErrorMessage $ErrorObject
        +             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
            + CategoryInfo          : NotSpecified: (:) [Get-LimitsEnforcementStatus], Exception
            + FullyQualifiedErrorId : [Server=AM9PR08MB6950,RequestId=bbb15516-4310-ba9b-9f27-be35c647a8ec,TimeStamp=Wed, 26 F
           eb 2025 04:56:56 GMT],Write-ErrorMessage

         

        Powershell module is 3.7.1

  • Suberg's avatar
    Suberg
    Copper Contributor

    Is this limit enforced even if centralized mailflow is enabled and thus emails are not send to external using EOP Servers, but through on premise mail gateways instead?

    • KevinShaughnessy's avatar
      KevinShaughnessy
      Icon for Microsoft rankMicrosoft

      Suberg as noted in blog post and FAQ, if it leaves EXO no matter how (e.g. via connector to an on-prem gateway) and the recipient address doesn't have an accepted domain then it gets counted against the TERRL. 

  • BoBeB's avatar
    BoBeB
    Brass Contributor

    is Azure Communication Services in GA, I`m assuming it will be chargeable - and is the pricing structure confirmed yet?

    • BoBeB  Yes ACS email is in GA and has been for some time. Are you thinking of High-volume Email service (HVE)? HVE is still in preview, but HVE only supports up to 2K external recipients per day.

  • Works for me and my customers. Just checked the #Messages in some customer tenants using the "outbound TLS Report" at  https://admin.cloud.microsoft/exchange#/reports/outboundconnectordetails. It's is not 100% accurate for that but if a german production 10.000 Seats Tenant may send 324k Mails in 24h and is currently using 40k/day peak, then we are far away from these limit. I think thousands others are safe, too. 
    Bit i have told them every time, that Exchange online is for "humans" not for Listservers, massmailers, ERP-Relays etc. they should have a look at other options. (Azure Communication, Sendgrid, Mailchimp, Mailgun and many others. and implement SPF, DKIM ,DMARC for besser deliverey rates at all

    • KevinShaughnessy's avatar
      KevinShaughnessy
      Icon for Microsoft rankMicrosoft

      Frank Carius Thanks for sharing that. Indeed there are multiple ways to assess current volume without the dedicated report available quite yet. The cmdlet noted in the FAQ above is probably the most accurate for the current 24-hour volume and threshold: Get-LimitsEnforcementStatus. Check the Threshold and ObservedValue properties. 

      Only a super small % of legitimate tenants will be impacted by this, and those that are, are egregiously blasting out bulk mail (or potentially are compromised). As more admins determine their threshold versus actual volume (via the cmdlet or after the report goes live this week) the vast majority will see they're also well under quota and won't be impacted by this. 

       

       

  • brogyi's avatar
    brogyi
    Brass Contributor

    The idea I love it, go secure, less spam yeey. The timing and implementation I hate. One of the things I loved about Exchange team that if they do change something they give us time to prepare. In the worst case I got less than a week and I consider myself lucky, because in the morning, I was scrolling social media, and I following Tony Redmond who was writing about this article. I only read Microsoft news once monthly mostly through Nick Ross, because who's got to time, to always catch up and follow all the updates Microsoft is giving out. The normal time I get this information would be that our clients are blocked and can’t send mails.

     Out company is an MSP, and also providing other IT related services to customers. We have multiple transport logistics companies, whose job is to organize transporting goods. The company is relatively small (<30 people), but they need to send large volume emails to arrange and do work. Now I was rushing to check the report, yet the option name was not the same (Tenant Outbound External Recipients count, yeey go renaming team...) but the main problem, is the report is just not loading. It is just an empty white page. I will check the page later, but all things considered, (with do respect) this is not what we used from Exchange Team.

    • KevinShaughnessy's avatar
      KevinShaughnessy
      Icon for Microsoft rankMicrosoft

      brogyi I hear you and I'll take the blame for the short notice. Our protocol is typically months in advance to give folks time to prepare, etc. and I've always aligned with that in previous releases. Alas, a confluence of factors conspired against that this time. Apologies.

      You don't have to wait for the report to be fully deployed/enabled later this week. Use the PowerShell cmdlet referenced in the FAQ: Get-LimitsEnforcementStatus. Check Threshold (your quota) and ObservedValue (your current volume). 

      • KarstenV59's avatar
        KarstenV59
        Brass Contributor

        Well this give you a moments nr. but that changes all the time, and it depenmds a lot on what kind off business you run in your tenant, and by the way this by far not the first time MS is introducing "new features" without giving the admins the tools to stay in control or even manage it. 

  • zolnaizsolt's avatar
    zolnaizsolt
    Copper Contributor

    What about educational subscriptions? For example, will the Student Use Benefits subscription provide extra limits? Or the free Office 365 A1?

     

    • KevinShaughnessy's avatar
      KevinShaughnessy
      Icon for Microsoft rankMicrosoft

      zolnaizsolt At this time EDU subscriptions are treated no differently than regular commercial subscriptions. EDU licenses are counted as purchased licenses. 

  • jt8585's avatar
    jt8585
    Brass Contributor

    Regarding the formula, Tenant External Recipient Rate Limit  (Purchased Email Licenses^0.7), is that power of 0.7 or multiply by 0.7 ?  Practical 365 website published it as  License * 0.7

    • KevinShaughnessy's avatar
      KevinShaughnessy
      Icon for Microsoft rankMicrosoft

      It's to the power of 0.7. So it's "500 times (Purchased Email Licenses to the power of 0.7) plus 9500".

      • jt8585's avatar
        jt8585
        Brass Contributor

        Looks like instead of acknowledge my comments, the author corrected his article and deleted all comments.

        https://practical365.com/tenant-wide-external-recipient-rate-limit/#comment-307838