Share via

Unable to redeploy an Azure Communication Service resource after renaming the deployment

Martin Stewart 0 Reputation points
2024-05-09T09:46:27.7566667+00:00

I have successfully been able to deploy an Azure Communication Service resource via bicep to my subscription.

After renaming deployment in bicep, the deployment fails with the following error:

{"code":"InvalidResourceOperation","message":"Another 'PUT' operation on the same resource '/subscriptions/<REDACTED>/resourceGroups/<REDACTED>/providers/Microsoft.Communication/communicationServices/<REDACTED>' is active/in-progress. Multiple concurrent operations of the same type (ex: PUT) are disallowed for resource type communicationServices. Please wait for the previous operation to complete and try again."}

There doesn't seem to be anything I can do my end to fix this. Is this a Microsoft problem?

Azure Communication Services
Azure Communication Services
An Azure communication platform for deploying applications across devices and platforms.
705 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Gowtham CP 1,010 Reputation points
    2024-05-09T10:31:32.18+00:00

    Hello @Martin Stewart Thanks for posting your question on Microsoft Q&A.

    The error message you're seeing indicates a potential issue with Azure Communication Service resource management. Azure Communication Services doesn't allow concurrent modifications (PUT operations) while a previous deployment is ongoing. This means that if a deployment is still in progress, renaming it in your Bicep file will fail. To address this, you can either wait for the current deployment to finish, delete and redeploy the resource, or consider using ARM templates for more control over deployments. Additionally, you can report this behavior to Microsoft through the Azure portal or support channels for further investigation.

    If you found the solution helpful, consider accepting it.

  2. Gowtham CP 1,010 Reputation points
    2024-05-13T13:01:57.1966667+00:00

    Hello Martin Stewart ,

    Despite our initial efforts, you're still facing the "InvalidResourceOperation" error. This issue often arises when Azure Communication Services attempts to deploy a resource while it's stuck in the "Accepted" state from a prior deployment. To address this, I suggest allowing the ongoing deployment to fully complete before proceeding further. It's also wise to review the deployment history to identify any lingering deployments causing interference. If necessary, you may need to perform a cleanup of the resource group. Following that, you can retry the deployment, ensuring that the resource isn't still undergoing provisioning. Additionally, exploring options like Azure CLI or ARM templates could provide deeper insights into the underlying issue.

    If you found the solution helpful, consider accepting it.

    0 comments