Security Policy Errors

Fix Microsoft 365 DKIM Signing Failures for a Custom Domain

Kushani NimanthikaKushani Nimanthika Nov 22, 2026 868 views

Question details

A user needs to restore DKIM signing for a custom domain in Microsoft 365 after messages stopped being signed.

Fix Microsoft 365 DKIM Signing Failures for a Custom Domain
Product
Microsoft 365 and Exchange Online
Device & OS
not provided
Scenario
Outgoing messages from a custom domain previously passed DKIM checks but later appeared without the expected custom-domain signature.
Observed behavior
Some messages appear not to be signed with the custom domain, potentially because of changed CNAME records, selector configuration, or Microsoft 365 DKIM settings.
Before you start

Sign in with an account authorized to manage DKIM in Microsoft 365, and make sure you can access the custom domain's DNS records. Obtain full headers from a successful message and a recent affected message if available.

Solution 1Recommended

Verify DKIM CNAME Records and Re-enable Signing

Use this approach when custom-domain signing has stopped or Microsoft 365 cannot find the expected DKIM records.

1
Open DKIM settings

In the Microsoft Defender portal, go to Email & collaboration > Policies & rules > Threat policies > Email authentication settings, then open the DKIM tab and select the custom domain.

2
Check Microsoft's expected values

Review the domain's DKIM details for the current selector1 and selector2 CNAME names and targets. If prompted, select Create DKIM keys and follow the displayed instructions.

3
Compare the DNS records

Open the DNS management page for the domain and compare both selector CNAME records with the values shown by Microsoft. Correct missing or changed records, then allow time for DNS changes to propagate.

4
Check the signing setting

Return to the domain's DKIM settings and enable signing if it is off. If it is already enabled and the records are correct, try disabling and re-enabling the custom-domain signature.

5
Send a test message

Send a new message from the custom domain to an external mailbox, then open the received message's full headers to check for a DKIM-Signature using the custom domain.

Verify DKIM CNAME Records and Re-enable Signing
Use the displayed CNAME targets: DKIM target values can vary by tenant and domain. Use the current values in the Microsoft 365 configuration rather than copying examples from another domain.
Free Microsoft Office alternative

Document Your DKIM Troubleshooting in WPS Writer

WPS Office is a free, lightweight alternative with a familiar interface and Microsoft Office format compatibility for easy migration. Use WPS Writer to organize DNS checks and message-header findings; Microsoft 365 DKIM settings must still be managed in the Microsoft Defender portal.

Document DKIM selector checks and troubleshooting results in WPS WriterOpen and save Microsoft Word DOCX documentsUse a familiar interface for an easier transition from Microsoft OfficeWork with a free, lightweight office suite
microsoft office alternative - wps office

Frequently Asked Questions

Where can I find DKIM settings for my Microsoft 365 domain?

In the Microsoft Defender portal, go to Email & collaboration > Policies & rules > Threat policies > Email authentication settings, then select the DKIM tab and your domain.

Do I need both selector1 and selector2 CNAME records?

Yes. Check both records in your DNS provider's management page against the current values shown for the domain in Microsoft 365 DKIM settings.

How can I tell whether a message was signed by my custom domain?

Open the received message's full headers and look for a DKIM-Signature field whose d= value matches your custom domain. The s= value identifies the selector used.

Does a DKIM failure always mean the message was not signed?

No. A message can contain a DKIM signature that fails verification. Compare the DKIM-Signature and Authentication-Results fields in the full headers to distinguish a missing signature from a failed one.

Why might DKIM still fail immediately after I update DNS?

DNS changes can take time to propagate. After updating the CNAME records, wait for the changes to propagate, check the records again, and send a new test message.