> ## 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 Private Endpoint

> Delete Azure private endpoints that have processed no data in 60 days.

An Azure private endpoint is billed for every hour it exists, plus a charge per GB it processes. Endpoints are often created for a test or a migration and left in place after the service behind them stops being used. nOps finds private endpoints billed every day for 60 days with no data processed, and estimates the saving from deleting them.

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

## Why it matters

Each endpoint costs little on its own, but large estates can hold hundreds of them, one per service and network.

## How nOps finds it

nOps reads your Azure Private Link billing. A private endpoint is flagged when its hourly charge was billed on all of the last 60 complete days and it processed no data at all in that time. nOps uses 60 days rather than 14 because endpoints that are only used now and then would otherwise be flagged. The saving is everything the endpoint cost in the last 7 days, net of discounts and scaled to a month, and must be at least \$5 a month.

## Before you start

Permission to delete private endpoints (for example **Network Contributor**).

## How to implement

1. In the Azure portal, open **Private Link Center → Private endpoints** and select the endpoint.
2. Check which resource it connects to and whether that resource is still in use.
3. Check the private DNS zone records for the endpoint so you know what clients resolve the service name to.
4. Delete the endpoint, or run `az network private-endpoint delete --resource-group MY_RG --name MY_ENDPOINT`.
5. If the endpoint is defined in Terraform, Bicep or ARM templates, remove it there as well.

## Risks and considerations

* After deletion, clients resolve the service name to its public endpoint. If public access to the service is turned off, those clients can no longer reach it.
* A deleted endpoint cannot be restored. You can create a new one, which gets a new private IP address.

## FAQs

> [accordion] Why does nOps wait 60 days?
>
> Some endpoints carry traffic only for occasional jobs. Waiting 60 days with no data at all makes it much less likely that an endpoint still in use is flagged.

## Related

* [Delete Idle Azure Load Balancer](https://help.nops.io/inform/supported-recommendations/delete-idle-azure-load-balancer)
* [Delete Idle Azure NAT Gateway](https://help.nops.io/inform/supported-recommendations/delete-idle-azure-nat-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.