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:
"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.comexists.- It points to
clientconfig.microsoftonline-p.netexactly 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
- Log in to cPanel.
- Go to Zone Editor > Click Manage.
- Find CNAME Record for
msoid.yourdomain.com. - If incorrect, click Edit:
- Name: msoid.yourdomain.com
- Target: clientconfig.microsoftonline-p.net
- TTL: 3600
- Click Save.
For Cloudflare Users
- Log in to Cloudflare > Go to DNS Management.
- Click "Add Record" (if missing) or edit existing CNAME.
- Enter:
- Name: msoid
- Target: clientconfig.microsoftonline-p.net
- TTL: Auto
- Ensure the "Proxy Status" is set to "DNS only" (?? Gray Cloud, not Orange ??).
- 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.
Re-Verify in Microsoft 365 Admin
- Go to Microsoft 365 Admin Center.
- Navigate to Settings > Domains.
- Select your domain.
- Click "Verify DNS Settings".
- 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!



