# Idle Azure Load Balancers in non-production environments Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/idle-azure-lb-in-non-prod-env Azure Load Balancers remain provisioned after the backend workloads they supported have been scaled down, stopped, or decommissioned. By: Taylor Houck Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Idle Azure Load Balancers in Non-Production Environments The short version Azure Load Balancers remain provisioned after the backend workloads they supported have been scaled down, stopped, or decommissioned. [Taylor Houck](https://www.linkedin.com/in/twhouck/) Cloud FinOps Specialist @ PointFive Azure service [Azure Load Balancer](https://www.pointfive.co/efficiency-hub/cloud-services/azure-load-balancer) Category [Networking](https://www.pointfive.co/efficiency-hub/service-category/networking) Reference CER-0292 Type Idle or Unused Resource ## Explanation Why the waste happens and who it affects. 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, a load balancer that still has rules configured continues to incur hourly rule charges, resulting in ongoing cost without delivering value. ## Billing model The pricing dimensions that drive this cost. Azure Standard Load Balancer is billed per hour based on the number of configured load-balancing and outbound rules (the first 5 rules at one rate, plus a per-rule charge for each additional rule), and per GB of data processed. There is no hourly charge when no rules are configured, so an idle load balancer that still has rules keeps accruing the rule-based hourly charge even when its backends are stopped and little traffic flows. ## How to detect How to find it in your estate. - Identify load balancers associated with non-production or intermittent environments - Review whether backend pools are empty or reference stopped resources - Check how many load-balancing and outbound rules each idle load balancer still has configured, since configured rules drive the hourly charge - Assess whether load balancers continue to exist despite applications being inactive or retired ## How to fix How to remove the waste. - 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 ## Documentation Vendor references for pricing and configuration. - [Pricing - Load Balancer azure.microsoft.com](https://azure.microsoft.com/en-us/pricing/details/load-balancer/) - [What is Azure Load Balancer? learn.microsoft.com](https://learn.microsoft.com/en-us/azure/load-balancer/load-balancer-overview) - [Azure Load Balancer SKUs learn.microsoft.com](https://learn.microsoft.com/en-us/azure/load-balancer/skus) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - Azure Load Balancer CER-0269 ### [Inactive Azure Load Balancer](https://www.pointfive.co/efficiency-hub/inefficiencies/inactive-azure-load-balancer) In dynamic environments - especially during autoscaling, testing, or infrastructure changes - it's common for load balancers to remain provisioned after their backend resources have been decommissioned. When this happens, the load balancer... Networking - Azure Load Balancer CER-0223 ### [Suboptimal Load Balancer Rule Configuration in Azure Standard Load Balancer](https://www.pointfive.co/efficiency-hub/inefficiencies/suboptimal-load-balancer-rule-configuration-in-azure-standard-load-balancer) As organizations migrate from the Basic to the Standard tier of Azure Load Balancer (driven by Microsoft's retirement of the Basic tier), they may unknowingly inherit cost structures they didn't previously face. Specifically, each load... Networking - Azure NAT Gateway CER-0319 ### [Idle Azure NAT Gateway Attached to Subnet Without Active Workloads](https://www.pointfive.co/efficiency-hub/inefficiencies/idle-azure-nat-gateway-attached-to-subnet-without-active-workloads) Azure NAT Gateways are commonly deployed to provide outbound internet connectivity for resources within virtual network subnets. Over time, the workloads that originally required this outbound access may be scaled down, migrated, or... Networking --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.