You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The ESLZ policy initiative defines "azureAcrDataPrivateDnsZoneId": "{regionName}.data.privatelink.azurecr.io" in the "dnsZoneNames" parameter, but then is not used.
In fact is not needed, because the zone "{regionName}.data.privatelink.azurecr.io" is a subzone of "privatelink.azurecr.io" already addressed properly by "azureAcrPrivateDnsZoneId".
Steps to reproduce
Create ACR with private Endpoint
The PE contains both entries for "privatelink.azurecr.io" and "{regionName}.data.privatelink.azurecr.io", just with "azureAcrPrivateDnsZoneId", without "azureAcrDataPrivateDnsZoneId".