SenderOwnerAnalyze two CSVs
Menu

Exchange Online field guide

What the Exchange Online TERRL means for your tenant

The Tenant External Recipient Rate Limit caps how many external message-recipient pairs an Exchange Online tenant can send during a rolling 24-hour window. Microsoft’s live enforcement status is the source of truth; an estimate or CSV is an attribution aid, not the counter itself.

Turn two exports into an action plan

Published rule snapshot

Checked September 13, 2026. Microsoft announced that revised quotas for new, trial, and education tenants begin rolling out on September 14, 2026. Rollout is not a guarantee that every tenant changes on that date: verify the live EAC report or Get-LimitsEnforcementStatus before planning a change.

  • External recipients are addresses whose domains are not accepted domains in the tenant.
  • The announced trial-tenant quota is 500 external recipients per rolling 24-hour window, regardless of license count.
  • New tenants receive 10% of the standard calculated quota when less than 31 days old, 25% at 31–60 days, and 100% after 60 days.
  • The standard formula for tenants without free EDU licenses is 500 × (non-trial email licenses^0.7) + 9,500. For tenants with free EDU licenses, the announced formula is 500 × (purchased email licenses^0.7 + free EDU licenses^0.3) + 9,500.
  • Microsoft lists TERRL rollout for GCC, GCCH, DoD, and 21Vianet as postponed; do not apply a worldwide rollout date to those environments.
  • If enforcement is enabled and the current limit is exceeded, external messages can be blocked until rolling usage falls below the limit. Microsoft lists 550 5.7.232 for trial tenants and 550 5.7.233 for non-trial tenants.

A report is the start, not the remediation plan

The EAC report and Microsoft support script can expose enforcement values, estimated usage, and contributing senders or domains. They do not know the business owner, whether a source should stay or move, who will execute the change, or what evidence proves a cutover worked.

  1. Confirm the live enforcement value and threshold.
  2. Export or estimate the contributing sender data.
  3. Identify the business and technical owner for each material source.
  4. Evaluate the route using current provider requirements.
  5. Define a test, rollback condition, and post-change verification.

Common questions

Does each unique recipient count only once?

No. Microsoft describes message-recipient pairs during the rolling window, not a lifetime list of unique addresses.

Is an estimate the live counter?

No. The support script describes its result as an estimate. Use live enforcement status for the current value, threshold, verdict, and state.

Will moving a sender guarantee delivery?

No. Eligibility, authentication, provider limits, content, reputation, and implementation all matter. This guide does not guarantee delivery or migration success.

Continue with the specific task

Sources