Security Policy Errors

Fix Microsoft 365 “No DKIM Keys Saved for This Domain” Error

Natalie TaylorNatalie Taylor Nov 22, 2026 868 views

Question details

The user needs to enable DKIM signing for a custom domain in Microsoft 365 purchased through GoDaddy.

Fix “No DKIM Keys Saved for This Domain” in Microsoft 365
Product
Microsoft 365 Exchange Online
Device & OS
not provided
Scenario
The user is configuring DKIM for a custom email domain but cannot use PowerShell.
Observed behavior
Microsoft 365 displays “No DKIM keys saved for this domain” when the user tries to enable DKIM.
Before you start

Confirm the custom domain is set up in Microsoft 365 and identify who can manage its authoritative DNS records. You will also need an account with permission to manage DKIM or help from a Microsoft 365 administrator.

Solution 1Recommended

Create DKIM keys and publish the CNAME records

Use the Microsoft Defender portal and your DNS provider to configure DKIM without PowerShell, if your account has the required permissions.

1
Open DKIM settings

Sign in to the Microsoft Defender portal at security.microsoft.com. Go to Email & collaboration > Policies & rules > Threat policies > Email authentication settings, then open the DKIM tab.

2
Create keys and copy the records

Select your custom domain. If a Create DKIM keys option is available, select it, then copy both CNAME names and targets shown for the domain.

3
Add the DNS records

Open your domain's DNS management page, such as GoDaddy's DNS page if GoDaddy hosts the DNS. Add the two CNAME records using the names and targets supplied by Microsoft 365.

4
Enable DKIM signing

After the DNS changes propagate, return to the DKIM tab, select the domain, and turn on DKIM signing. If Microsoft 365 cannot find the records yet, wait and try again.

5
Check a signed message

Send a message from an address on the custom domain to a mailbox where you can view message headers. Open the received message's headers and check for a DKIM-Signature header and a passing DKIM result.

Create DKIM keys and publish the CNAME records
DNS changes may take time: DNS propagation can take several hours or longer. Use the exact CNAME targets provided for your tenant; do not copy targets from another domain.
Free Microsoft Office alternative

Work with Office documents in WPS Office

WPS Office is a free, lightweight alternative with a familiar interface for working with Office files. It can help you move your document workflow, but it does not configure Microsoft 365 DKIM or fix Exchange Online errors.

Create and edit documents, spreadsheets, and presentations in one suiteOpen and work with Microsoft Office formats such as DOCX, XLSX, and PPTXUse a familiar interface to make moving everyday document work easierKeep document work separate from Microsoft 365 email security administration
microsoft office alternative - wps office

Frequently Asked Questions

Where do I find the DKIM CNAME records for my domain?

In the Microsoft Defender portal, go to Email & collaboration > Policies & rules > Threat policies > Email authentication settings > DKIM. Select your domain and create keys if prompted to see the CNAME details.

Do I have to use PowerShell to enable DKIM?

Not always. If your account has the required permissions and the portal offers key creation, you can configure DKIM through the portal and your DNS provider. If the error persists, an administrator may need Exchange Online PowerShell.

Why can't Microsoft 365 find the CNAME records I just added?

DNS changes may not have propagated yet, or the records may have been added at a provider that is not authoritative for the domain. Check the CNAME names and targets in your authoritative DNS settings, then wait and retry.

Who can help if my Microsoft 365 subscription is through GoDaddy?

Ask your Microsoft 365 global administrator first. If the issue remains unresolved, contact GoDaddy support for the subscription or Microsoft Support as appropriate.

How can I verify that DKIM signing is working?

Send a message from the custom domain to a mailbox that displays message headers. In the received message's headers, look for a DKIM-Signature header and a passing DKIM result.