# Suboptimal Load Balancer rule configuration in Azure Standard Load Balancer Canonical: 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... By: Jurian van Hoorn Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Suboptimal Load Balancer Rule Configuration in Azure Standard Load Balancer The short version 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. [Jurian van Hoorn](https://www.linkedin.com/in/j-hoorn/) Operations Senior (Azure Cloud) @ Netcompany 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-0223 Type Inefficient Configuration ## Explanation Why the waste happens and who it affects. Specifically, each load balancing rule-both inbound and outbound-can contribute to ongoing charges. In applications that historically relied only on Basic load balancers, outbound rules may never have been configured, meaning their inclusion post-migration could be unnecessary. This inefficiency tends to emerge in larger Azure estates where infrastructure-as-code or templated environments create load balancers in bulk, often replicating rules without review. Over time, dozens or hundreds of unused or outdated rules can accumulate, inflating network costs with no operational benefit. ## Billing model The pricing dimensions that drive this cost. Azure Standard Load Balancer charges a flat hourly rate covering the first five load-balancing and outbound rules, plus an hourly charge for each additional rule, plus a per-GB charge for data processed. Inbound NAT rules are free, and a Standard Load Balancer with no rules configured has no hourly charge. Unlike the retired Basic tier (which had no per-rule charges), the Standard tier's billing is tied directly to the number of rules. This makes it important to assess the necessity of each rule, especially in environments with many load balancers or frequent replication across dev, QA, and staging. ## How to detect 6 checks to find it in your estate. - Identify Standard Load Balancers with more than five load-balancing and outbound rules combined (exclude inbound NAT rules, which are free) - Review whether inbound and outbound rules are actively used by the application - Check for templated or duplicated rules across non-production environments - Determine whether rules were carried over from legacy Basic-tier load balancers - Confirm with application teams whether each rule is still required - Review load balancer configurations in environments that have recently been migrated or cloned ## How to fix 4 ways to remove the waste. - Audit existing Standard Load Balancer rule sets to identify unused entries - Remove unnecessary inbound and outbound rules, especially in non-production environments - Avoid blanket rule creation in templated environments unless explicitly required - Coordinate with application owners before removing rules to avoid disruption ## Documentation Vendor references for pricing and configuration. - [Load Balancer pricing azure.microsoft.com](https://azure.microsoft.com/en-us/pricing/details/load-balancer/) - [Azure Load Balancer Components Overview learn.microsoft.com](https://learn.microsoft.com/en-us/azure/load-balancer/components) - [Outbound Rules for Azure Load Balancer learn.microsoft.com](https://learn.microsoft.com/en-us/azure/load-balancer/outbound-rules) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - Azure Load Balancer CER-0292 ### [Idle Azure Load Balancers in Non-Production Environments](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. This is common in non-production environments where virtual machines are shut down outside business... Networking - 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 Databricks CER-0068 ### [Inefficient Private Link Routing to Azure Databricks](https://www.pointfive.co/efficiency-hub/inefficiencies/inefficient-private-link-routing-to-azure-databricks) In Azure Databricks environments that rely on Private Link for secure networking, it's common to route traffic through multi-tiered network architectures. This often includes multiple VNets, Private Link endpoints, or peered subscriptions... Networking --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.