Explanation
Why the waste happens and who it affects.
When this happens, the load balancer continues to incur hourly charges despite serving no functional purpose. These inactive resources often go unnoticed, particularly in dev/test environments or when deployment pipelines fail to include proper cleanup logic. Over time, the accumulation of unused load balancers contributes to unnecessary recurring costs with no operational benefit.
Billing model
The pricing dimensions that drive this cost.
Azure Load Balancer (Standard SKU) is billed based on:
- Rule-based hourly charge
- A flat hourly rate for the first 5 configured load-balancing and outbound rules, plus an hourly rate per additional rule (inbound NAT rules are free); billed continuously, regardless of backend activity
- Data processing charges
- Billed per GB, if traffic is present
As long as at least one load-balancing or outbound rule is configured, cost persists even when there are no active backend pool members and no traffic is flowing. A Standard Load Balancer with no rules configured has no hourly charge.
How to detect
5 checks to find it in your estate.
- Identify Azure Load Balancers with empty backend address pools
- Confirm the load balancer has one or more load-balancing or outbound rules configured, since a load balancer with no rules has no hourly charge
- Verify that there are no associated virtual machines or scale sets
- Check network traffic metrics to confirm zero inbound or outbound flow
- Cross-reference with naming conventions or tags to flag decommissioned environments
How to fix
3 ways to remove the waste.
- Delete Azure Load Balancers that have no backend pool members and no observed traffic
- Implement automation or tagging policies to detect and flag inactive networking resources
- Update infrastructure-as-code or deployment scripts to ensure load balancers are removed alongside their dependent compute resources
Documentation
Vendor references for pricing and configuration.