An Azure network security service that is used to protect Azure Virtual Network resources.
Hello Varsha Jain,
Thank you for the clarification.
Based on the details you’ve shared, this behavior typically indicates that the AzureFirewallSubnet is still associated with a dependent resource that exists outside your current subscription.
Even though you don’t have access to that subscription, Azure continues to treat the subnet as “in use” because it is referenced by another resource (for example, Azure Firewall, Private Endpoint, or a service integration). As a result, the platform prevents deletion of the subnet.
What this means
- The dependency is likely cross-subscription or part of a shared networking setup.
- The blocking resource is not visible or manageable from your subscription.
- In some cases, this could also be due to a Service Association Link (SAL) or an orphaned backend reference created by another Azure service.
Recommended action
Since the dependent resource exists outside your scope, the issue cannot be resolved directly from your end.
You may proceed with one of the following:
Reach out to the owning team of the other subscription
- Request them to remove or detach the resource that is using the subnet.
Azure enforces that all resources using a subnet must be removed before the subnet (and associated resources like Azure Firewall) can be deleted. When those dependencies exist in another subscription, manual cleanup is not possible from your side.
If this answers your question, feel free to click**“Upvote”**, which may help other community members facing similar scenarios.