Skip to content
  • There are no suggestions because the search field is empty.

Microsoft 365 or Google Workspace setup issues

When Microsoft 365 or Google Workspace authentication still isn't working after setup, the usual suspects are DKIM that isn't turned on or isn't published correctly, an extra or overlong SPF record, and third-party senders that don't align with your From domain. Each platform also has its own traps. Microsoft 365 uses two DKIM CNAMEs and is strict about their exact values. Google Workspace uses a long TXT key that some DNS hosts truncate, and it can take up to 48 hours to settle. Find your symptom below, then go to the linked article for the fix.

This page is for "I followed the steps and something's wrong." The setup steps themselves are in DMARC for Microsoft 365 for Microsoft 365 and DMARC for Google Workspace for Google Workspace.

When Microsoft 365 DKIM isn't working

Symptom Cause to check
dkim=none on mail from your custom domain DKIM isn't configured for that domain. Microsoft's DKIM page says: "Currently, no DKIM signing occurs for outbound mail from custom domains" (as fetched 12 Nov 2026). Each sending subdomain needs its own DKIM configuration too.
Status No DKIM keys saved for this domain Keys haven't been created yet. That's the first step in the portal.
The DKIM toggle won't enable; status stays CnameMissing The host name has the domain doubled (selector1._domainkey.example.com.example.com) or lacks _domainkey; a TXT record was published instead of a CNAME; or the CNAME target doesn't match Microsoft's value. Also check trailing-dot handling at your DNS host, and give DNS time.
DKIM enabled, but key rotation fails later The selector2 CNAME is missing. Microsoft requires both.
Intermittent dkim=temperror at receivers The CNAME TTL is too low. Microsoft recommends at least 3600 seconds.

Microsoft lists these in its "Troubleshoot DKIM DNS configuration" section. Copy the CNAME targets from the Defender portal or Get-DkimSigningConfig; not to construct them manually. A TXT key isn't an alternative in Microsoft 365. Managing keys that way "isn't supported." For "DKIM record not found" and selector questions in general, see DKIM signature not found.

Other Microsoft 365 symptoms

  • SPF permerror. Check for two SPF records, for example one left over from a migration, or more than 10 DNS lookups. See Two SPF records and SPF permerror: too many DNS lookups.
  • DMARC failures on marketing or CRM mail. The service is signing with its own domain, not yours. Microsoft calls having the service "DKIM-sign with your domain" the preferred fix. Adding the service's SPF include helps DMARC only if the service's Return-Path uses your domain (Third-party mail fails alignment).
  • dkim=fail (body hash did not verify) behind a gateway or disclaimer tool. Something modified the message after it was signed. Microsoft's options, in its order: ARC on the gateway, having the gateway DKIM-sign after modification, or Enhanced Filtering for Connectors (Why DKIM signatures fail).
  • No DMARC aggregate reports from Microsoft. Microsoft sends them only "as long as the MX record for the Microsoft 365 domain points directly to Microsoft 365". That's about your recipients' tenants, not yours (The rua mailbox is empty).
  • Your *.onmicrosoft.com domain has no DMARC record. Microsoft hosts that DNS, so you add the record in the Microsoft 365 admin center. To add one even if you don't send from it (DMARC for Microsoft 365).
  • Mail to Outlook.com or Hotmail bounces with 550 5.7.515. That's the consumer side, not your tenant. Outlook.com requires high-volume senders to pass SPF and DKIM and publish a passing DMARC record, and can reject or junk mail that doesn't; Microsoft 365 business mailboxes apply their own anti-spoofing checks and settings. Details are in Microsoft and Outlook authentication rules.

Inbound: when your tenant is the receiver

Two Microsoft 365 header results confuse people because they aren't really DMARC problems:

  • compauth=fail reason=001 on partner mail that shows dmarc=pass. Microsoft describes this as composite authentication failing even though standard authentication passed, likely from spoof intelligence. Its fix is a spoof allow entry in the Tenant Allow/Block List.
  • dmarc=bestguesspass. The sender has no DMARC record, and Microsoft 365 "inferred a pass using heuristics."

When Google Workspace DKIM isn't working

Symptom Cause to check
DKIM not passing right after setup Give it time. Google: "After adding a DKIM key, it can take up to 48 hours for DKIM authentication to start working."
The Admin console still says you must update the DNS records for this domain This may show for up to 48 hours. If you've correctly added your DKIM key at your domain provider, you can ignore the message.
Key published but DKIM fails, or the key can't be read A 2048-bit key cut off by the 255-character TXT string limit, or split strings out of order. Split the key into multiple quoted strings in one TXT record and compare with the Admin console value.
Key published, but mail still shows dkim=none Start authentication wasn't clicked in the Admin console after publishing.
Selector conflict The default prefix selector is google. If google._domainkey is already in use for another service, to choose a different prefix.
DKIM fails only for some mail An outbound gateway modifies messages, for example by adding a footer.

Before you regenerate anything, check what's already there. You might not need to set up DKIM "if your domain already has DKIM set up by default, or if you bought your domain from a Google partner," and that if your domain provider is Squarespace, the key is created and added automatically.

Other Google Workspace symptoms

Both platforms

  • Neither platform publishes records at your DNS host for you, apart from the cases above (Microsoft-hosted *.onmicrosoft.com, and Squarespace-hosted DKIM for Google). If your domain is hosted elsewhere, the SPF, DKIM, and DMARC records have to be published there.
  • Your platform's DKIM covers only the mail that platform sends. Every third-party sender needs its own aligned DKIM or SPF (Third-party mail fails alignment).
  • Forwarding still breaks SPF on either platform. Aligned DKIM is what carries forwarded mail through DMARC (Forwarded mail fails DMARC).

Migrating between Microsoft 365 and Google Workspace

  • Keep one SPF record listing both providers during the cutover, within 10 lookups. Then remove the provider you're leaving, for example:

example.com. TXT "v=spf1 include:spf.protection.outlook.com include:_spf.google.com ~all"

  • DKIM selectors can coexist. Google's default is google; Microsoft 365 uses selector1 and selector2. Don't delete the old provider's selector until it has stopped sending.
  • Hold your DMARC policy steady until both sides show aligned results in your reports.

Mistakes worth avoiding

  • Creating only the selector1 CNAME in Microsoft 365.
  • Letting the DNS host double the host name.
  • Regenerating the Google key while the first one is still propagating.
  • A second SPF record added during a migration.
  • Expecting Microsoft reports for recipients whose MX points to a gateway.
  • Treating a compauth quarantine as a DMARC failure.

Free DMARC account

Not sure which sender is failing?

Connect your domain's DMARC reports and see every service that sends as your domain, and whether each one passes SPF, DKIM and DMARC.

  • Every sending source in one dashboard
  • SPF, DKIM and alignment results per sender
  • No XML files to read

Create a free DMARC accountTalk to an expert

FAQ

Microsoft 365 says CnameMissing. What did I do wrong?

Usually a doubled host name, a TXT record instead of a CNAME, or a CNAME target that doesn't match Microsoft's value. If the records are right, give DNS time.

You must update the DNS records even though I did. Why?

That message can show for up to 48 hours. If the key is correct, you can ignore it.

Why don't I get DMARC reports from Microsoft?

Microsoft sends aggregate reports only for recipient domains whose MX points directly to Microsoft 365.

We're moving from Google to Microsoft. Can both be in SPF?

Yes, in one record, within the 10-lookup limit. The DKIM selectors are different, so both can be published at the same time.