An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
I accidentally posted the same question twice. Please consider one of the posts a duplicate.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello,
I deleted an Azure Database for MySQL Flexible Server that was using private access on a delegated subnet. The server has been deleted, but its service association link (SAL) remains and prevents deletion of the virtual network and resource group.
The resource group deletion fails with:
InUseSubnetCannotBeDeleted: Subnet webcrudDbSubnet is in use by a serviceAssociationLink and cannot be deleted.
The subnet is:
Listing the subnet's service association links through the Microsoft.Network REST API returns:
The MySQL Flexible Server has been deleted for more than 20 minutes. Removing the subnet delegation in the portal also fails: Azure reports that the subnet still needs the MySQL delegation to reference the SAL.
Is there a supported customer-side procedure to clean up this orphaned MySQL Flexible Server SAL? Or does it require backend cleanup by Microsoft? I do not have a paid Azure technical support plan. If possible, could a Microsoft moderator advise whether one-time assistance is available?
I have not tried to delete the SAL directly because allowDelete is false.
I can provide the subscription ID and the Azure deletion tracking ID privately if needed.
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
I accidentally posted the same question twice. Please consider one of the posts a duplicate.
Thanks for clarifying. I understand that a technical support request requires a paid plan, quoted at approximately CHF 100. I’d prefer not to purchase a monthly plan solely for this issue, so I’d first like to explore any supported alternatives.
Is there a customer-side workaround I can try, such as restoring or recreating the MySQL Flexible Server and then deleting it cleanly, or another supported cleanup procedure? I’m also open to any other reasonable steps you recommend. If backend cleanup is the only option, could a Microsoft moderator advise whether a one-time escalation is possible without a paid plan?
The orphaned link has allowDelete: false and linkedResourceType: Microsoft.DBforMySQL/flexibleServers. It blocks deletion of subnet webcrudDbSubnet in VNet webcrudVnet (rg_csr_webcrud). I can provide the subscription ID and deletion tracking ID privately if needed.
Hello @Grégoire Boisnard
Because the MySQL Flexible Server has already been deleted and the remaining SAL reports linkedResourceType: Microsoft.DBforMySQL/flexibleServers with allowDelete: false, this appears to be an orphaned platform-managed association rather than an active subnet dependency.
Microsoft’s documented procedure is:
You can run this Azure CLI command to confirm all subnet dependencies:
az network vnet subnet show \
--resource-group rg_csr_webcrud \
--vnet-name webcrudVnet \
--name webcrudDbSubnet \
--query "{delegations:delegations[].serviceName,ipConfigurations:ipConfigurations[].id,privateEndpoints:privateEndpoints[].id,serviceAssociationLinks:serviceAssociationLinks[].{name:name,linkedResourceType:linkedResourceType,allowDelete:allowDelete}}" \
--output json
If the only remaining dependency is that MySQL SAL, don’t remove the subnet delegation first; the delegation error is a consequence of the SAL still being present.
Also, don’t attempt to delete the SAL through an undocumented REST path. The current general-purpose Virtual Network REST documentation exposes only the List operation for service association links, and allowDelete: false explicitly indicates that the resource cannot be deleted through the normal resource operation. Microsoft documents customer-side removal commands for certain services such as Azure Container Instances, but not for Microsoft.DBforMySQL/flexibleServers.
Since the link has already remained beyond the documented cleanup interval, Microsoft backend cleanup is the supported next step. In the Azure portal, open:
Help + support > Create a support request
Select the affected subscription and resource, then include:
Keep the subscription ID and tracking information out of the public thread.
Technical support normally requires a support plan; free subscription-management support covers billing, quota adjustments, and account transfers. The portal may still offer automated diagnostics or another applicable support path.
A Microsoft moderator may offer a private escalation route, but that is discretionary and shouldn’t be treated as a documented entitlement.
References:
Help make this community better for everyone: If this answer helped or resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution. Thank you.