Azure Health Data Services
An Azure offering that provides a suite of purpose-built technologies for protected health information in the cloud.
172 questions
Health Data Services Private Endpoint CNAME records missing
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 31%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMR%3C/text%3E%3C/svg%3E)
Maarten Rasenberg
0
Reputation points
Hi All,
We are having difficulties with connecting to our Health Data Services through a Private endpoint. All configuration is verified and via a VM using the hosts file, we can connect.
It seems that Azure DNS is not updated automatically as it should be; it resolves the public A record of the service instead of the CNAME to the privatelink.azurehealthcareapis.com address.
Searching the community, I've found a similar issue whit a different service: https://learn.microsoft.com/en-us/answers/questions/1258850/apim-private-endpoint-missing-dns-cname-alias
Is the Health Data Services service having the exact same issue of not updating the Azure DNS when creating a private endpoint?
Kind regards,
Maarten Rasenberg
Sign in to answer