public loadbalancer outbound rules showing 0 instance

Question

Hi all,

I am working on 1 solution where we have a development vm need to communicate to internet using public load balancer(SNAT) feature.
I configured everything and when I go to vm and do what's my ip it is not giving me public ip associated with public load balancer.
I checked in outbound rules backend is showing 0 instance whereas I assigned my vm in backend pool of load balancer.

Can you please help in figuring out where is the issue.

Answer 1

Hello @ankur datta , Thank you for your patience and apologies for the delay.

I recreated a similar scenario and I was able to connect to internet via my VM using my Public Load balancer's IP.

We will go through some configurations below to see if you have set them correctly.

• Since you are using SNAT to communicate with internet. Can you please confirm if you do not have any NAT gateway configured on your backend subnet?
  
• Can you please confirm if have the outbound rule set in your Load Balancer? this is outbound rule for the backend pool. Here the LoadBalancerFrontend represents my Loadbalancer Frontend IP, myBackendPool represents my backend pool which consists my VM. If this rule is missing, you can add it via portal or you can follow the documentation here to add it using powershell. Please retry the connectivity from your VM if you had to set this rule.

• Can you please confirm if your backend pool is up and running?

• When you click on your backend pool above? Do you see your VM listed in it as shown below.

• In your resource group, can you please validate the NSG associated with your VM and see if any rules are blocking this connectivity?

• If does not help can you please check if any firewall on your VM is blocking this connectivity?
• On Azure Portal on your VM's overview page do you see any Public IP. For me its my Load balancer's public IP . On the networking Tab of the VM in the Topology section you can see how your connectivity is established.

Hope this helps. Please let me know if you have any additional questions, I will be glad to continue with our discussion.

Answer 2

I had the same issue and it is because the BEP was configured with IP address instead of NIC.

When a backend pool is configured by IP address, it will behave as a Basic Load Balancer with default outbound enabled. For secure by default configuration and applications with demanding outbound needs, configure the backend pool by NIC.