Communication Services: Email DKIM Verification Stuck — Ongoing Issue

Question

Communication Services: Email DKIM Verification Stuck — Ongoing Issue

KevinMarsh-0076 0

Have posted this here already and saw a response that an engineer will need to look at it, but heard nothing more. This is still an issue

Problem description

I am experiencing an issue where the DKIM verification for my custom domain in Azure Communication Services Email remains stuck at 'Verification in progress', despite the DNS records being correctly configured and publicly resolvable.

Environment

Azure Communication Services Email with an associated Communication Services resource; custom email domain hosted in public DNS.

What I've already tried

I checked the public DNS resolution for the DKIM selector CNAME records using public DNS resolvers; both records are resolvable and match the Azure Portal targets. I verified that the domain ownership, SPF, and DKIM2 are verified, while DKIM1 is still in 'Verification in progress'. I confirmed the authoritative DNS records for the selectors match the expected values. I also checked the DNS records' creation and update times; records were created during setup and have not been altered since, with no proxy or flattening enabled.

Current status

I am seeking assistance to understand why the DKIM1 verification remains pending despite correct DNS configuration, and to explore steps to resolve this backend verification issue.

Ajay Rathod 450 Reputation points Microsoft External Staff Moderator

2026-10-14T16:26:20.8633333+00:00

Hi @KevinMarsh-0076

Thanks for reaching out to Q&A. We are looking into this is and we will get to you on this.

1 answer

Your answer

Ajay Rathod 450 Reputation points Microsoft External Staff Moderator

2026-10-14T16:26:20.8633333+00:00

Hi @KevinMarsh-0076

Thanks for reaching out to Q&A. We are looking into this is and we will get to you on this.

Answer 1

Salamat Shah 910 MVP

Since the DNS records are resolving correctly and DKIM remains stuck in "Verification in Progress", this is likely a backend issue rather than a DNS configuration problem.

First check in records properly placed in the public DNS or not, mostly copy paste records from the ACS sometime not properly and such kind an issue occurs.

Also, its recommended to Open or follow up on a Microsoft Support case and provide the ACS resource details and domain name. The support team can verify the backend status and re-trigger the DKIM validation process if required.

0 comments