Details of the scenario you tried and the problem that is occurring
The built-in policy "Deploy - Configure IoT Central to use private DNS zones" (d627d7c6-ded5-481a-8f2e-7e16b1e6faf6) only implements one zone parameter, but IoT Central private endpoints register in four different zones.
The use of the policy leaves the private endpoint incomplete, as shown below.
Verbose logs showing the problem
Suggested solution to the issue
Implement four private DNS zone parameters to cover all required zones:
privatelink.azureiotcentral.com
privatelink.azure-devices.net
privatelink.servicebus.windows.net
privatelink.azure-devices-provisioning.net
If policy is Guest Configuration - details about target node
Details of the scenario you tried and the problem that is occurring
The built-in policy "Deploy - Configure IoT Central to use private DNS zones" (d627d7c6-ded5-481a-8f2e-7e16b1e6faf6) only implements one zone parameter, but IoT Central private endpoints register in four different zones.
The use of the policy leaves the private endpoint incomplete, as shown below.
Verbose logs showing the problem
Suggested solution to the issue
Implement four private DNS zone parameters to cover all required zones:
If policy is Guest Configuration - details about target node