> ## 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.

# Stop Unused Azure Data Explorer Cluster

> Stop Azure Data Explorer clusters that Azure Advisor finds unused.

A running Azure Data Explorer cluster bills for its compute every hour, even when nobody queries it and no data is ingested. Azure Advisor flags clusters with no recent use. nOps imports these recommendations, checks them against your bill, and shows the estimated monthly saving from stopping the cluster.

| | |
| - | - |
| **Cloud** | Microsoft Azure |
| **Category** | Database |
| **Service** | Azure Data Explorer |
| **Action** | Stop |
| **Effort** | Low |
| **Restart needed** | No |
| **Can be rolled back** | Yes |
| **Analysis window** | Last 7 days |
| **Source** | Azure Advisor |

## Why it matters

Clusters for proofs of concept or old projects are easy to forget, and their compute keeps billing.

## How nOps finds it

This recommendation comes from Azure Advisor, which looks for clusters with little or no query and ingestion activity. nOps imports Advisor's recommendations daily and checks each one against your own Azure bill for the last 7 complete days: the resource must still be billed in the last 3 days of that window, and Advisor's estimate is capped at what the resource actually cost (Advisor prices at pay-as-you-go rates, so you may pay less through discounts, reservations or savings plans). Recommendations worth less than \$1 a month are left out.

## Before you start

Confirm with the owner that nothing queries or ingests into the cluster, including scheduled jobs and dashboards.

## How to implement

1. Confirm with the owner that the cluster is not needed right now.
2. In the Azure portal, open the cluster and select **Stop**. Or use `az kusto cluster stop --resource-group RESOURCE_GROUP --name CLUSTER`.
3. If the cluster is no longer needed at all, delete it instead.
4. Consider turning on **auto-stop** for clusters that are used only occasionally.

## Risks and considerations

* A stopped cluster cannot be queried and stops ingesting data. Data from sources such as Event Hubs that arrives while it is stopped may be lost if it expires in the source first.
* Storage keeps billing while the cluster is stopped.
* To roll back, start the cluster again; it takes several minutes.

## Related

* [Right-size Azure Data Explorer Cluster](https://help.nops.io/inform/supported-recommendations/right-size-azure-data-explorer-cluster)
* [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.