Configuring a custom domain name cannot verify DKIM, and the CNAME configuration has been added to cloudflare

琉 璃 5 Reputation points
2023-04-01T02:27:46.4+00:00

User's image

User's image

Azure Communication Services
Azure Communication Services
An Azure communication platform for deploying applications across devices and platforms.
736 questions
0 comments No comments
{count} vote

3 answers

Sort by: Most helpful
  1. brtrach-MSFT 15,456 Reputation points Microsoft Employee
    2023-04-06T18:13:49.3066667+00:00

    The verification process for custom domains in Azure Communication Services can take up to 24 hours. During this time, Azure Communication Services will verify that the domain is owned by you and that you have the necessary permissions to use it. Once the domain is verified, you can use it to send and receive messages, make voice and video calls, and more. If you are still having issues after 24 hours, please let me know and I can help you troubleshoot further. Since it's been longer than 24 hours, please let me know if this is still an issue.


  2. Dmytro Chernov 0 Reputation points
    2023-11-15T09:58:56.6233333+00:00

    Hi, I have the same issue, domain status and SPF record verified successfully but DKIM is not, please help User's image

    User's image

    0 comments No comments

  3. Angelo Verlain Shema 0 Reputation points
    2024-05-20T21:11:10.8233333+00:00

    Just FYI, in case you are also encountering this error, this is what solved it for me.

    If you are trying to add an address with a subdomain like "notify.example.com", you will need to add the subdomain name (in this case ".notify") to the CNAME records for DKIM and DKIM2.

    So finally, the records will be something like this:

    Role CNAME Value
    DKIM selector1-azurecomm-prod-net._domainkey**.notify** selector1-azurecomm-prod-net._domainkey.azurecomm.net
    DKIM2 selector2-azurecomm-prod-net._domainkey**.notify** selector2-azurecomm-prod-net._domainkey.azurecomm.net
    0 comments No comments