Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
7,429 questions
Multiple resource group found
![](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(272, 52%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPM%3C/text%3E%3C/svg%3E)
Pavel Makul
0
Reputation points
We faced a strange issue during deploying our API to Azure AppService resource. Deploy yaml pipeline includes AzureAppServiceManageV0 task run and it is precisely this task that has begun to fail recently. We continue getting "Multiple resource group found for App Service 'our-api-name'" error message. But on Azure Portal for current subscription we have exactly single 'our-api-name' resource. Could you please explain what went wrong? Just for info we decided to check how many resources we have with name 'our-api-name' using Azure CLI in cmd with command 'az resource list --name our-api-name --resource-type Microsoft.Web/sites'. And Azure CLI shows that we have two resources in the same group, but it should be impossible, on Azure Portal for current subscription we see exactly single resource.
{count} votes
-
Grmacjon-MSFT 17,456 Reputation points2024-07-19T19:56:10.8533333+00:00 Hello @Pavel Makul there a few possible causes for this scenario:
- It's possible that you previously had another resource named "our-api-name" that was deleted but not fully purged from ARM. These "soft-deleted" resources can sometimes cause conflicts during deployment.
- There might be an inconsistency within the resource group where your "our-api-name" App Service resides. This could be due to manual configuration errors or unexpected resource creation.
Here are a few ways to troubleshoot the issue:
- Check Azure Resource Explorer:
- Access the Azure Resource Explorer (https://azure.microsoft.com/en-us/blog/azure-resource-explorer-a-new-tool-to-discover-the-azure-api/).
- Search for "your-api-name" and filter by resource type "Microsoft.Web/sites". This can reveal hidden or soft-deleted resources causing the conflict.
- Verify Resource Group:
- In the Azure portal, navigate to the resource group containing your "your-api-name" App Service.
- Double-check there are no duplicate App Services with the same name within this group.
- Clean Up Soft-Deleted Resources:
- If the Azure Resource Explorer reveals a soft-deleted resource, you can attempt to permanently delete it using the Azure CLI command:
Replaceaz resource delete --id {resource-id} --force-deletion{resource-id}with the ID of the soft-deleted resource. - Check for any locks or slots: Make sure there are no locks added to the App Service Plan and Resource group. Also, if your app has been configured with multiple slots, ensure that the slots are deleted before deleting the web app.
Hope that helps.
-Grace
-
Pavel Makul 0 Reputation points
2024-07-30T23:24:44.3433333+00:00 Thanks a lot for your help @Grmacjon-MSFT . But seems like even 'force-deletion' didn't help. 'resource delete' command I tried before and now, but nothing happened when it called. Anyway we migrate our resources to another subscription (for other reason) and I hope that we will not face this issue in future;)
-
Pavel Makul 0 Reputation points
2024-07-30T23:25:57.4733333+00:00 Thanks a lot for your help @Grmacjon-MSFT . But seems like even 'force-deletion' didn't help. 'resource delete' command I tried before and now, but nothing happened when it called. Anyway we migrate our resources to another subscription (for other reason) and I hope that we will not face this issue in future;)
Sign in to comment