This might happen because of our method for naming resources.
Our 'Azure Dev' authored templates allow for configuring the name of the resource. To do so, you can add an entry to the main.parameters.json in the infra folder. For example:
"webServiceName": {
"value": "my-unique-name"
}
This entry creates a new resource named "my-unique-name" instead of a randomized value such as "app-web-aj84u2adj" the next time you provision your application. You can either manually remove the old resource group using the Azure Portal or run azd down to remove all previous deployments. After removing the resources, run azd provision to create them again with the new name.
This name will need to be globally unique, otherwise you will receive an ARM error during azd provision when it tries to create the resource.