New Microsoft 365 Domain Can Send Email but Can’t Receive? Here’s the Fix (Step-by-Step)

You’ve just purchased a new domain (e.g., abc.com), set up a brand-new Microsoft 365 (Office 365) subscription, and created a mailbox like aa@abc.com. Outgoing email works perfectly — but incoming email never arrives.

This is one of the most common “new tenant / new domain” scenarios, and the fix is almost always DNS-related — specifically your MX record (and sometimes missing mailbox licensing).

Below is a practical step-by-step guide to get inbound mail flowing.

Why You Can Send but Not Receive

When you send email from Microsoft 365, Microsoft will happily deliver it outward using your mailbox credentials.
But receiving email depends on the public internet knowing where to deliver mail for your domain.

That “where to deliver” instruction is controlled by your domain’s DNS MX record. If your MX record still points to:

  • your old web host (cPanel, shared hosting, etc.)
  • a previous mail provider
  • a placeholder record from your domain registrar
  • or the wrong Microsoft value

…then inbound mail will go somewhere else (or bounce), and your new Microsoft 365 mailbox will never see it.

Quick Checklist Before You Start

✅ You have a Microsoft 365 tenant
✅ The user mailbox exists (e.g., aa@abc.com)
✅ You can send outbound email
❌ You cannot receive inbound email

Let’s fix it.

Step 1: Confirm the Mailbox Has a License (and Actually Exists)

  1. Go to Microsoft 365 admin center
  2. Navigate to Users → Active users
  3. Click the user (e.g., aa@abc.com)
  4. Open Licenses and apps
  5. Ensure a license is assigned that includes Exchange Online (for example: Business Basic, Business Standard, E1/E3/E5, or Exchange Online Plan)

What you’re looking for: Exchange Online is enabled and the mailbox is provisioned.

If there’s no Exchange license, the mailbox may not exist — and inbound mail will fail even if DNS is correct.

Step 2: Verify the Domain Is Added and Verified in Microsoft 365

  1. In Microsoft 365 admin center, go to Settings → Domains
  2. Select your domain (e.g., abc.com)
  3. Ensure the status is Healthy / Verified

If it shows “Setup in progress” or “Not verified,” complete the domain verification first (usually a TXT record).

Step 3: Fix the MX Record (The Most Common Root Cause)

This is the main step.

3.1 Get the Correct MX Value from Microsoft 365

  1. Go to Settings → Domains → abc.com
  2. Select DNS records / View DNS records
  3. Look for the MX record Microsoft provides

It usually looks like:

abc-com.mail.protection.outlook.com

(Your exact value will vary.)

3.2 Update DNS at Your Domain Hosting Provider

Log in to wherever your DNS is hosted (examples: GoDaddy, Cloudflare, Namecheap, VentraIP, Crazy Domains, etc.) and update MX.

Recommended MX setup:

  • Type: MX
  • Name/Host: @ (or leave blank depending on provider)
  • Value/Points to: abc-com.mail.protection.outlook.com (use the one from your tenant)
  • Priority: 0 (or lowest number / highest priority)

3.3 Remove Conflicting MX Records

If you see multiple MX records pointing to other services (old hosting, older mail systems), remove them — unless you intentionally use a third-party email gateway.

Tip: If you keep multiple MX records accidentally, mail may go to the wrong place.

Step 4: Add the Essential Supporting DNS Records (Highly Recommended)

These records don’t always block inbound mail, but they do prevent deliverability issues and make Outlook setup smoother.

SPF (TXT record)

  • Type: TXT
  • Name: @
  • Value:
    v=spf1 include:spf.protection.outlook.com -all

Autodiscover (CNAME record)

  • Type: CNAME
  • Name: autodiscover
  • Value: autodiscover.outlook.com

Step 5: Allow Time for DNS Propagation (Then Retest)

DNS changes can take time to spread globally (often 15–60 minutes, sometimes longer depending on TTL and provider).

Test inbound email:

  • Send an email from a non-Microsoft source (like Gmail) to aa@abc.com
  • Also test from another business mailbox if available

If MX is correct, inbound mail should start arriving once propagation completes.

Step 6: Use Message Trace to See What’s Happening (If Still Not Working)

If inbound mail still doesn’t arrive, message trace tells you whether Microsoft received the email at all.

  1. Go to Exchange admin center
  2. Navigate to Mail flow → Message trace
  3. Search for:
    • Recipient: aa@abc.com
    • Time range: last 1–4 hours
  4. Review status:
    • Delivered
    • Quarantined
    • Failed
    • Filtered / Junked

What the results mean:

  • Nothing shows in trace: mail isn’t reaching Microsoft 365 → DNS/MX still incorrect (or external sender never delivered)
  • Shows as Delivered: check Inbox, Junk, rules, or quarantine
  • Shows as Failed: click details and fix the listed reason

Common Mistakes That Cause “Send Works, Receive Doesn’t”

  • MX record still points to old hosting provider
  • MX record host/name set incorrectly (mail instead of @)
  • Multiple MX records still active from past providers
  • Domain is not fully verified or setup incomplete
  • Mailbox doesn’t have an Exchange Online license

Best Practice: Keep DNS Simple for a New Microsoft 365 Domain

For a clean Microsoft 365 email setup, the minimum reliable DNS set is:

  • ✅ MX → Microsoft 365 (EOP)
  • ✅ TXT (SPF)
  • ✅ CNAME (autodiscover)

Once these are correct, inbound mail is typically resolved immediately after propagation.

Need Help Fixing It Fast?

If you share:

  • who hosts your DNS (e.g., GoDaddy, Cloudflare)
  • a screenshot (or text) of your current DNS records for abc.com

…I can tell you exactly what to change and what to remove, click-by-click.