logo
search
Others

Fix Microsoft 365 Not Recognizing CNAME Record in cPanel

John WilsonJohn Wilson Oct 14, 2026 868 views

Question details

The user added a CNAME record provided by Microsoft 365 to cPanel, but Microsoft 365 fails to detect it during the domain verification process.

How to Fix Microsoft 365 Not Recognizing CNAME Record in cPanel
Product
Microsoft 365 / cPanel
Device & OS
not provided
Scenario
Setting up a custom domain in Microsoft 365 and verifying DNS records via a cPanel hosting environment.
Observed behavior
Microsoft 365 does not detect the CNAME record, preventing the domain setup from successfully completing.
Before you start

Ensure you have administrator access to both your Microsoft 365 admin center and your web host's cPanel dashboard before modifying DNS settings.

Solution 1Recommended

Verify and Correct CNAME Record Settings in cPanel

Ensure the host name and destination exactly match Microsoft's requirements and resolve any conflicting records.

Often, domain setup fails because the DNS records entered in cPanel have slight typographical errors or are conflicting with existing records. Correcting these details is the most common fix.

1
Access cPanel Zone Editor

Log in to your cPanel account and navigate to the 'Zone Editor' tool located under the Domains section.

2
Manage Domain Records

Click the 'Manage' button next to the specific domain you are trying to verify for Microsoft 365.

3
Verify CNAME Values

Locate the CNAME record you added. Verify that the 'Name' (host name) and 'Record' (destination/target) values match the exact strings provided in your Microsoft 365 admin center.

4
Remove Conflicting Records

Check the list for any duplicate CNAME or TXT records using the same host name. Delete any conflicting records that might interfere with propagation.

5
Save and Retry Verification

Save your changes. Wait for DNS propagation (which can take up to 48 hours), then return to the Microsoft 365 domain setup page and click 'Continue' to retry verification.

Verify and Correct CNAME Record Settings in cPanel
DNS Propagation Time: DNS changes can take anywhere from a few minutes to 48 hours to fully propagate across the global internet. If it fails immediately, try again later.
Free Microsoft Office alternative

Skip the Complicated Setups with WPS Office

If managing Microsoft 365 infrastructure and domains is too complex, consider switching to WPS Office. It provides a lightweight, highly compatible, and user-friendly alternative for all your document, spreadsheet, and presentation needs without the hassle of complex cloud setups.

  1. 1. Download WPS Office: Visit the official WPS website and download the free installation package for your operating system.
  2. 2. Install and Launch: Run the installer and follow the on-screen instructions. Once installed, launch the application to access Writer, Spreadsheets, and Presentation.
  3. 3. Open Your Files: Drag and drop your existing Microsoft Office files directly into WPS Office to continue working with perfect formatting.
Fully compatible with Microsoft Office formats (.docx, .xlsx, .pptx).Free and lightweight alternative to Microsoft 365.Familiar user interface makes migration completely seamless.No complex domain setups or DNS configurations required to start working.
microsoft office alternative - wps office

Frequently Asked Questions

Why does Microsoft 365 say my CNAME record is missing?

This typically occurs due to incomplete DNS propagation, a typographical error in the record value, or because the record was added to a non-authoritative DNS zone (meaning your domain's nameservers are pointing elsewhere).

How long does it take for Microsoft 365 to recognize a new CNAME record?

While some DNS changes are detected by Microsoft within 10 to 15 minutes, it can take up to 48 hours for global DNS propagation to complete fully.

Can I use a TXT record instead of a CNAME for Microsoft 365 verification?

Yes, Microsoft 365 typically allows domain ownership verification using either a TXT record or an MX record if you are encountering persistent issues with CNAME records.