Deployment Failed: A virtual network cannot be linked to multiple zones with overlapping namespaces

Question

I created a new Function App using an existing App Service plan with Inbound Private Endpoints and Outbound VNET Integration. During deployment on the ~11th step an error occurred;

A virtual network cannot be linked to multiple zones with overlapping namespaces. You tried to link virtual network with 'privatelink.azurewebsites.net' and 'privatelink.azurewebsites.net' zones.

It appears the App Function is "Running", but I've never had a deployment fail like this before.

1. What happens if I click the "Delete" button on the Deployment Overview page?
2. Is that the only step that failed and I can proceed and configure DNS as needed or did this halt some additional deployment steps?

Note when configuring inbound access, I had DNS setting set to Azure Private DNS Zone (Instead of Manual).

Answer 1

@vdidxho Thanks for reaching out. From the error message it looks like you are trying to assign multiple DNS zones for the same namespace to the single VNET. You cannot assign many DNS zones with the same namespace to the single VNET. The proper way of managing DNS zones it to have a single DNS zone namespace and assign it (link) to multiple VNETs.

1. What happens if I click the "Delete" button on the Deployment Overview page?
   If you click on delete button on deployment overview page the deployment record will get erased from the deployment history only but the resources deployed which are deployed successfully will remain under that subscription and resource group.
2. Is that the only step that failed and I can proceed and configure DNS as needed or did this halt some additional deployment steps?
   The resources which were created during the deployment will remain constant. Since the deployment got failed while creating the Microsoft.Network/privateDnsZones/virtualNetworkLinks and the next resources which are dependent on Virtual Network Links going to be deployed in that deployment will get failed and you can procced configuring DNS as needed manually.

Feel Free to reach back to me if you have any further questions on this.

Answer 2

This happened to me when adding a private endpoint to an App Service, but 1 domain existed before it started, and it was Azure that added the second and then complained there were two. Check the event history on the private DNS domains.

Answer 3

This happened to me when adding a private endpoint to an App Service, but 1 domain existed before it started, and it was Azure that added the second and then complained there were two. Check the event history on the private DNS domains.

Answer 4

I have this issue when I tried to create a new DNS zone with a virtual network link and the link is existing in another private DNS zone.