Hi @Mitch Abel,
Is there no way to detach these resources?
As there is no way to detach or delete a resource stuck in the Provisioning state, only the support team can access and remove such resources.
If the subnet remains locked even after deleting the application gateway and waiting, check the subnet status using the cmdlet below. It will display the current state. If the resource has failed in the 'Provisioning' state, only the support team can delete it.
az network vnet subnet show -g MyResourceGroup -n MySubnet --vnet-name MyVNet
az resource show
Reference: az resource show
To prevent this from happening again, ensure that resources are properly managed and cleaned up after deployments. Always check for any dependencies or connected devices before deleting a resource to avoid such conflicts.
I hope this helps to resolve your issue. Please feel free to ask any questions if the solution provided isn't helpful.
If this answer helped you, please don’t forget to upvote and mark it as accepted to help others in the community.