Azure front door not working with. private link service created by internal load balancer

akash warkhade 26 Reputation points

Hi all,

I have integrated private link service with internal load balancer and then integrate that private link service with front door service using below documentations :

I am able to connect to my service using its private ip within vnet as shown below :

bash-5.1# kubectl get svc my-service  
NAME                  TYPE           CLUSTER-IP   EXTERNAL-IP              PORT(S)                      AGE  
my-service         LoadBalancer    80:32462/TCP,443:32547/TCP   5d21h  
bash-5.1# curl  
404 page not found  
bash-5.1# curl  
request should have bearer token headers or internal headers. no token/api keys/ad ingest key /internal headers are found  

But same is not happening when integrated private link service with front door service
when i try to curl front door service url its giving error below :

akashwarkhade % curl -i
HTTP/2 502
cache-control: no-store
content-length: 952
content-type: text/html
x-azure-ref: 0EOJYYwAAAADxJmfOsrcfTKvLVwax/bsCQk9NMDJFREdFMDgxNwA2NzgxNzMzMi1mZTkzLTRiZDgtOThhYS1kNGQxNDllZmY5NzQ=
date: Wed, 26 Oct 2022 07:30:24 GMT

<h2>Our services aren't available right now</h2>
<p>We're working to restore all services as soon as possible. Please check back soon.</p>


(note : i have updated frontdoor name in curl request for security)

PFB images for private link and front door config :



Please let me know what might be wrong

Azure Front Door
Azure Front Door
An Azure service that provides a cloud content delivery network with threat protection.
614 questions
Azure Private Link
Azure Private Link
An Azure service that provides private connectivity from a virtual network to Azure platform as a service, customer-owned, or Microsoft partner services.
484 questions
Azure Load Balancer
Azure Load Balancer
An Azure service that delivers high availability and network performance to applications.
415 questions
{count} votes