Azure vms are not able to fetch the Public IP address of the Public Load balancer

Naveen Neerukattu 26 Reputation points
2022-09-25T08:19:52.237+00:00

Hi Team,
I have created a Static Public Load balancer with Backed 2 vms.
The problem is the backend vms are not able to fetch the Public Ip address of the Load balancer.
Backend vms are having Private IPs but Public Ip showing as Empty.
Need help

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,254 questions
Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,197 questions
Azure Load Balancer
Azure Load Balancer
An Azure service that delivers high availability and network performance to applications.
408 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Jackson Martins 9,801 Reputation points MVP
    2022-09-25T10:37:23.1+00:00

    Hi @Naveen Neerukattu
    Can you post screenshots of the structure? Is your load balance standard?
    Make sure you are not using internal load balance, try to create a standard public ip and attach your vm's NIC.

    I have load balance scenarios with public ip in vm, below a print of a basic load balance with ip in VM

    244505-image.png

    244497-image.png

    1 person found this answer helpful.
    0 comments No comments

  2. KapilAnanth-MSFT 36,396 Reputation points Microsoft Employee
    2022-10-03T05:02:20.083+00:00

    Hi @Naveen Neerukattu ,

    Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.
    I understand that you are not able to see the Public IP address on the VM via Portal.

    I was scoping the following,

    • Are you using a Standard Public Load Balancer or a Basic one?
    • Have you configured the backend Pool with NIC or IP-Based?
    • Can you please make sure the VMs are in a running state while you check for Public IP?

    Post which, you have confirmed the issue has been resolved.

    Cheers,
    Kapil

    0 comments No comments