Fix Microsoft 365 custom-domain email not working: when this repair path applies
Compare the current MX/SPF/autodiscover records with the values shown for the domain in Microsoft 365. Use these steps when Exchange Online DNS records are missing, wrong or still point to another mail system, but first run the embedded diagnostic so the business-email DNS and mail authentication evidence supports this provider-specific path rather than a neighboring DNS, TLS, application or mail cause.
Find the authoritative setting before editing
Microsoft 365 Admin Center for assigned DNS values and the authoritative DNS provider for publication. For Fix Microsoft 365 custom-domain email not working, confirm the active nameservers and exact service owner before changing check MX. A DNS-looking screen at microsoft-365 has no public effect when another provider is authoritative for the zone.
Evidence to save for Fix Microsoft 365 custom-domain email not working
Record the current public state for check MX, merge SPF into one policy, check autodiscover. This gives the repair a before/after comparison and prevents a cached answer or a separate working service from being confused with the configuration that produced the symptom.
- Check MX — Read the public MX priorities and targets, then verify that each target itself resolves. A visible MX record is not enough if its mail hostname is broken.
- Merge SPF into one policy — Inspect the single public v=spf1 policy, validate its terms and count DNS-query-causing mechanisms; duplicate policies or excessive lookups can invalidate SPF.
- Check autodiscover — Verify check autodiscover from the public Internet and compare it with the value the responsible provider says should be live.
- Remove obsolete conflicting MX — Read the public MX priorities and targets, then verify that each target itself resolves. A visible MX record is not enough if its mail hostname is broken.
Repair steps in microsoft-365
Compare the current MX/SPF/autodiscover records with the values shown for the domain in Microsoft 365.
- 1. Check MX. After this step, check the public value tied to check mx before changing another unrelated setting.
- 2. Merge SPF into one policy. After this step, check the public value tied to merge spf into one policy before changing another unrelated setting.
- 3. Check autodiscover. After this step, check the public value tied to check autodiscover before changing another unrelated setting.
- 4. Remove obsolete conflicting MX. After this step, check the public value tied to remove obsolete conflicting mx before changing another unrelated setting.
Why this order matters for microsoft-365
The sequence begins with the provider/authority decision, then moves through check MX, merge SPF into one policy, check autodiscover. That keeps the change scoped to the failed business-email DNS and mail authentication path and avoids replacing nameservers, mail authentication or another healthy service just to make a provider dashboard indicator change.
Verify Fix Microsoft 365 custom-domain email not working
The public MX/authentication records should match the intended mail provider, required hostnames should resolve, and the relevant SPF/DKIM/DMARC check should no longer show the original failure. Compare the same check MX and merge SPF into one policy evidence used before the change; a repair is complete when the public result agrees, not merely when the microsoft-365 interface reports that a save succeeded.
If microsoft-365 and the public result disagree
Check whether the edited zone is authoritative, whether the exact root/www/subdomain was changed, whether a proxy state alters the visible endpoint, and whether a prior TTL can still exist in recursive caches. Do not add a second conflicting check MX value to force validation.
Mistakes to avoid for this repair
Do not copy tenant-specific or region-specific values from another account, delete working email records during a website repair, change nameservers as a shortcut, or alter SSL/proxy modes without evidence from the origin. Fix Microsoft 365 custom-domain email not working should change only the settings required by this diagnosis.
Technical references
These primary standards and provider documents are used to verify the behavior described on this page. Provider dashboards can change, so use the current official value for tenant-specific DNS records rather than copying an example from another account.