`Microsoft.Communication/emailServices@2021-10-01-preview` leads to conflict after first run

[hho]

Bicep version

➜ az bicep version
Bicep CLI version 0.9.1 (a2950a16df)

Describe the bug After deploying an email communication service, every subsequent deployment fails with {"status":"Failed","error":{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"BadRequest","message":"{\r\n \"error\": {\r\n \"code\": \"ResourceNameUnavailable\",\r\n \"message\": \"Specified resource name already in use\"\r\n }\r\n}"}]}}

To Reproduce Deploy the following template to a resource group:

param nameEmailService string
param nameCommService string
param domainName string = 'AzureManagedDomain'
param location string = 'global'
param dataLocation string = 'unitedstates'

var domainManagement = domainName != 'AzureManagedDomain' ? 'CustomerManaged' : 'AzureManaged'

resource emailCommunicationService 'Microsoft.Communication/emailServices@2021-10-01-preview' = {
  name: nameEmailService
  location: location
  properties: {
    dataLocation: dataLocation
  }

  resource emailDomain 'domains@2021-10-01-preview' = {
    name: domainName
    location: location
    properties: {
      domainManagement: domainManagement
      userEngagementTracking: 'Disabled'
      validSenderUsernames: {
        DoNotReply: 'DoNotReply'
      }
    }
  }
}

resource communicationService 'Microsoft.Communication/communicationServices@2021-10-01-preview' = {
  name: nameCommService
  location: location
  properties: {
    dataLocation: dataLocation
    linkedDomains: [
      emailCommunicationService::emailDomain.id
    ]
  }
}

Deploy with

az deployment group create --resource-group rg-foo-bar --template-file emailCommunicationService.bicep

• First time it works and creates the three resources.
• From the second time onwards, it always fails with the error from above.

Additional context

• Deployment log shows that Bicep is always trying to Create the resource, instead of being idempotent.
• The output of --what-if does not show the attempted creation and instead shows the expected Resource changes: 3 no change.

[slavizh]

+1