What is different about warming Microsoft mailboxes
A Microsoft 365 mailbox sends through Exchange Online, and receiving systems, including Microsoft's own, judge it by three things at once: the tenant's reputation, the domain's authentication, and the mailbox's own behaviour. New tenants start with nothing, and Exchange Online Protection is strict about authentication failures in a way that will stall a warm-up long before volume becomes a question. Get the plumbing right and Microsoft mailboxes warm predictably.
Before the first warm-up message
- A dedicated tenant on secondary domains. Never the tenant your company's real mail lives in. One sending mailbox per domain by default, up to 25 sending mailboxes per tenant.
- DKIM actually enabled. Exchange assigns two selector CNAMEs per domain that point at hostnames specific to your tenant. They cannot be guessed from a pattern; the platform reads them from Exchange and publishes them, then confirms Exchange reports DKIM as enabled. This single step is the most common reason Microsoft warm-ups fail.
- SPF with Microsoft's include and DMARC at monitoring. Move DMARC to quarantine once two weeks of reports are clean.
- Application access, not a password. Security Defaults and Conditional Access can silently block the client that sends for you. The platform holds an application grant per tenant and checks it before sending, so a blocked grant is a visible error, not a quiet stop.
- Real names and a plain signature. Name, title, company, one website link. No images, no tracking.
The limits, and the number that matters
| Limit | Exchange Online publishes | Recommendation |
|---|---|---|
| Recipients per mailbox per day | 10,000 | Irrelevant; placement fails long before it |
| Messages per minute | 30 | Warm-up and cold sends are spread across the day |
| Recipients per message | 500 by default | One |
| Cold emails per mailbox per day after warm-up | Not stated | 8 to 10; 5 to 15 is the hard band |
| Time to full volume | Not stated | Two to three weeks |
The schedule
| Days | What the platform does | Cold campaigns |
|---|---|---|
| 1 to 3 | A few warm-up conversations a day to seasoned peers; replies threaded; anything landing in junk is rescued | None |
| 4 to 10 | Volume rises by a fixed daily step; DKIM and refusals watched on every message | None |
| 11 to 16 | Target reached; a placement test at Gmail and Outlook | None |
| 17 to 21 | Target held | Start at 5 a day |
| After 21 | Maintenance warm-up for the life of the mailbox | 8 to 10 a day |
Reading Microsoft's signals
- 5.7.1 and 5.7.5xx refusals are Exchange Online Protection saying no to the sender: authentication, a blocked IP, or a tenant it distrusts. The platform pauses that mailbox for Microsoft recipients and shows the exact code; fix the cause, then resume.
- Junk-folder placement in the placement test at Outlook with inbox placement at Gmail usually means a Microsoft-side authentication issue; the reverse usually means content or a Gmail domain reputation issue.
- Silent stops are almost always the access grant. The console shows a mailbox that has not sent when it should have.
Mixing Microsoft with Google
The best-placing fleets we run use both providers and send to each prospect from the provider their own company uses where that is known. If you only run Microsoft 365 today, adding Google Workspace mailboxes is a provisioning step, not a migration.
Questions, answered straight
- How long does it take to warm up a Microsoft 365 mailbox?
- Two to three weeks to the target volume, the same as Google Workspace. Microsoft ramps tend to be less forgiving of authentication mistakes and more forgiving of volume once the tenant is trusted, so get DKIM right before the first warm-up message.
- Is warming up Outlook.com different from Microsoft 365?
- Yes. Outlook.com (consumer) mailboxes are filtered by Microsoft's consumer systems and are the wrong tool for business cold email. Microsoft 365 mailboxes on your own domains in your own tenant go through Exchange Online Protection with your tenant's reputation. This page is about Microsoft 365.
- Why does my Microsoft 365 warm-up stall in week two?
- The two usual causes: DKIM was never actually enabled for the domain (the selector CNAMEs Exchange assigns are per tenant, and copying a pattern from a blog leaves them wrong), or application access was blocked by Security Defaults and the mailbox silently stopped sending. The platform reads the real selectors from Exchange and handles the access grant at setup.
- How many cold emails per day after warm-up on Microsoft 365?
- 8 to 10 per mailbox per day; 5 to 15 is the hard band. Exchange's published limits are far higher and irrelevant to placement.
- Do I need Microsoft SNDS or JMRP?
- Not for Microsoft 365 mailboxes: those programs are for people who send from their own IP addresses. If you run self-hosted servers, yes, register the IPs in both.
Published 19 September 2026. Updated 19 September 2026. Written by the team that runs the infrastructure; numbers come from the platform's own provisioning and sending, and from the providers' published documentation at the time of writing.