An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
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:
- Verify that no resource from the linked service still uses the subnet.
- Wait 10–15 minutes for platform cleanup.
- Retry the subnet deletion.
- If the SAL persists, open an Azure support request and include the linkedResourceType.
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:
- Subscription ID
- Resource group, VNet, and subnet resource IDs
- Deleted MySQL server name and resource ID
- SAL name and complete JSON output
- Server deletion time and tracking/correlation ID
- The InUseSubnetCannotBeDeleted error
- Confirmation that no MySQL Flexible Server remains in the subnet
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:
- Troubleshoot VNet or subnet deletion failures
- Troubleshoot subnet deletion and modification failures
- Service Association Links REST API
- Create an Azure support request
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.