This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(268.8, 47%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETJ%3C/text%3E%3C/svg%3E)
The first run deploying communication services using the Bicep file below succeeds. However when deploying a second time the deployment fails due to an InvalidResourceOperation error. Could anyone tell me how to solve this issue?
When removing the resources and rerunning deployment resources are successfully created.
{
"code": "DeploymentFailed",
"target": "/subscriptions/711699cf-05b7-4ec1-948b-65637bfb0de0/resourceGroups/sso-dev/providers/Microsoft.Resources/deployments/nexusCommunications-20230613.3",
"message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.",
"details": [
{
"code": "InvalidResourceOperation",
"message": "The operation for resource '/subscriptions/711699cf-05b7-4ec1-948b-65637bfb0de0/resourceGroups/sso-dev/providers/Microsoft.Communication/communicationServices/coms-hsks-nxs-dev-we' is invalid as it is being provisioned with state: 'Accepted'."
}
]
}
// https://learn.microsoft.com/en-us/azure/templates/microsoft.communication/communicationservices?pivots=deployment-language-bicep
// https://learn.microsoft.com/en-us/azure/templates/microsoft.communication/emailservices?pivots=deployment-language-bicep
param communicationsName string
param communicationsEmailName string
param domainUsername string
param domainDisplayName string
resource communicationsEmail 'Microsoft.Communication/emailServices@2023-03-01-preview' = {
name: communicationsEmailName
location: 'global'
tags: {}
properties: {
dataLocation: 'Europe'
}
}
resource communicationsEmailDomain 'Microsoft.Communication/emailServices/domains@2023-03-01-preview' = {
name: 'AzureManagedDomain'
location: 'global'
parent: communicationsEmail
properties: {
domainManagement: 'AzureManaged'
userEngagementTracking: 'Disabled'
}
}
resource communicationsEmailDomainSendUsername 'Microsoft.Communication/emailServices/domains/senderUsernames@2023-03-01-preview' = {
name: domainUsername
parent: communicationsEmailDomain
properties: {
displayName: domainDisplayName
username: domainUsername
}
}
resource communications 'Microsoft.Communication/communicationServices@2023-03-01-preview' = {
name: communicationsName
location: 'global'
tags: {}
properties: {
dataLocation: 'Europe'
linkedDomains: [
communicationsEmailDomain.id
]
}
}
// Determine our connection string
var communicationsConnectionString = listKeys(communications.id, communications.apiVersion).primaryConnectionString
// Output our variables
output communicationsConnectionString string = communicationsConnectionString
output communicationsEmailDomainName string = communicationsEmailDomain.name
weirdly enough that actually worked, thanks!
Try changing the name to someting else seems like some previous deployment
coms-hsks-nxs-dev-weu
Glad that it worked! Tim Joosten - The reason behind this is the resource name was in accepted state from previous deployment (maybe cancelled one) if you give it some time and re-try this will work.
Please "Accept as answer" so it will be helpful for others :)
![](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(28.799999999999997, 86%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJN%3C/text%3E%3C/svg%3E)
I have almost the same issue, but I want to keep the same resource name - the resource has been stuck as "accepted" for well over a week at this point (and this seems to keep happening with azure communication service deployments (we're using ARM templates not bicep files, but same result)).
Is there any way to "force" the service out of the stuck accepted state?
![](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(121.6, 18%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVD%3C/text%3E%3C/svg%3E)
Still having the same issue. The same resource name and i also let it be provisioned for a week. I cannot run any terraform plan either now, even when removing from tf code. Not sure what the solution is other than recreating the resource or removing it from the state
For me the solution was contacting support and then they "did things" behind the scenes to shunt the resource out of the "Accepted" state and back into a "Failed" state.
Then re-deployments worked again.
![](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, 73%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBH%3C/text%3E%3C/svg%3E)
I am getting this same error in our CD pipeline while deploying to one particular environment (UAT) while for the other env (Dev, QA) it worked fine. Any solution for this?