<p>Right now, my production is using <a href="https://cloud.google.com/load-balancing/docs/negs" rel="nofollow noreferrer">Google Cloud Network Endpoint Group</a>
I am planning to use Multi-cluster spread into different Cloud Provider.</p>
<p>In Google Cloud, the flow is like <code>visitor -&gt; LB -&gt; NEG -&gt; Pod</code></p>
<p>I am curious, what is NEG called in Azure Cloud ? After reading azure docs, i don't find the similarity of NEG. Only <a href="https://learn.microsoft.com/en-us/azure/aks/static-ip" rel="nofollow noreferrer">Static IP Address LB</a> and <a href="https://learn.microsoft.com/en-us/azure/aks/load-balancer-standard" rel="nofollow noreferrer">Standard IP Address LB</a></p>
<p>In google cloud, the best practice is Network Endpoint Group. What is the best practice in Azure Cloud ?</p>

Nicky Puff
<p>I recommend to consider this method below to replace Google Cloud Load Balancer NEG, <a href="https://azure.github.io/application-gateway-kubernetes-ingress/" rel="nofollow noreferrer">https://azure.github.io/application-gateway-kubernetes-ingress/</a></p>
<p>or this one for fastest deployment <a href="https://learn.microsoft.com/en-us/azure/application-gateway/tutorial-ingress-controller-add-on-existing" rel="nofollow noreferrer">https://learn.microsoft.com/en-us/azure/application-gateway/tutorial-ingress-controller-add-on-existing</a></p>
