Keep your first 100 outreach emails from dying in a new Microsoft 365 tenant

A new Microsoft 365 tenant can block your first 100 before your list does

You are about to email your first 100 prospects by hand. The Microsoft 365 tenant behind that outreach may be the thing that blocks them. Microsoft starts rolling out new Exchange Online outbound sending restrictions on September 14, 2026.

A fresh tenant can look like a clean sender. In practice, it is a sender with little history and a lower ceiling. Manual outreach is slow enough to notice a bounce, but it is also the moment when a weak sending path hurts most. A bigger stack will not fix this. The tenant has to deliver a small list.

Your copy, list, and follow-up can wait; the sending tenant is the first check. A tenant that is too young, on trial, or already using its external recipient headroom can stop the first 100 before they reach inboxes.

Trial and young tenants have the tightest sending ceilings

TERRL, the tenant-wide external recipient limit, applies to the whole tenant, not to one mailbox, and it adds up external recipients across every message in a 24-hour rolling window. Another mailbox sending at the same time can eat the headroom you planned for your manual list. For tenants using free education licenses, including Microsoft 365 A1, the TERRL math weights purchased licenses at the 0.7 power and free EDU licenses at the 0.3 power.

Once that limit is hit, external sending is blocked, and the affected message gets a 550 5.7.233 non-delivery response. For a first 100, that can stop the send.

On a trial, the external recipient ceiling is the number that decides whether your list survives the initial send. A young tenant may have less headroom than the license count suggests. The audit below turns those risks into five checks you can finish before the first send.

Run this 10-minute audit before the first send

Do it in the tenant admin view, not in your inbox. You need the tenant age, license type, and sending headroom, not just your mailbox. Ask the person who created the tenant when you cannot see those fields. Take ten minutes, not an hour, because the first 100 are too small to waste on a broken send.

• Check the tenant age; when it is under 60 days old, assume the outbound quota is temporarily reduced regardless of license count, and plan a slower send.
• Check whether the tenant is a trial; when it is, treat the tenant-wide external recipient limit as 500 in a rolling 24-hour period, down from 5,000, and expect no raise from more trial licenses.
• Count external recipients across every mailbox, not just your own.
• Have an aged domain ready as a fallback, since a freshly migrated tenant may sit at one-tenth of its usual outbound quota for its first month after migration.
• Send one test message to an external address before that date, and confirm it arrives without a bounce.

A failed item means stop the send and change the sending path, not try a smaller batch.

If the test send fails, move the small send to an aged domain

An aged-domain fallback is a separate sending domain that has existed long enough to have a history. It can carry a small send while the new tenant ages. Build one before the list grows when you lack it.

The fallback only needs to be a separate path that can carry the first 100 without putting the new tenant under pressure. When you switch, keep the list, the notes, and the manual follow-up plan intact. It is a manual sending path, not a growth engine.

A bounced test message means pause, move the send to the fallback, and let the new tenant age. The first 100 are small enough that a short delay is cheaper than a damaged sender reputation on a new domain. A delivered test send means start the list. A failed test send means switch to the fallback and send tomorrow.