Era Host hosting
EraHost – Free Domain, Cheap Hosting!
Client Area
Support 24/7
Menu

Fix: "The Record We Detected Doesn't Match All the Expected Values" (MSOID CNAME Issue)

3 min read
02.05.2025
> Important Note: Based on URL analysis, the domain msoid.yourdomain.com appears to be hosting unrelated content. This is likely causing your verification failure. Ensure your CNAME record points to Microsoft's endpoint and not to a web server.

Understanding the Error

When setting up Microsoft 365 or Azure AD, you may encounter the error:

MSOID DNS Configuration Error Fix
Microsoft 365: "The record we detected doesn't match all the expected values" on MSOID.

For the MSOID record context and configuration, see MSOID DNS Record — What It Is and How to Configure It; for verification, Verify That the MSOID Record Works (clientconfig.microsoftonline-p.net); for the deep dive on the endpoint, Understanding clientconfig.microsoftonline-p.net (MSOID CNAME Record).

"The record we detected doesn't match all the expected values."

This means that the CNAME, MX, TXT, or SRV record required for Microsoft authentication is either misconfigured, missing, or not yet propagated.

Check the Required MSOID CNAME Record

Verify that your MSOID record is correctly set in your DNS settings.

Correct MSOID CNAME Format:

Record Type Host (Name) Value (Target) TTL
CNAME msoid.yourdomain.com clientconfig.microsoftonline-p.net 3600

Ensure:

  • msoid.yourdomain.com exists.
  • It points to clientconfig.microsoftonline-p.net exactly as shown.
  • The TTL (Time to Live) is 3600 seconds (1 hour).

How to Check Your DNS Records: Run:

dig CNAME msoid.yourdomain.com +short

Expected output:

clientconfig.microsoftonline-p.net.

If incorrect or missing, fix the DNS record.

Correct the DNS Record in Your Hosting Provider

If the record is incorrect, update it.

For cPanel Users

  1. Log in to cPanel.
  2. Go to Zone Editor > Click Manage.
  3. Find CNAME Record for msoid.yourdomain.com.
  4. If incorrect, click Edit:
    • Name: msoid.yourdomain.com
    • Target: clientconfig.microsoftonline-p.net
    • TTL: 3600
  5. Click Save.

For Cloudflare Users

  1. Log in to Cloudflare > Go to DNS Management.
  2. Click "Add Record" (if missing) or edit existing CNAME.
  3. Enter:
    • Name: msoid
    • Target: clientconfig.microsoftonline-p.net
    • TTL: Auto
  4. Ensure the "Proxy Status" is set to "DNS only" (?? Gray Cloud, not Orange ??).
  5. Click Save.

For Other Registrars (GoDaddy, Namecheap, etc.)

  • Navigate to DNS Management.
  • Locate or add a new CNAME record.
  • Enter:
    • Host: msoid
    • Type: CNAME
    • Value: clientconfig.microsoftonline-p.net
    • TTL: 3600
  • Click Save.

Now, the correct MSOID record should be set.

Check for DNS Propagation

DNS changes can take up to 24-48 hours to propagate.

Verify if the update is live:

  • Run this in the terminal:
    nslookup -type=CNAME msoid.yourdomain.com
  • Use an online tool like:

If the new record appears, Microsoft should now detect it correctly.

cPanel Hosting
Full control over your website
  • Convenient
  • Simple
  • Fast
  • Free 7-day trial
cPanel Hosting

Re-Verify in Microsoft 365 Admin

  1. Go to Microsoft 365 Admin Center.
  2. Navigate to Settings > Domains.
  3. Select your domain.
  4. Click "Verify DNS Settings".
  5. Wait for Microsoft to check the DNS records.

If everything is correct, the error should be resolved.

Troubleshooting If the Error Persists

Issue Fix
DNS Record Still Not Detected Wait 24-48 hours for propagation
Wrong CNAME Target Ensure it is clientconfig.microsoftonline-p.net
Cloudflare Proxy Issue Set Proxy to "DNS only" (Gray Cloud ??)
Multiple Conflicting MX/TXT Records Remove old/incorrect entries

Summary

Task Action
Check Current DNS Record Use dig CNAME msoid.yourdomain.com +short
Update DNS Record Correct CNAME to clientconfig.microsoftonline-p.net
Verify DNS Propagation Use MXToolbox or nslookup
Recheck in Microsoft 365 Go to Admin Center > Domains and Verify

Now your MSOID record should be correctly configured!

Frequently asked questions
Four common mistakes: (1) leading https:// or trailing slash in the value (Microsoft's verifier rejects), (2) an extra dot at the end on a DNS UI that doesn't expect it, (3) a typo in the target (microsoftonline.net instead of microsoftonline-p.net), (4) the wrong DNS record type (TXT instead of CNAME). Compare the published value character-by-character to clientconfig.microsoftonline-p.net.
Almost always propagation. Microsoft queries from multiple regions; one stale resolver in the chain causes the verifier to declare mismatch. Wait until dnschecker.org shows the new value globally, then retry Verify in the Admin Center. The Admin Center's check is the slow path — your own dig run was authoritative once the new value appeared.
Yes if it exists. CNAME alone is what Microsoft expects; an AAAA on the same name confuses some validators and breaks the CNAME chain in others. Removing it has no downside — the CNAME handles both IPv4 and IPv6 by following down the alias chain.
It matters a lot. Orange (proxied) terminates SSL at Cloudflare's edge and serves Cloudflare's IP — Microsoft's MSOID validator receives Cloudflare's address instead of clientconfig.microsoftonline-p.net and fails. Set this record to grey (DNS only) so Cloudflare answers the CNAME and gets out of the way.
Related articles
Fixing t_dkim_invalid (DKIM Signature Issue) in Emails
Fix: MSOID Record Not Resolving (msoid.clientconfig.microsoftonline-p.net)
Fixing session_start(): Permission Denied (13) in XAMPP — System Administrator's Guide