Skip to main content
Five Steps for Cloud Compliance Readiness·A practical playbook for security teamsDownload
CIS Microsoft 365 Foundations v7.0.0 · 2.1.9

DKIM signing should be turned on for every domain that sends mail from Exchange Online

  • E3 Level 1
  • Microsoft Defender
  • Automated check

This check looks at each accepted domain in Exchange Online and whether DKIM signing is enabled for it. The safe setting is that every domain that sends mail through Exchange Online signs its outgoing messages with DKIM.

Why it matters

DKIM adds a cryptographic signature to outgoing mail. The receiving server looks up a public key in your DNS and checks that the message really came through your mail system and was not changed on the way. Without it, a receiver has less to go on when someone sends mail that pretends to be your domain, and your own legitimate mail is more likely to be treated as suspicious.

Microsoft explains how DKIM works with Exchange Online and why it should be set up for custom domains in Use DKIM to validate outbound email sent from your domain. DKIM works best together with SPF and DMARC, which Microsoft describes on the same documentation site.

How to check it yourself

Open the Microsoft Defender portal, go to Email & collaboration, then Policies & rules, Threat policies, and Email authentication settings, and open the DKIM tab. Each domain is listed with its signing status. A domain shown as not signing is a gap.

The same information is available from Exchange Online PowerShell. Both commands only read configuration.

Connect-ExchangeOnline
Get-AcceptedDomain | Select-Object DomainName
Get-DkimSigningConfig | Select-Object Domain, Enabled, Selector1CNAME, Selector2CNAME

A domain that is accepted but missing from the second list, or listed with Enabled set to False, does not sign. Try it on a test tenant or with a read-only role first.

How to fix it

In the Defender portal open the DKIM tab, select the domain and switch on signing. The portal first shows two CNAME records, selector1 and selector2 under the _domainkey name of your domain. Publish both in the public DNS zone for the domain, wait for DNS to update, then enable signing.

Scripted version. It changes your tenant, so ConfigCobra never runs it for you:

# 1. create the signing configuration if the domain has none yet
New-DkimSigningConfig -DomainName example.com -Enabled $false
# 2. publish the two CNAME records shown here in your DNS zone
Get-DkimSigningConfig -Identity example.com | Format-List Selector1CNAME, Selector2CNAME
# 3. once DNS has the records, turn signing on
Set-DkimSigningConfig -Identity example.com -Enabled $true

Repeat for every custom domain that sends mail. The default onmicrosoft.com domain is signed by Microsoft already.

What changes when you fix it

The people affected are everyone who sends mail from the domain, plus whoever manages its DNS. Senders notice nothing: outgoing messages simply carry an extra header with the signature.

  • Two new CNAME records appear in your DNS zone, and they must stay there. Deleting them later makes signing fail.
  • Mail sent by other services on behalf of the domain, such as a newsletter tool, is not signed by this setting. Those services need their own DKIM setup.
  • If DNS is not ready when you switch signing on, the change is rejected, so publish the records first.

Check who manages DNS for each domain before you start, because the CNAME step is often the slow part.

Included in

BenchmarkCIS IDProfile
CIS Microsoft 365 Foundations v7.0.02.1.9E3 Level 1

Check this on your Microsoft 365

ConfigCobra runs this check with every other control of the CIS Microsoft 365 Foundations Benchmark, read-only.

Get in touch

Let's talk.

Whether you're evaluating ConfigCobra, running an audit, or managing a client fleet — we respond within one business day.

Free trial