Azure communication/email service ARM deployment error with linkedDomains

Question

Azure communication/email service ARM deployment error with linkedDomains

wunderbar 20

The error is:
"Requested linked domains are not valid (Code: InvalidLinkedDomains)"

It is definetely due to the following line

"linkedDomains": [
    "[resourceId('Microsoft.Communication/emailServices/domains',variables('acsename'),'AzureManagedDomain')]"
]

of the communicationServices resource. When deployed with linkedDomains as empty array - communication service is created successfully (but, of course, without linked domain).

ARM Template (taken from the answer in https://learn.microsoft.com/en-us/answers/questions/1189581/azure-communication-service-email-arm-deployment-e):

{
    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
    "contentVersion": "1.0.0.0",
    "parameters": {
        "acsemailName": {
            "type": "string"
        },
        "tagsByResource": {
            "type": "object"
        },
        "dataLocation":{
            "type": "string"
        }
    },
    "functions": [],
    "variables": {
        "acsename": "[concat(parameters('acsemailName'),'-email')]"
        
    },
    "resources": [
        {
            "type": "Microsoft.Communication/emailServices",
            "apiVersion": "2022-07-01-preview",
            "location": "global",
            "name" :"[variables('acsename')]",
            "tags": "[parameters('tagsByResource')]",
            "properties":{
                "dataLocation" :"[parameters('dataLocation')]"
            }
        },
        {
            "type": "Microsoft.Communication/communicationServices",
            "apiVersion": "2022-07-01-preview",
            "location": "global",
            "name" : "[concat(parameters('acsemailName'),'-cs')]",
            "tags": "[parameters('tagsByResource')]",
            "dependsOn":[
                "[resourceId('Microsoft.Communication/emailServices/domains',variables('acsename'),'AzureManagedDomain')]"
            ],
            "properties": {
                "dataLocation":"[parameters('dataLocation')]",
                "linkedDomains": [
                    "[resourceId('Microsoft.Communication/emailServices/domains',variables('acsename'),'AzureManagedDomain')]"
                ]
            }
        },
        {
            "type": "Microsoft.Communication/emailServices/domains",
            "apiVersion": "2022-07-01-preview",
            "location": "global",
            "name": "[concat(variables('acsename'),'/AzureManagedDomain')]",
            "tags":"[parameters('tagsByResource')]",
            "properties":{
                "domainManagement": "AzureManaged",
                "userEngagementTracking": "Enabled",
                "validSenderUsernames":{"DoNotReply": "DoNotReply"}
            },
            "dependsOn": [
                "[resourceId('Microsoft.Communication/emailServices', variables('acsename'))]"
            ]
        }
    ],
    "outputs": {}
}

VenkateshDodda-MSFT 25,111 Microsoft Employee Moderator

@wunderbar Thanks for reaching out to Microsoft Q&A, apologize for any inconvenience caused on this.

Please update the values of linkedDomains and dependsOn property under Microsoft.Communication/CommunicationService with the below

"[resourceId('Microsoft.Communication/emailServices/domains',concat(parameters('acsemailName'), '-email'),'AzureManagedDomain')]"

or update the entire block of Microsoft.Communication/CommunicationService in the above shared ARM template.

{
         "type":"Microsoft.Communication/CommunicationServices",
         "apiVersion":"2022-07-01-preview",
         "name":"[concat(parameters('acsemailName'),'-cs')]",
         "location":"global",
         "tags":"[parameters('tagsByResource')]",
         "properties":{
            "dataLocation":"[parameters('dataLocation')]",
            "linkedDomains":[
                "[resourceId('Microsoft.Communication/emailServices/domains',concat(parameters('acsemailName'), '-email'),'AzureManagedDomain')]"
            ]
         },
         "dependsOn":[
           "[resourceId('Microsoft.Communication/emailServices/domains',concat(parameters('acsemailName'), '-email'),'AzureManagedDomain')]"
         ]
      }

and retry the deployment and let us know if you are facing the issue.
I have made the above suggested changes and able to deploy the ACS, ACS email service and provision managed domain without any issues.

Please refer to the sample output screenshot for your reference.

User's image

Feel free to reach back to me if you have any further questions on this.

wunderbar 20

@VenkateshDodda-MSFT thanks for the quick reply, but unfortunately it's still not working for me.

Is there anything else I can share with you to help in troubleshooting (name of the deployment or Correlation ID)?

Image with error: azure-comm-svc-error

Let me duplicate again ARM template with your fix (just in case):

{
    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
    "contentVersion": "1.0.0.0",
    "parameters": {
        "acsemailName": {
            "type": "string",
            "defaultValue": "email-test",
            "metadata": {
                "description": "email service name"
              }
        },
        
        "dataLocation":{
            "type": "string",
            "defaultValue": "United States",
            "metadata": {
                "description": "data location (United States)"
              }
        }
    },
    "functions": [],
    "variables": {
        "acsename": "[concat(parameters('acsemailName'),'-email')]"
        
    },
    "resources": [
        {
            "type": "Microsoft.Communication/emailServices",
            "apiVersion": "2022-07-01-preview",
            "location": "global",
            "name" :"[variables('acsename')]",
            
            "properties":{
                "dataLocation" :"[parameters('dataLocation')]"
            }
        },
    {
         "type":"Microsoft.Communication/CommunicationServices",
         "apiVersion":"2022-07-01-preview",
         "name":"[concat(parameters('acsemailName'),'-cs')]",
         "location":"global",
         "properties":{
            "dataLocation":"[parameters('dataLocation')]",
            "linkedDomains":[
                "[resourceId('Microsoft.Communication/emailServices/domains',concat(parameters('acsemailName'), '-email'),'AzureManagedDomain')]"
            ]
         },
         "dependsOn":[
             "[resourceId('Microsoft.Communication/emailServices/domains',concat(parameters('acsemailName'), '-email'),'AzureManagedDomain')]"
         ]
        },
        {
            "type": "Microsoft.Communication/emailServices/domains",
            "apiVersion": "2022-07-01-preview",
            "location": "global",
            "name": "[concat(variables('acsename'),'/AzureManagedDomain')]",
            
            "properties":{
                "domainManagement": "AzureManaged",
                "userEngagementTracking": "Enabled",
                "validSenderUsernames":{"DoNotReply": "DoNotReply"}
            },
            "dependsOn": [
                "[resourceId('Microsoft.Communication/emailServices', variables('acsename'))]"
            ]
        }
    ],
    "outputs": {}
}

wunderbar 20 Reputation points

2023-07-26T16:22:34.61+00:00

VenkateshDodda-MSFT, I've created a new azure account, new subscription and group, and deployed this ARM template there to eliminate account specific configuration issues. The result is absolutely the same:

Accepted answer

0 additional answers

Your answer

VenkateshDodda-MSFT 25,111 Reputation points Microsoft Employee Moderator

2023-07-26T13:53:54.19+00:00

@wunderbar Thanks for reaching out to Microsoft Q&A, apologize for any inconvenience caused on this.

Please update the values of linkedDomains and dependsOn property under Microsoft.Communication/CommunicationService with the below

"[resourceId('Microsoft.Communication/emailServices/domains',concat(parameters('acsemailName'), '-email'),'AzureManagedDomain')]"

or update the entire block of Microsoft.Communication/CommunicationService in the above shared ARM template.

{ "type":"Microsoft.Communication/CommunicationServices", "apiVersion":"2022-07-01-preview", "name":"[concat(parameters('acsemailName'),'-cs')]", "location":"global", "tags":"[parameters('tagsByResource')]", "properties":{ "dataLocation":"[parameters('dataLocation')]", "linkedDomains":[ "[resourceId('Microsoft.Communication/emailServices/domains',concat(parameters('acsemailName'), '-email'),'AzureManagedDomain')]" ] }, "dependsOn":[ "[resourceId('Microsoft.Communication/emailServices/domains',concat(parameters('acsemailName'), '-email'),'AzureManagedDomain')]" ] }

and retry the deployment and let us know if you are facing the issue.
I have made the above suggested changes and able to deploy the ACS, ACS email service and provision managed domain without any issues.

Please refer to the sample output screenshot for your reference.

Feel free to reach back to me if you have any further questions on this.
wunderbar 20 Reputation points

2023-07-26T16:22:34.61+00:00

VenkateshDodda-MSFT, I've created a new azure account, new subscription and group, and deployed this ARM template there to eliminate account specific configuration issues. The result is absolutely the same:

Answer 1

VenkateshDodda-MSFT 25,111 Microsoft Employee Moderator

@wunderbar Thanks for your patience on this. I have tried deploying the above shared template and it has failed with the same error.

Upon checking the template further, we see that you are passing the data location parameter value as United States (containing Upper case), post passing the datalocation parameter value in lower case we are able to deploy the resources successfully.

I have checked with Azure communication Engineering team and sharing the below.

Our product team has identified a bug and they are actively working on it.

As a workaround, please try the deployment by modifying the Data Location name to be in lowercase, such as "unitedstates" or "canada.", the fix will be rolled out in a few days.

Feel free to reach back to me if you have any further questions on this.

wunderbar 20 Reputation points

2023-07-26T19:04:27.7166667+00:00

VenkateshDodda-MSFT, thanks a lot. That solved the issue.
VenkateshDodda-MSFT 25,111 Reputation points Microsoft Employee Moderator

2023-07-26T19:08:32.0166667+00:00

wunderbar Thanks for your swift response and Glad to know that your problem has resolved.

Share via

Azure communication/email service ARM deployment error with linkedDomains

0 additional answers

Your answer