If you have configured an MSOID CNAME record for Microsoft 365 or Azure AD authentication, you need to ensure it resolves correctly. This record is critical for proper identity processes and client connections to Microsoft cloud services.
The correct MSOID CNAME record should look like this:
| Record Type | Host (Name) | Value (Target) | TTL |
|---|---|---|---|
| CNAME | msoid.yourdomain.com | clientconfig.microsoftonline-p.net | 3600 |
You can use dig or nslookup commands to verify the MSOID CNAME record.
Expected Output (properly configured):
If there is no output, the CNAME record is missing or hasn't propagated yet.
Expected Output (properly configured):
If command line results are unclear, use these online tools to check global DNS propagation:
msoid.yourdomain.comIf the CNAME resolves to clientconfig.microsoftonline-p.net, the MSOID record is working correctly.
If you recently updated the record but it's still not resolving, try flushing the local DNS cache.
For Windows
For Linux/macOS (systemd)
For Linux (alternative methods)
After flushing the cache, repeat the dig or nslookup command.
Once the MSOID record is resolving correctly, double-check it in Microsoft 365:
If Microsoft confirms the DNS settings are correct, the MSOID record is properly configured and ready for use.
| Problem | Solution |
|---|---|
| MSOID record missing | Add msoid.yourdomain.com > clientconfig.microsoftonline-p.net |
| MSOID not resolving | Wait 24-48 hours for DNS propagation |
| Cloudflare proxy issue | Set proxy to "DNS Only" (?? Grey cloud, NOT ?? Orange) |
| Conflicting CNAME records | Remove duplicates and ensure the value is correct |
| Microsoft 365 still reporting errors | Go to Admin Center > Domains > Verify |
| Record fails verification in admin panel | Check spelling in hostname and target, ensure no extra spaces |
| Task | Steps |
|---|---|
| Check MSOID DNS record | Run dig CNAME msoid.yourdomain.com +short |
| Flush local DNS cache | Use ipconfig /flushdns (Windows) or systemd-resolve --flush-caches (Linux) |
| Check with online tools | Use MXToolbox or WhatsMyDNS |
| Re-verify in Microsoft 365 | Go to Admin Center > Domains > Verify |
| Troubleshoot issues | Check DNS, remove conflicting records, wait for propagation, disable Cloudflare proxy |
Your MSOID record should now resolve correctly for Microsoft authentication!