Exchange Online TERRL Changes: What September's Sending Limits Mean

A sending plan built by multiplying mailboxes by a daily allowance can overstate what an Exchange Online tenant can send. Microsoft's September changes make that mistake more expensive for teams planning around newly created tenants.

In an August 13 update, Microsoft announced changes to its Tenant External Recipient Rate Limit, or TERRL, beginning rollout on September 14, 2026. The updated schedule sets the quota at 10% of the standard calculation for tenants younger than 31 days, 25% at 31–60 days, and the full quota after 60 days. It also lowers the trial-tenant ceiling to 500 external recipients per day, regardless of license count. Check the quota enforced on your own tenant before planning around these figures. Microsoft's announcement supplies the details.

Read the Limit at the Tenant Level

A tenant is the organization boundary under which Exchange Online mailboxes are administered. TERRL applies across that tenant. A mailbox can therefore be below its individual limit while the organization has exhausted its allowance for external recipients.

Microsoft's Exchange Online service limits distinguish mailbox limits from TERRL and describe the latter as a rolling 24-hour limit. A new calendar day does not necessarily restore the capacity used the previous afternoon.

For planning purposes, map the mailboxes to their tenant and identify the other workloads using it. Leave space for ordinary business correspondence and necessary operational messages. If the plan only accounts for one campaign, it can miss the rest of the organization's traffic.

The 10%, 25%, and 100% figures are stages of the tenant's calculated quota. They are not recommended campaign volumes or promises that mail sent below them will reach an inbox.

Check the Enforced Quota Before Launch

Ask the administrator for the tenant's current quota and enforcement status in the Exchange admin center's Tenant Outbound External Recipients report. Record when it was checked. If the reported position does not explain a rejection, investigate the rejection with the provider before resuming the workload.

Keep the actual non-delivery report. Microsoft's troubleshooting documentation identifies 550 5.7.233 as a tenant external-recipient limit rejection for non-trial tenants. That gives the operator a more specific starting point than a campaign dashboard saying “failed.” Microsoft's sending-limit troubleshooting guide explains how the limits differ.

Also confirm the environment. Microsoft's updated announcement says TERRL rollout is postponed for GCC, GCCH, DoD, and 21Vianet. Do not apply a commercial-tenant timeline to every Microsoft customer.

Revisit the Launch Plan

The practical question is how much usable capacity the proposed setup has during the actual launch window. Ask for tenant age, applicable licenses, enforced quota, expected background traffic, and the person responsible for reducing load when conditions change.

A trial can establish whether a connection or workflow behaves as expected. It does not establish the production capacity of a different tenant with different limits. Similarly, buying more mailboxes should not be treated as evidence that every constraint increases by the same amount.

If the revised plan leaves too little room, change the schedule or evaluate a service designed for that workload. Microsoft recommends Azure Communication Services email for bulk or high-volume external emailing beyond Exchange Online's limits. Creating fresh tenants to work around a restriction is not a sound capacity plan.

Verify Which Microsoft Service You Are Buying

These changes concern Exchange Online. A product described as Microsoft- or Azure-based does not automatically have the same service, licensing model, or sending limits.

That is why our Mailrun infrastructure comparison asks buyers to examine the operating model behind the inbox price. Ask us the same questions: what service carries the mail, which limits govern it, and who owns the response when sending is restricted? Get those answers before attaching a launch target to a mailbox count.