How to Set Up Microsoft 365 Domains and Inboxes for Cold Email in 2026

Start With the Tenant

A Microsoft 365 tenant is the organizational container everything else lives inside. Your domains, your mailboxes, your Exchange settings — all of it lives within a tenant. Most operators treat the tenant as an afterthought. It should be your first decision.

Rule of thumb: one tenant per client. If you're an agency managing outreach for multiple clients, each client gets their own isolated tenant.

If you choose to run multiple clients inside a single tenant, enforcement becomes non-negotiable.

Domain reputation is still isolated at the domain level. But sending limits and enforcement happen at the tenant level.

If one user exceeds safe thresholds, it can impact sending behavior across the entire tenant, not just that mailbox or domain. Read more about the Tenant External Recipient Rate Limit (TERRL)

Isolation protects structure. Enforcement protects the system.

Domain Structure That Scales

Each tenant should have multiple sending domains — not one. We target 12 domains per tenant as a structural maximum. Each domain gets 2–3 mailboxes. That gives you 24–36 mailboxes per tenant, which is enough sending capacity without overloading any single domain.

Your domains should be brand-adjacent but not your primary domain. Use variants: trycompany.com, getcompany.com, companymail.com. Keep your real brand domain off sending infrastructure entirely.

DNS Records You Can't Skip

Every sending domain needs three records configured correctly before a single email goes out:

• SPF — authorizes Microsoft's servers to send on your behalf
• DKIM — cryptographically signs outbound mail (enable in Exchange admin, wait 72hrs for propagation)
• DMARC — policy record that tells receiving servers how to handle failures. Start with p=none and monitor.

Missing any of these means you're flying without authentication. Even a small percentage of unauthenticated mail will tank your sender reputation over time.

Exchange Transport Rules

Exchange transport rules are optional, but they become critical if you're running multiple clients inside the same tenant.

In that setup, multiple users are sending from the same infrastructure. If one sender exceeds safe thresholds, it can affect sending across the entire tenant.

Transport rules allow you to enforce per-mailbox limits at the Exchange level, before mail leaves the tenant. This prevents any single user from pushing volume beyond what the system can safely handle.

You can configure this in the Exchange Admin Center under Mail flow → Rules by creating a rule that limits messages per sender per day.

If you're using TenantCore, this layer is handled automatically. Send limits are enforced at the infrastructure level by default, so individual users or campaign tools can't exceed safe thresholds.

Warmup Before You Send

New mailboxes need 2–4 weeks of warmup before you run cold campaigns through them. Use a warmup tool (Mailreach, Lemwarm, or your sequencer's built-in warmup) and ramp slowly. Start at 5–10 emails/day, increase 20–30% per week.

Don't shortcut this. The warmup period is when you build the sender reputation that all future deliverability depends on.