Here are some common scenarios in question:
- AzFW goes into failed state due to a Private DNS zone linked with the VNET which causes resolution failures.
- Private Endpoint creation where DNS zone fails to link to the vnet as another zone with the same name is already assigned.
- Trying to create vnet link in DNS zone and failing as there is another zone with the same name linked to the vnet.
Resolution:
You can leverage the below given PS script in order to find the zone names which have a link with the vnet in question:
Connect-AzAccount
Write-host"Here is a list of subscription available to you"Get-AzSubscription | format-table-property Subscriptionid, Name
$Subid= Read-Host"Enter the SubscriptionID you need to search the vnet link in"Connect-AzAccount -Subscription $subid$ResourceGroups= Get-AzResourceGroup
$ResourceGroupsNames= $ResourceGroups.ResourceGroupName
$VNETID=