Getting Error in Email Communication Service

Hii @Amal Syed,

Thank you for reaching us regarding the issue.

Azure Communication Services (ACS) recently added new features and updated APIs for email domains. The UI was updated, but the backend domain provisioning blade is referencing an API version that isn’t published for the emailServices/domains resource type.

Update your Terraform or API requests to use a supported API version

• 2025-05-01 (latest stable)
• 2024-11-01-preview, 2024-09-01-preview
• 2023-03-31, 2023-04-01-preview, etc.

Verify Region Support

Email Communication Service domain features are not yet available in all regions.

Europe regions sometimes lag behind (common customer reports). If the resource was deployed in West Europe or North Europe, domains may not appear because ECS backend capabilities haven’t rolled out.

How to check:

1. Go to Azure Resource Explorer
2. Browse to your region > Microsoft.Communication
3. Check if EmailServices/Domains is listed

If not listed > region not yet enabled.

Until the portal is updated, domain provisioning must be done using Azure CLI or ARM with a supported API version.

So, Please follow the below steps to add a custom domain in ACS.

Ensure Azure CLI is installed and updated (az upgrade), then log in with az login. Identify your Email Communication Service name, resource group, and desired domain.
Step 1: Create Domain Resource Below command bypasses the portal, uses the supported API version, and successfully creates the domain.

Azure CLI

az communication email domain create --resource-group <YourResourceGroup> --service-name <YourEmailServiceName> --name <yourdomain.com> --location Global --domain-management CustomerManaged

Step 2: Verify Domain Ownership

• In the Azure portal, navigate to your Email Communication Service > Provision Domains.
• Select the new domain and click Configure or Verify Domain.
• Copy the provided TXT record value (e.g., azcommunicationcenter.azurecomm.net).
• Add this TXT record to your domain's DNS provider at the root (@ or blank name field), then wait 15-30 minutes for propagation.
• Click Next > Done in the portal to verify. Status changes to Verified.

Step 3: Configure Sender Authentication

• In Provision Domains, click Configure on the verified domain.
• Add the provided SPF TXT record and two DKIM CNAME records to your DNS:
  • SPF: e.g., v=spf1 include:spf.protection.outlook.com -all
    • DKIM: e.g., selector1._domainkey and selector2._domainkey pointing to Azure values.
    • Wait 15-30 minutes, then verify in portal (click Next > Done). Status updates to Enabled.

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/cli/azure/communication/email/domain?view=azure-cli-latest#az-communication-email-domain-create
Kindly let us know if the above comment helps or you need further assistance on this issue.

Please "Accept" if the information helped you. This will help us and others in the community as well.