> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Delete Idle Azure Load Balancer

> Delete Azure load balancers that are billed for rules every day but process no data.

A Standard Azure Load Balancer is billed for each hour its load-balancing rules exist, even when no traffic passes through it. Load balancers are often left behind after the virtual machines or services behind them are removed. nOps finds load balancers billed for rules every day for two weeks with no data processed, and estimates the saving from deleting them.

| | |
| - | - |
| **Cloud** | Microsoft Azure |
| **Category** | Networking |
| **Service** | Load Balancer |
| **Action** | Delete |
| **Effort** | Low |
| **Restart needed** | No |
| **Can be rolled back** | No |
| **Analysis window** | Last 14 days |
| **Source** | nOps |

## Why it matters

An idle load balancer does nothing but cost money, and it is easy to miss because it has no compute of its own.

## How nOps finds it

nOps reads your Azure Load Balancer billing. A load balancer is flagged when its rule hours were billed on all of the last 14 days and it processed no data at all in that time. The saving is everything the load balancer cost in the last 7 days, net of discounts and scaled to a month, and must be at least \$5 a month. Load balancers in accounts where credits cover almost all of the cost are left out.

## Before you start

Permission to delete load balancers in the subscription (for example **Network Contributor**).

## How to implement

1. In the Azure portal, open **Load balancers** and select the load balancer.
2. Check **Backend pools**, **Frontend IP configuration** and any DNS records or routes that point at it, and confirm nothing depends on it.
3. Delete the load balancer, or run `az network lb delete --resource-group MY_RG --name MY_LB`.
4. Delete its public IP address too if nothing else uses it, since public IPs are billed separately.
5. If the load balancer is defined in Terraform, Bicep or ARM templates, remove it there as well.

## Risks and considerations

* A load balancer used only for failover can carry no traffic for weeks. Check before deleting.
* Load balancers created by AKS or other managed services are recreated by that service. Change the service instead.
* A deleted load balancer cannot be restored. You would recreate it with a new frontend unless you keep its public IP.

## FAQs

> [accordion] What if I only want to keep the public IP address?
>
> Keep the public IP resource and delete only the load balancer. You can attach the IP to a new load balancer later.

## Related

* [Delete Idle Azure NAT Gateway](https://help.nops.io/inform/supported-recommendations/delete-idle-azure-nat-gateway)
* [Delete Idle Azure Private Endpoint](https://help.nops.io/inform/supported-recommendations/delete-idle-azure-private-endpoint)
* [Delete Unconnected Azure Virtual Network Gateway](https://help.nops.io/inform/supported-recommendations/delete-unconnected-azure-virtual-network-gateway)
* [Supported recommendations](https://help.nops.io/inform/supported-recommendations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.