Azure Communication Services
An Azure communication platform for deploying applications across devices and platforms.
Cannot add domain - Resource type not found in namespace
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 57.00000000000001%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMF%3C/text%3E%3C/svg%3E)
Martin Framstad Lokrheim
10
Reputation points
I am not able to add a custom domain to a Email Communication Service in Azure, the process is stuck in the "Finish" step. I have tried in two different Tenants, and a Lab Subscription
Same thing happens when attempting through the "Provision Domain" blade -> Add Domain -> Custom Domain.
This error message is displayed at the top of the Privision Domain blade:
The resource type 'EmailServices/Domains' could not be found in the namespace 'Microsoft.Communication' for api version '2025-09-01-preview'. The supported api-versions are '2021-10-01-preview,2022-07-01-preview,2022-10-01-preview,2023-03-01-preview,2023-03-31,2023-04-01-preview,2023-04-01,2023-06-01-preview,2024-09-01-preview,2024-11-01-preview,2025-01-25-preview,2025-09-01'.
It is not possible to Add a free Azure subdomain either.
Azure Communication Services
{count} vote
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(208, 84%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJV%3C/text%3E%3C/svg%3E)
Joan Vandellos 0 Reputation points2025-12-11T10:22:14.23+00:00 I have the same problem.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(99.2, 85%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGV%3C/text%3E%3C/svg%3E)
Golla Venkata Pavani 270 Reputation points Microsoft External Staff Moderator2025-12-11T11:56:00.89+00:00 Hii @Martin Framstad Lokrheim,
Thank you 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.
The only valid API versions for emailServices/domains are- 2025-05-01 (latest stable)
- 2024-11-01-preview, 2024-09-01-preview
- 2023-03-31, 2023-04-01-preview, etc.
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.az communication email domain create --resource-group <YourResourceGroup> --service-name <YourEmailServiceName> --name <yourdomain.com> --location Global --domain-management CustomerManagedStep 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 "upvote" if the information helped you. This will help us and others in the community as well.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 81%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
Amal Syed 60 Reputation points2025-12-11T15:25:41.5033333+00:00 Even I have the same problem. So is basically MS that incompetent?
-
Golla Venkata Pavani 270 Reputation points Microsoft External Staff Moderator
2025-12-17T06:58:36.18+00:00 Hii @Martin Framstad Lokrheim,
I am Just checking in to see if you had a chance to see the previous response posted by me. If you have any further questions do let us know.
Sign in to comment
Sign in to answer