A private endpoint assigns a private IP in a virtual network for supported Azure services. Private DNS ensures the service’s normal hostname resolves to that private address from networks that should use the endpoint.
Overview
Connect Azure PaaS services through private endpoints, configure private DNS zones and troubleshoot name resolution and network reachability.
Implementation guide
- Confirm the target service supports private endpoints and review the required subnet and network policies.
- Create the private endpoint in the intended virtual network and approve the connection where required.
- Create or link the appropriate private DNS zone and configure the service’s DNS zone group integration.
- Test DNS resolution from a VM or workload in the connected network and verify the hostname resolves to the private IP.
- Validate routing, NSGs, firewalls and on-premises DNS forwarding for hybrid networks.
Code example
# Example: create a private DNS zone for a Storage Blob endpoint
az network private-dns zone create \
--resource-group <resource-group> \
--name privatelink.blob.core.windows.net
# Link the zone to a virtual network
az network private-dns link vnet create \
--resource-group <resource-group> \
--zone-name privatelink.blob.core.windows.net \
--name storage-private-link \
--virtual-network <vnet-resource-id> \
--registration-enabled false
Common pitfalls
- Do not assume a private endpoint alone configures DNS correctly.
- Do not test only from the Azure portal; test from the actual client network.
- Avoid overlapping private DNS zones or incorrect links that return unexpected addresses.
Conclusion
Use the documented platform behaviour as the contract, validate the design with realistic traffic and failure scenarios, and keep operational configuration under version control where appropriate.