Azure Load Balancer Pricing: Rules and Data Costs Azure Load Balancer distributes TCP and UDP traffic across backend resources. Creating one is the easy part. Predicting the bill is harder, because the charge depends on the SKU, the number of configured rules, the data processed, and a pile of neighboring resources.

Teams often budget for the Load Balancer line alone. Then public IPs, bandwidth, cross-region transfer, and monitoring show up on the invoice. This guide covers current US pricing, how rules and data are billed, what causes surprise charges, and how to build an estimate you can defend.

Key Takeaways

  • Basic retired September 30, 2025, so Standard and Gateway are the current SKUs.
  • Rule hours and processed GB are separate meters, billed independently.
  • Inbound NAT rules are free; other rules count toward the billed total.
  • IPs, egress, peering, and monitoring sit outside the Load Balancer meters.

How Much Does Azure Load Balancer Cost? (Pricing Overview)

There is no single price. The cost depends on SKU, region, rule count, and traffic. The rates below come from Microsoft's Load Balancer pricing page for East US in USD. The page shows no last-updated date, so confirm them before you budget.

SKU / tier Meter Rate
Standard (Regional or Global) First 5 rules, grouped $0.025/hour
Standard (either tier) Each additional rule $0.01/rule/hour
Standard (either tier) Inbound NAT rules Free
Standard, Regional Data processed $0.005/GB
Standard, Global Data processed No additional charge for Global-to-Regional packets
Gateway Gateway hour $0.013/hour
Gateway Chain hour $0.01/hour
Gateway Data processed $0.004/GB

Microsoft bills on consumption, and a partial hour counts as a full hour. A Standard load balancer with no rules configured has no hourly charge. Microsoft doesn't state a minimum GB rounding or a fixed monthly hour count, so check the calculator's assumptions.

Common Pricing Mistakes

  • Budgeting only for the Load Balancer and skipping public IP, bandwidth, and monitoring.
  • Assuming more backend VMs raises the Load Balancer price. The meters are rules and data, not backend count.
  • Reusing old Basic pricing. The calculator may still show Basic as free, but the retirement guidance takes precedence.

Three Illustrative Scenarios

These use the rates above. Figures use 730 hours per month, a common estimate rather than a Microsoft-stated figure.

Dev/test, Standard Regional: 3 rules, 50 GB processed.

  • Rules: 730 × $0.025 = $18.25
  • Data: 50 × $0.005 = $0.25
  • Total: about $18.50

Production regional: 8 rules, 2 TB (2,000 GB) processed.

  • First 5 rules: $18.25
  • 3 extra rules: 3 × $0.01 × 730 = $21.90
  • Data: 2,000 × $0.005 = $10.00
  • Total: about $50.15

High-throughput: 12 rules, 100 TB (100,000 GB) processed.

  • First 5 rules: $18.25
  • 7 extra rules: 7 × $0.01 × 730 = $51.10
  • Data: 100,000 × $0.005 = $500.00
  • Total: about $569.35

At scale, processed data dominates the Load Balancer charge. Transfer charges can then exceed it.

Azure Load Balancer pricing scenarios comparing rules and data costs

These figures exclude VMs or scale sets, public IPs, NAT, Azure Monitor, Azure Firewall, Application Gateway, Traffic Manager, cross-region transfer, internet egress, and support plans. Confirm every number against current rates before you budget.

Azure Load Balancer Pricing Factors and Cost Breakdown

Treat the bill as several independent components, not one flat fee.

SKU and Load Balancer Type

SKU Scale SLA Zones
Basic (retired) 300 IP configs per pool None Unsupported
Standard 5,000 per backend pool 99.99% Zonal or zone-redundant
Gateway Standard limits; 100 chained consumers per frontend Not specified Not specified

Gateway Load Balancer handles transparent insertion and scaling of third-party network virtual appliances, with a private-only frontend. It's a different function, not a cheaper Standard.

Keep Load Balancer separate from other services:

  • Application Gateway: capacity units and processing
  • Traffic Manager: DNS queries and monitored endpoints
  • Front Door: base fees, requests, and data transfer
  • Azure Firewall: deployment and data processing

Rules: Load-Balancing, Inbound NAT, Outbound, and HA Ports

Rule type What it does Billing
Load-balancing Maps a frontend IP/port to multiple backends Counts toward the rule total
Inbound NAT Forwards to one specific backend instance Free
Outbound Defines outbound NAT for the backend pool Counted with load-balancing rules
HA ports One internal rule spanning all TCP/UDP ports One rule; no separate tariff listed

The first five rules are one charged group, not five free rules per type. Unused or duplicate rules inflate the count and muddy cost attribution. Microsoft's Well-Architected guidance recommends consolidating rules.

Data Processed

Microsoft defines it as data processed inbound and outbound, independent of rules. Traffic path matters. In a same-VNet internal setup, inbound traffic is processed, while return traffic from backend to source bypasses the load balancer without charge.

Calculation: average GB per hour × monthly hours × $0.005. Or simply monthly GB × $0.005.

Keep this apart from other transfer charges:

  • Internet egress: first 100 GB/month free, billed separately from processed GB.
  • Inter-region transfer: $0.02/GB within North America, $0.05/GB from North America to other continents.
  • VNet peering: $0.01/GB inbound and $0.01/GB outbound in the same region.
  • Inter-availability-zone transfer: free as of February 12, 2025.

Azure networking transfer charges and Load Balancer data costs comparison

Related Networking and Infrastructure Charges

  • Standard static public IPv4: $0.005/hour; Global: $0.01/hour. Charges continue until deletion.
  • Backend VMs and scale sets, billed on their own meters.
  • Azure Monitor: exporting LoadBalancerHealthEvent to ALBHealthEvent is chargeable, plus Log Analytics ingestion and retention.
  • NAT Gateway, which takes precedence for new outbound connections and avoids SNAT port-exhaustion limits.

Health probes originate from 168.63.129.16. Whether probe traffic is billed is not clearly documented, so confirm on your Azure bill or with Microsoft support before assuming either way.

Region, Zones, and Ongoing Cost

Model each region and major traffic path separately. Don't apply one rate everywhere.

Review processed data, rule usage, and unexpected outbound traffic monthly, and compare against Azure Cost Management actuals. Engineering time and overprovisioned backends belong in total cost of ownership even though they never appear on the Load Balancer line.

Low-Cost vs Higher-Cost Azure Load Balancer Options: What's the Difference?

Choose by workload fit, not by the lowest base charge.

Feature and Resilience Profile

  • Lower cost: Fits only if the workload tolerates the limits. Basic is gone, so "cheap" now means a Standard with few rules and little traffic.
  • Higher cost: Justified by zone redundancy, the 99.99% SLA, HA ports, declarative outbound rules, and Global tier cross-region balancing.

Traffic and Data Economics

A small rule set still produces a large bill if data volume is high. In the high-throughput scenario above, data cost roughly 9 times the rule cost. Meanwhile, a pricier architecture can pay for itself through lower downtime risk and better backend utilization.

Best-Fit Use Cases

  • Dev, test, limited regional workloads: a few Standard rules, minimal data.
  • Production, zone-aware, multi-tier, enterprise: more rules, zones, possibly Global tier.
  • Network appliance chaining: Gateway, with its own three meters.

Azure Load Balancer SKU use cases and cost profiles comparison

No SKU is universally free. Standard's no-rules exemption does not waive processing charges.

How to Estimate and Reduce Azure Load Balancer Costs

Start with traffic patterns and availability needs, not a generic monthly figure.

Build a Workload Inventory

Record:

  • Regions, SKU, and number of frontends
  • Rules by category
  • Backend resources and operating hours
  • Average and peak processed data, and traffic direction
  • Internet or cross-region exposure
  • Adjacent services: NAT, Application Gateway, Traffic Manager, Front Door, Firewall, logging

Calculate and Validate

Use the Azure pricing calculator and calculate each meter separately. Record the date and assumptions.

After deployment, compare to actuals in Cost Management using:

  • Tags, including inherited tags, to group costs
  • Budgets and alerts (actual or forecast), which don't stop consumption
  • Scheduled daily or monthly exports to Azure Storage in CSV or Parquet

Azure Monitor metrics such as ByteCount, PacketCount, and SnatConnectionCount help you track real usage against your forecast.

Reduce Avoidable Charges

  • Remove unused frontends and obsolete rules.
  • Consolidate rules where architecture allows.
  • Place communicating VMs in the same VNet: transfer is free, though processing still applies.
  • Avoid extra regions or paid services without a clear availability need.
  • Review caching, private connectivity, and data paths with security teams before changing them.

Five ways to reduce avoidable Azure Load Balancer charges

Review the Whole Bill

Optimizing the Load Balancer line alone misses most of the spend. Include VMs, public IPs, NAT, monitoring, firewall, and transfer.

For enterprise FinOps teams, Lucidity covers one adjacent piece: its AutoScaler and free Assessment tool give visibility and optimization for Azure block-storage spend (disks), with stated reductions of up to 70%. It doesn't replace Microsoft's calculator or manage Load Balancer billing rules.

What Most Teams Miss

  • Ignoring bandwidth, cross-region, public IP, and monitoring costs.
  • Assuming every rule, probe, or backend is billed the same way.
  • Assuming reservations apply. Load Balancer isn't on Microsoft's reservation or savings plan eligible lists, so the model is consumption-based.
  • Not revisiting the estimate when traffic, regions, or frontends change.

Conclusion

Azure Load Balancer cost comes from SKU, region, rule count, processed data, traffic paths, and surrounding resources. Model rules and data separately, then validate with the official calculator and Cost Management actuals after deployment.

The cheapest advertised charge rarely makes the best architecture. Balance price against availability, security, performance, and operational simplicity.

Frequently Asked Questions

How much does an Azure Load Balancer cost?

For Standard in East US, the first five rules cost $0.025/hour combined, extra rules $0.01/hour each, and processed data $0.005/GB. Add public IP, transfer, and monitoring costs, and confirm rates in the Azure pricing calculator.

What is the difference between Azure pay-as-you-go and reserved pricing?

Load Balancer bills on consumption: you pay for what you use. It isn't on Microsoft's reservation or savings plan lists. Those discounts apply to other resources, such as VMs, not Load Balancer meters.

Which is faster, ALB or NLB?

ALB and NLB are AWS terms. NLB is Layer 4, like Azure Load Balancer; ALB is Layer 7, like Application Gateway. The right choice depends on protocol and routing needs, not a universal speed ranking.

What is 168.63.129.16 used for?

It's Azure's platform virtual IP, used for Load Balancer health probes, DHCP, VM Agent signaling, and filtered DNS. You'll see it when troubleshooting connectivity. It isn't a normal public endpoint.

Are Azure Load Balancer rules charged separately?

Partly. Load-balancing and outbound rules count toward the billed total (first five grouped, then $0.01/hour each). Inbound NAT rules are free. Data processing is a separate meter.

Is Azure Load Balancer free?

Not anymore. Basic, formerly free, retired September 30, 2025. Standard has no hourly charge with zero rules, but processed data, public IPs, transfer, and monitoring still cost money.