An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
Logged in this morning and the stale VM link is gone. I've been able to proceed as business as usual.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I am trying to delete a virtual network and its subnet in East US, but the process is blocked because Azure reports a NIC as still in use by a VM that no longer exists from my perspective. The error indicates that the NIC is attached to a VM, but I have verified that the VM has been removed. I suspect this is a stale service-managed dependency.
Azure Virtual Network in East US, with a subnet and NIC in resource groups, involving a possibly service-managed NIC attached to a VM that no longer exists.
I attempted to delete the subnet and virtual network after deleting the associated VM. The deletion failed with an error indicating the subnet was still in use by a NIC. I also checked the NIC's provisioning state, which was Succeeded, and verified that the NIC still references the subnet and has a VM link, although the VM no longer exists. I reviewed documentation on NIC dependencies and attempted to delete the NIC directly, but Azure reports it as still in use by a VM resource, which does not seem to be present.
I am seeking guidance on how to remove the stale NIC attachment from Azure's perspective to enable subnet and VNet deletion. Specifically, how to identify and dissociate the NIC from the non-existent VM to resolve the dependency blockage.
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
Logged in this morning and the stale VM link is gone. I've been able to proceed as business as usual.