Share via

Communication Service can't connect to a verified domain

PN 20 Reputation points
2026-03-26T17:15:14.0533333+00:00

When connect email domain in communication service, I see there is no verified domain under the email service, but in Email communication Service-->settings-->Provision domain, i can see my custom domain have been all verified (SPF/DKIM/DKIM2). What am i missing? Thank you

Azure Communication Services

2 answers

Sort by: Most helpful
  1. Praneeth Maddali 7,315 Reputation points Microsoft External Staff Moderator
    2026-03-26T18:07:57.54+00:00

    Hi @PN

    Thank you for providing the details. I understand the situation: your custom domain is fully verified (Domain status, SPF, DKIM, DKIM2) in the Email Communication Service under Settings > Provision domains, but it does not show up in the main Azure Communication Services resource when you attempt to connect it. This is a common issue.

    Even though the domain is verified and ready in the Email service, you still need to explicitly connect it to your Communication Services resource. The two resources are intentionally decoupled, so verification alone doesn’t make the domain visible for sending emails.

    Quick fix:

    1. Go to your Azure Communication Services resource (the main one, not the Email one).
    2. In the left menu under Email, click Domains.
    3. Click Connect domain.
    4. In the blade that opens, filter by your Subscription, Resource Group, and Email Service, then select your verified custom domain and click Connect.

    That’s usually all you need to do. Once you’re connected, you can start sending emails right away.

    Before proceeding, check this: Ensure that the Data location (geography) for your Email Communication Service matches exactly with your Communication Services resource. If they don’t match, the domain won’t appear — you’ll need to set it up in an Email service with the same data location.

    Reference:

    https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/email/connect-email-communication-resource?pivots=azure-portal

    https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/email/add-custom-verified-domains?pivots=platform-azp

    https://learn.microsoft.com/en-us/azure/communication-services/concepts/email/email-domain-configuration-troubleshooting

    If the answer is helpful,  Please do click "Accept the answer” and Yes, this can be beneficial to other community members.

    If you have any other questions, let me know in the "comments" and I would be happy to help you

    0 comments No comments

  2. Q&A Assist
    2026-03-26T17:15:27.35+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The verified domain in Email Communication Service must be explicitly linked to the Azure Communication Services (ACS) resource before it appears as a selectable/connected domain for sending.

    What is happening:

    • The domain is fully verified at the Email Communication Service → Settings → Provision domain level (SPF/DKIM/DKIM2 all OK).
    • It is not yet connected/linked to the Communication Service resource, so ACS shows no verified domains under Email.

    To fix this, connect the verified domain to the Communication Service resource.

    Portal method:

    1. Open the Azure Communication Service resource.
    2. In the left navigation under Email, select Domains.
    3. Select Connect domain.
    4. In the picker, filter by:
      • Subscription
      • Resource group
      • Email Service
      • Verified Domain
    5. Select the verified custom domain that is already validated in Email Communication Service.
    6. Click Connect.

    Important constraints:

    • The Communication Service resource and the Email Communication Service/domain must be in the same geography (data location). If they are in different geographies, the domain will not appear in the list to connect.
    • Only verified domains can be connected.

    If using REST/SDK instead of portal, ensure the Communication Service resource has the linkedDomains property set to the Email domain resource ID, for example:

    {
      "properties": {
        "linkedDomains": [
          "/subscriptions/{subscription-id}/resourceGroups/{resource-group-name}/providers/Microsoft.Communication/emailServices/{email-service-name}/domains/{domain-name}"
        ]
      }
    }
    

    Once the domain is linked, it will show up under the Communication Service → Email → Domains, and can be used for sending.


    References:

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.