Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
30 commits
Select commit Hold shift + click to select a range
cdfa739
new PR
ktalmor Oct 30, 2025
b2685c6
removed SDX
ktalmor Oct 30, 2025
c759b6d
wip
ktalmor Oct 30, 2025
00c1966
Merge branch 'main' of https://github.com/MicrosoftDocs/dataexplorer-…
ktalmor Nov 30, 2025
935c675
removing Synapse
ktalmor Dec 1, 2025
bd431ae
ms.topic: article
ktalmor Dec 1, 2025
230c6bd
Merge branch 'main' of https://github.com/MicrosoftDocs/dataexplorer-…
ktalmor Dec 1, 2025
2480c06
redirect added
ktalmor Dec 1, 2025
1863786
Keep Synapse SQL
ktalmor Dec 8, 2025
d9b38b2
redirect file fix
ktalmor Dec 8, 2025
bed878e
updated images
ktalmor Dec 8, 2025
a737951
final
ktalmor Dec 8, 2025
1c3e30c
Merge branch 'main' of https://github.com/MicrosoftDocs/dataexplorer-…
ktalmor Dec 8, 2025
59edcdb
Documentor and Acrolinx
ktalmor Dec 8, 2025
0879c55
build fixes
ktalmor Dec 8, 2025
71d33b5
ms.topic update
ktalmor Dec 8, 2025
cbe9de7
Merge branch 'main' of https://github.com/MicrosoftDocs/dataexplorer-…
ktalmor Dec 31, 2025
81c5624
double check
ktalmor Dec 31, 2025
082a770
fix bookmark
ktalmor Dec 31, 2025
8076905
Update source path in redirection configuration
ktalmor Jan 8, 2026
3b3dbec
Fix typo in database-script.md
ktalmor Jan 8, 2026
79466ed
Fix capitalization in subscription picker explanation
ktalmor Jan 8, 2026
07b8b4f
Fix title and grammar in Event Hub overview
ktalmor Jan 8, 2026
d1fe4b7
Fix grammatical error in data overview documentation
ktalmor Jan 8, 2026
f478f28
Fix spelling errors in integration overview
ktalmor Jan 8, 2026
fa6ba60
Fix typos and improve clarity in POC playbook
ktalmor Jan 8, 2026
e581276
Merge branch 'main' into Archive-SDX
ktalmor Jan 8, 2026
bbf489f
Merge pull request #7197 from ktalmor/Archive-SDX
v-ccolin Jan 8, 2026
55a2b1f
Merge pull request #7309 from MicrosoftDocs/main
learn-build-service-prod[bot] Jan 8, 2026
2c3be4f
Merging changes synced from https://github.com/MicrosoftDocs/dataexpl…
Jan 8, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions data-explorer/.openpublishing.redirection.json
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,11 @@
"redirect_url": "/kusto/query/graph-best-practices?view=azure-data-explorer&preserve-view=true",
"redirect_document_id": false
},
{
"source_path": "azure/synapse-analytics/quickstart-connect-azure-data-explorer.md",
"redirect_url": "/azure/data-explorer/integrate-overview",
"redirect_document_id": false
},
{
"source_path": "graph-overview.md",
"redirect_url": "/kusto/query/graph-semantics-overview?view=azure-data-explorer&preserve-view=true",
Expand Down
68 changes: 33 additions & 35 deletions data-explorer/auto-stop-clusters.md
Original file line number Diff line number Diff line change
@@ -1,81 +1,79 @@
---
title: Automatic stop of inactive clusters in Azure Data Explorer
description: Learn when your cluster will be stopped using the Automatic stop feature, and how to enable/disable the Automatic stop.
description: Learn when your cluster is due to stop running using the Automatic stop feature, and how to enable/disable the Automatic stop.
ms.reviewer: orhasban
ms.topic: how-to
ms.date: 11/03/2021
ms.date: 12/08/2025
---
# Automatic stop of inactive Azure Data Explorer clusters
# Configure automatic stop of inactive Azure Data Explorer clusters

Azure Data Explorer clusters that have been *inactive* for a specified time interval are automatically stopped. Inactivity is defined as clusters that haven't had any data ingestion or queries in the past 5 days. The interval is fixed at 5 days and cannot be changed.
Azure Data Explorer clusters that are *inactive* for a specified time interval stop automatically. Inactivity means clusters with no data ingestion or queries in the past 5 days. The interval is fixed at 5 days and can't be changed.

Cluster behavior isn't automatically resumed. To restart the cluster, do so manually.
Cluster behavior doesn't resume automatically. Restart the cluster manually.

> [!NOTE]
> Cluster types listed below are not automatically stopped: </br>
> The following cluster types aren't stopped automatically: </br>
>
> * Leader clusters. For more information, see [follower databases](follower.md).
> * Clusters deployed in a Virtual Network
> * [Start-for-free](start-for-free.md) clusters
> * Clusters where the [Auto-Stop setting](auto-stop-clusters.md#set-auto-stop-settings-while-creating-a-new-cluster) is turned off
> * Azure Synapse Data Explorer pools
> * Clusters where the [Auto-Stop setting](auto-stop-clusters.md#configure-auto-stop-while-creating-a-new-cluster) is turned off

## Manage Automatic stop behavior on your cluster
## Manage automatic stop behavior on your cluster

Azure Data Explorer clusters are created by default with the cluster property of `enableAutoStop = true`. This property can be set or altered either on cluster creation or post creation.
Azure Data Explorer clusters are created by default with the cluster property `enableAutoStop = true`. You can set or change this property during or after cluster creation.

[Azure portal](#configure-auto-stop-while-creating-a-new-cluster)

Set this property using one of the following methods, or using the [Azure portal](#azure-portal):
* [ARM Templates](/azure/templates/microsoft.kusto/clusters?tabs=json#trustedexternaltenant-object)
* [Azure CLI](/cli/azure/kusto/cluster#az-kusto-cluster-update-optional-parameters)
* [PowerShell](/powershell/module/az.kusto/new-azkustocluster)
* [Azure Resource Explorer](https://resources.azure.com/).

For more information, see [Azure Data Explorer cluster request body](/rest/api/azurerekusto/clusters/createorupdate#request-body).
* [Azure Resource Explorer](https://resources.azure.com/)

## Azure portal
Learn more in [Azure Data Explorer cluster request body](/rest/api/azurerekusto/clusters/createorupdate#request-body).

### Set Auto-Stop settings while creating a new cluster
## Configure auto-stop while creating a new cluster

1. Follow the steps in [Create an Azure Data Explorer cluster and database](create-cluster-and-database.md).
1. In the Azure portal, follow the steps in [create an Azure Data Explorer cluster and database](create-cluster-and-database.md).
1. In the **Configurations** tab, select **Auto-Stop cluster** > **On**.

:::image type="content" source="media/auto-stop-clusters/auto-stop-cluster-creation.png" alt-text="Screenshot of auto-stop configuration.":::
:::image type="content" source="media/auto-stop-clusters/auto-stop-cluster-creation.png" alt-text="Screenshot of auto-stop configuration." :::

### Modify settings on an existing cluster
## Modify settings on an existing cluster

To enable/disable Auto-Stop cluster after cluster was created:
To enable or disable Auto-Stop cluster after the cluster is created:

1. Sign into the [Azure portal](https://ms.portal.azure.com/).
1. Browse to your Azure Data Explorer cluster.
1. Sign in to the [Azure portal](https://ms.portal.azure.com/).
1. Go to your Azure Data Explorer cluster.
1. In **Settings**, select **Configurations**.
1. In the **Configurations** pane, select **On**/**Off** to enable/disable **Auto-Stop cluster**.
1. In the **Configurations** pane, select **On** or **Off** to enable or disable **Auto-Stop cluster**.
1. Select **Save**.

:::image type="content" source="media/auto-stop-clusters/auto-stop-cluster-update.png" alt-text="Screenshot of auto-stop configuration in Azure portal.":::
:::image type="content" source="media/auto-stop-clusters/auto-stop-cluster-update.png" alt-text="Screenshot of auto-stop configuration in the Azure portal.":::

## Verify Auto-Stop using the Activity log
## Verify auto-stop using the activity log

When a cluster is automatically stopped, an Activity log is sent. To verify when and how the cluster was stopped, use the following steps:

1. Sign into the [Azure portal](https://ms.portal.azure.com/).
1. Browse to Azure Data Explorer cluster.
1. On the left pane, select **Activity log**.
1. Choose a timespan.
1. Under **Operation name**, look for **Stop Clusters**.
1. In the left pane, select **Activity log**.
1. Select a timespan.
1. Under **Operation name**, find **Stop Clusters**.

:::image type="content" source="media/auto-stop-clusters/auto-stop-cluster-activity-log.png" alt-text="Screenshot of activity log.":::
:::image type="content" source="media/auto-stop-clusters/auto-stop-cluster-activity-log.png" alt-text="Screenshot of the activity log.":::

## Examples

### REST example

Update the cluster using the following operation:
Update the cluster with this operation:

```http
PATCH https://management.azure.com/subscriptions/12345678-1234-1234-1234-123456789098/resourceGroups/kustorgtest/providers/Microsoft.Kusto/clusters/kustoclustertest?api-version=2021-08-27
```

#### Request body to disable Auto-Stop
#### Request body to disable auto-stop

```json
{
Expand All @@ -85,12 +83,12 @@ PATCH https://management.azure.com/subscriptions/12345678-1234-1234-1234-1234567
}
```

#### Request body to enable Auto-Stop
#### Request body to enable auto-stop

```json
{
"properties": {
"enableAutoStop": true
}
"properties": {
"enableAutoStop": true
}
}
```
Loading