Fix Microsoft 365 Cannot Validate DKIM CNAME Records
Question details
Microsoft 365 fails to validate DKIM CNAME records even though they exist in the domain's DNS and appear to match the required configuration.

- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Administrators attempting to enable DKIM signing for outbound emails encounter missing record errors or ADObjectAlreadyExistsException.
- Observed behavior
- Microsoft 365 reports that DKIM CNAME records are missing, preventing DKIM validation, despite the records being present in DNS.
Ensure you have administrative access to the Microsoft 365 Admin Center, Exchange Online PowerShell, and your domain's DNS hosting provider.
Reconfigure DKIM via PowerShell and Fix DNS Formatting
Reset the DKIM signing configuration and ensure there are no syntax errors like hyphens or invisible characters in your DNS records.
Often, validation fails because the DKIM configuration object already exists but is out of sync, or the DNS CNAME records contain hidden formatting errors such as invisible spaces or periods used instead of hyphens.
Connect to Exchange Online PowerShell and run 'New-DkimSigningConfig -DomainName <domain> -Enabled $false' to create or update the configuration with signing disabled.
Run 'Get-DkimSigningConfig -Identity <domain> | Format-List Selector1CNAME, Selector2CNAME' to get the exact records expected by Microsoft 365.
Check your DNS provider carefully. Ensure you are using hyphens instead of periods where required (e.g., mydomain-com) and remove any trailing spaces or invisible characters in the selector fields.
After fixing the DNS records and allowing time for propagation, run 'Set-DkimSigningConfig -Identity <domain> -Enabled $true' to activate DKIM.

Request a Validate DKIM Signing Diagnostic
Ask Microsoft Support to run a backend diagnostic if manual PowerShell configuration fails to identify the mismatch.
Looking for a simpler way to handle your daily documents?
While Microsoft 365 administration requires dealing with complex domain and DNS policies like DKIM, your daily document tasks shouldn't be complicated. WPS Office provides a seamless, lightweight, and completely free alternative for creating and editing your important files without the administrative headaches.

Frequently Asked Questions
Why does Microsoft 365 say my DKIM CNAME records are missing?
This usually occurs due to DNS propagation delays, invisible characters in the DNS entry, or minor formatting errors, such as using a period instead of a hyphen in the domain selector name.
What does the ADObjectAlreadyExistsException mean when setting up DKIM?
This exception means a DKIM configuration object has already been created for your domain in Microsoft 365. You should use the 'Set-DkimSigningConfig' command to modify it instead of trying to create a new one.
How do I check my current DKIM signing configuration?
Open Exchange Online PowerShell and run the command 'Get-DkimSigningConfig -Identity <yourdomain>' to view your current selectors, CNAME requirements, and enablement status.




