Hi Daniel Woodhouse,
Thanks for reaching out to Microsoft Q&A.
It seems like there might be some residual or orphaned resources left in azure after uninstalling the SQL extension and deleting the SQL instance. Based on the steps you’ve already taken, here are a few things you could try to resolve the issue:
- Check Azure Arc Resource Management:
- Go to the Azure Arc section in the Azure portal and see if the SQL Server resource is still being tracked under Azure Arc for SQL Servers.
- If it’s still present, try to disconnect or remove the Arc-enabled SQL Server resource from Azure Arc explicitly.
- Check for Resource Locks:
- Navigate to the Resource Group where the databases are appearing.
- Check if there are any locks on the resource group or specific resources (under Settings > Locks). These locks might be preventing the deletion.
- If locks exist, you’ll need to remove them before deleting the resources.
- Forcefully Remove Resources via Azure CLI or PowerShell:
- If the resources keep reappearing after deletion, try using Azure CLI or Azure PowerShell to forcefully delete them.
az resource delete --ids <resource-id> Remove-AzResource -ResourceId "<resource-id>" -Force
- Check Resource Explorer:
- In the Azure portal, navigate to Resource Explorer to investigate the status of the resources.
- Go to All services > Resource Explorer, find the resource that keeps reappearing, and inspect its details. You may be able to get a clearer view of the resource’s state and dependencies.
- Check Activity Logs:
- Go to the Activity Log of your Azure subscription and check for any automated operations that might be recreating the resources (such as a policy or automation script).
- Look for any clues related to why the resources are being recreated after deletion.
Please 'Upvote'(Thumbs-up) and 'Accept' as an answer if the reply was helpful. This will benefit other community members who face the same issue.