Cannot delete VNet — subnet blocked by orphaned App Service serviceAssociationLink

Aditya Sinha 25 Reputation points • Microsoft Employee

I'm trying to delete a virtual network, but it fails with:
InUseSubnetCannotBeDeleted: Subnet <subnet> is in use by .../serviceAssociationLinks/AppServiceLink and cannot be deleted.

The subnet was previously used for App Service / Function App regional VNet integration. The app has since been re-integrated with a different VNet, so nothing actively uses this subnet anymore. However, an orphaned serviceAssociationLink (AppServiceLink, owned by Microsoft.Web, with allowDelete: false) remains on the subnet and blocks deletion.

What I've already tried (all fail):

  1. Delete the whole VNet → InUseSubnetCannotBeDeleted (subnet in use by AppServiceLink).
  2. Delete the subnet → same InUseSubnetCannotBeDeleted error.
  3. Remove the subnet delegation (Microsoft.Web/serverFarms) → SubnetMissingRequiredDelegation, because the SAL requires the delegation to exist (circular lock — delegation can't go while the SAL is present).
  4. az webapp vnet-integration add then remove (point the app at the stale subnet, then disconnect) → App Service reuses the existing orphaned SAL rather than tearing it down (etag never changes), so it persists.

Questions:

Is there any supported customer-side way to remove an orphaned Microsoft.Web serviceAssociationLink (or flip allowDelete to true)?

If not, is a support request to the App Service team the only path to clear this stuck SAL?

Any guidance appreciated.

  1. Praneeth Maddali 10,460 Reputation points • Microsoft External Staff • Moderator

    Hi @Aditya Sinha

    Thanks for reaching us regarding your issue we have reached you through teams

Sign in to comment

Answer accepted by question author

Praneeth Maddali 10,460 Reputation points • Microsoft External Staff • Moderator

Hi @Aditya Sinha

Thank you for sharing the requested details over the Teams message.

The orphaned ServiceAreaLink has been successfully removed from the backend. We also appreciate your confirmation over Teams that the issue is now resolved.

Please feel free to reach out if you have any further queries—we’re happy to assist.

If you found this helpful, kindly click on “Accept the answer” and select “Yes”, as this can benefit other community members facing similar issues.

If you have any additional questions, feel free to post them in the “Comments” section, and I’ll be glad to help.

  1. Aditya Sinha 25 Reputation points • Microsoft Employee

    @Praneeth Maddali Thanks for the quick action, I really appreciate it.

Sign in to comment

0 additional answers

Sign in to answer

Your answer