Introduction

Office 365 mail problems often start right after a DNS change that seemed unrelated to email. A domain move, nameserver update, or zone cleanup can leave Outlook clients, inbound mail, or outbound authentication broken even though the Microsoft 365 tenant itself is fine. The service depends on several DNS records working together, not just one MX entry. The fix is to compare the live zone against the exact Microsoft 365 mail records the domain should be using now.

Symptoms

  • Inbound mail stops arriving after a DNS migration or zone edit
  • Outlook or mobile clients fail to discover mailbox settings automatically
  • Outbound mail authentication or reputation starts failing
  • The issue began after moving DNS providers or replacing old records
  • Some users can send mail, but others see inconsistent mail client behavior

Common Causes

  • The MX record was changed, deleted, or left pointing to the old provider
  • Autodiscover or related Microsoft 365 records were not recreated correctly
  • SPF, DKIM-related setup, or verification records no longer match the active mail flow
  • DNS propagation or split-horizon DNS causes different clients to see different answers
  • A legacy mail provider record still conflicts with Microsoft 365 routing

Step-by-Step Fix

  1. Check the live MX record and confirm it points to the correct Microsoft 365 destination for the domain.
  2. Review Autodiscover and any other required Microsoft 365 DNS entries so mail clients can locate the right service endpoints.
  3. Compare the current zone to the provider’s expected records instead of relying on memory from the previous DNS setup.
  4. Remove or correct leftover records from an old mail provider that may still attract delivery or confuse client setup.
  5. Verify SPF and related sending records so outbound mail still aligns with the platforms allowed to send for the domain.
  6. Test DNS from multiple public resolvers if behavior is inconsistent, because propagation differences can affect client and mail server results differently.
  7. Confirm the domain is still verified and healthy inside Microsoft 365 after the DNS change.
  8. Re-test inbound delivery, outbound sending, and client auto-configuration after the corrected records are live.
  9. Keep a complete mail DNS checklist for Microsoft 365 so future DNS moves do not break mail flow one record at a time.