Microsoft 365 New Domain Cold Email Problems and How to Avoid Them
New domains on M365 face a double reputation challenge. Here's why deliverability starts poor and the exact steps to avoid the most common traps.
You registered a new domain, set up Microsoft 365 on it for cold outreach, and discovered that deliverability is poor out of the gate. Emails land in Junk, get deferred, or get rejected outright. You did the DNS configuration but Microsoft is not treating your new domain well.
Why new domains on M365 start harder
New domains on Microsoft 365 face a double reputation challenge: the domain has no history and the M365 tenant is new. Microsoft applies heightened scrutiny to new tenants because spammers regularly spin up M365 accounts for bulk sending. This means new domains on M365 start in a worse position than new domains on some other providers.
Microsoft's outbound sending pool is shared. New tenants are placed on lower-reputation IP pools until they establish a positive sending pattern. If other new tenants on the same pool are sending spam, your deliverability suffers. Sending limits for new M365 tenants are also restrictive by design — Microsoft intentionally caps sending volume for new accounts and increases limits as the tenant matures.
Step-by-step diagnosis
Step 1: Confirm all authentication is correct
Check SPF, DKIM (both selectors), and DMARC. Check email headers from test emails. For M365, specifically verify DKIM signing is enabled in the Microsoft 365 Defender portal — not just that the DNS records are published. Use the DKIM checker to verify both selector1 and selector2.
Step 2: Check if you're hitting sending limits
Check bounce messages for rate-limiting errors. New M365 tenants should start at 5–10 emails per day and ramp over weeks. Use the sending limit planner to configure the correct limits.
Step 3: Check domain age
If the domain was registered within the last 30 days, age is a major factor for Microsoft specifically. Check with the domain expiry checker to see registration date. Microsoft weights domain age more heavily than Google for new sender evaluation.
Step 4: Check the sending IP reputation
Check the IP addresses your M365 tenant uses for outbound mail (visible in email headers) against Microsoft SNDS.
The fix path
Do not send cold outreach from the domain until you have warmed it for at least 2–4 weeks. Start with internal communication and warmup network engagement only. New M365 tenants should start at 5–10 emails per day and ramp over weeks, not days.
Use domain aging to your advantage. Register domains 30–60 days before you plan to use them. Set up DNS immediately but do not start sending until the domain has some age. Check your domains' current expiry and registration dates with the domain expiry checker.
Keep warmup running continuously. M365 inboxes need sustained engagement signals just like Google Workspace inboxes. Use the warmup readiness checker before activating any inbox for campaigns.
Repair or replace?
New domain problems on M365 are usually a patience issue. The domain and tenant need time to build reputation. If you give them that time with proper warmup, they will perform.
If you do not have 4–6 weeks to wait, consider using domains that have already been aged and warmed. WarmInboxes provides Microsoft 365 accounts on domains that have been through the maturation process, which eliminates the new-domain penalty entirely.
Run the checks first
Before replacing anything, run a free inbox placement test. You might find the issue is DNS, not the domain — and save yourself a week of unnecessary work.