Security Policy Errors

Fix Microsoft 365 DKIM When CNAME Records Exist

Amos GikundaAmos Gikunda Nov 22, 2026 868 views

Question details

Enable DKIM for a Microsoft 365 domain when the service reports missing CNAME records despite external DNS checks showing them.

Fix Microsoft 365 DKIM When CNAME Records Exist
Product
Microsoft 365 and Exchange Online
Device & OS
not provided
Scenario
An administrator has published DKIM CNAME records and wants to enable DKIM signing for a custom domain.
Observed behavior
Microsoft 365 reports that the DKIM CNAME records are missing even though external DNS tools can find them.
Before you start

Identify the custom domain and have access to its authoritative DNS provider and a Microsoft 365 account with Exchange Online administrative permissions. If the DNS records were recently changed, allow time for propagation before retrying.

Solution 1Recommended

Verify DKIM CNAME targets and enable signing with PowerShell

Use Exchange Online PowerShell to inspect the domain configuration, confirm both DNS targets, and retry DKIM activation.

1
Connect to Exchange Online

Open PowerShell, install the ExchangeOnlineManagement module if needed with Install-Module ExchangeOnlineManagement, and run Connect-ExchangeOnline. Sign in with an account that can manage DKIM.

2
Inspect the DKIM configuration

Run Get-DkimSigningConfig -Identity contoso.com | Format-List, replacing contoso.com with your domain. Review the configuration, including the selector CNAME values and enabled status.

3
Verify both DNS records

In your DNS provider's management console, compare the selector1 and selector2 CNAME hostnames and targets with the values shown in the DKIM configuration or Microsoft Defender portal. Correct any mismatches and check that the records are published in the authoritative DNS zone.

4
Enable DKIM

After DNS changes have propagated, run Set-DkimSigningConfig -Identity contoso.com -Enabled $true in the connected PowerShell session. Then rerun Get-DkimSigningConfig -Identity contoso.com | Format-List and check that Enabled is True.

Verify DKIM CNAME targets and enable signing with PowerShell
If the command still reports missing records: Recheck both hostnames and targets, allow more time for DNS propagation, and check Microsoft 365 service health before retrying.
Free Microsoft Office alternative

Use WPS Office for compatible documents while managing Microsoft 365

WPS Office is a free, lightweight, easy-to-use alternative for working with Office documents. Its familiar interface and format support make it easy to move between applications, although it does not fix Microsoft 365 DKIM or DNS settings.

Document editing is separate from Microsoft 365 DKIM configurationCompatible with Microsoft Office formats including DOCX, XLSX, and PPTXFree, lightweight office suite with a familiar interfaceOpen existing Office files to make migration easier
microsoft office alternative - wps office

Frequently Asked Questions

Why does Microsoft 365 say my DKIM CNAME records are missing?

DNS changes may still be propagating, or one of the two CNAME hostnames or targets may not match the domain's Microsoft 365 configuration. Compare both records in your DNS provider's console with the values shown by Get-DkimSigningConfig.

How can I check whether DKIM is enabled?

Connect to Exchange Online PowerShell and run Get-DkimSigningConfig -Identity contoso.com | Format-List, replacing contoso.com with your domain. Check the Enabled value in the output.

Can I enable DKIM from PowerShell?

Yes. After connecting with Connect-ExchangeOnline and verifying both CNAME records, run Set-DkimSigningConfig -Identity contoso.com -Enabled $true with your domain name.

Where can I check for a Microsoft 365 service incident?

In the Microsoft 365 admin center, go to Health > Service health and review active Exchange Online incidents and advisories.