CER-0292
This inefficiency occurs when Azure Load Balancers remain provisioned after the backend workloads they supported have been scaled down, stopped, or decommissioned. This is common in non-production environments where virtual machines are shut down outside business hours, but the associated load balancers are left in place. Even when no meaningful traffic is flowing, the load balancer continues to incur base charges, resulting in ongoing cost without delivering value.
Azure Load Balancer charges are driven by the provisioned load balancer and processed data, regardless of whether backend resources are actively serving traffic.
• Identify load balancers associated with non-production or intermittent environments
• Review whether backend pools are empty or reference stopped resources
• Assess whether load balancers continue to exist despite applications being inactive or retired
• Remove load balancers that are no longer required after backend workloads are stopped or decommissioned
• Recreate load balancers on demand for temporary or non-production use cases
• Incorporate load balancer cleanup into environment shutdown and decommissioning processes
