LOW
Source
CloudSploit
ID
lb-no-instances

LB No Instances

Detects load balancers that have no backend instances attached

All load balancers should have backend server resources. Those without any are consuming costs without providing any functionality. Additionally, old load balancers with no instances pose a security concern if new instances are accidentally attached.

Follow the appropriate remediation steps below to resolve the issue.

  1. Log into the Microsoft Azure Management Console.

  2. In search bar at the top search for Load balancers and select “Load Balancers”. Step

  3. Select the “Load balancer” by clicking on the “Name” as a link which needs to be checked for active Instances.Step

  4. On the “Load balancer” page, scroll down the left navigation panel and choose the “Backend pools” option.

  5. On the “Backend pools” pane that opens, if there are no backend instances then we should delete it as a security best practice.

  6. In the left navigation panel click on “Overview” and click on “Delete” button at the top to delete the load balancer.

  7. In the confimation box that opens, click “Yes” to confirm deletion of this load balancer.

  8. Repeat step number 3 - 7 to check and delete old load balancers that no longer have backend resources.