diff --git a/data-explorer/dashboard-parameters.md b/data-explorer/dashboard-parameters.md index a83ca9d043..19c79d175c 100644 --- a/data-explorer/dashboard-parameters.md +++ b/data-explorer/dashboard-parameters.md @@ -148,7 +148,7 @@ The parameter can be seen in the **Parameters** side pane, but aren't currently #### Use a single-selection fixed-values parameter -1. Run a sample query using the new *Event TypTope* parameter by using the `_eventType` variable name: +1. Run a sample query that uses the new *Event Type* parameter by using the `_eventType` variable name: ```kusto StormEvents @@ -249,13 +249,13 @@ Query-based parameter values are retrieved during dashboard loading by executing ### Multiple-selection query-based parameters -Query-based parameter values are derived at dashboard load time by executing the user specified query. The following example shows how to can create a multiple-selection query-based parameter: +Query-based parameter values come from running the user-specified query when the dashboard loads. The following example shows how to create a multiple-selection query-based parameter: #### Create a multiple-selection query-based parameter 1. Select **Parameters** to open the **Parameters** pane and select **+ New parameter**. -1. 1. Fill in the details as mentioned in [Use a single-selection fixed-values parameter](#use-a-single-selection-fixed-values-parameter) with the following changes: +1. Fill in the details as described in [Use a single-selection fixed-values parameter](#use-a-single-selection-fixed-values-parameter) with the following changes: * **Label**: State * **Parameter type**: Multiple selection diff --git a/data-explorer/data-explorer-insights.md b/data-explorer/data-explorer-insights.md index 09bdaa0d8c..993fd6498f 100644 --- a/data-explorer/data-explorer-insights.md +++ b/data-explorer/data-explorer-insights.md @@ -1,15 +1,16 @@ --- title: Azure Data Explorer Clusters insights -description: This article describes how to use Azure Data Explorer Clusters Insights. -ms,reviewer: guregini +description: This article describes how to use Azure Data Explorer Clusters insights. +ms.reviewer: guregini ms.topic: concept-article ms.date: 05/24/2022 +ai-usage: ai-assisted ms.custom: - subject-monitoring - sfi-image-nochange --- -# Azure Data Explorer Clusters Insights +# Azure Data Explorer Clusters insights Azure Data Explorer Clusters Insights provides comprehensive monitoring of your clusters by delivering a unified view of your cluster performance, operations, usage, and failures. @@ -102,7 +103,7 @@ The **Key Metrics** tab shows a unified view of some of the cluster's metrics. T ### Usage tab -The **Usage** tab allows users to deep dive into the performance of the cluster's commands and queries. On this tab, you can: +The **Usage** tab provides detailed insights into the performance of the cluster's commands and queries. On this tab, you can: - See which workload groups, users, and applications are sending the most queries or consuming the most CPU and memory. You can then understand which workloads are submitting the heaviest queries for the cluster to process. - Identify top workload groups, users, and applications by failed queries. @@ -121,7 +122,7 @@ The **Tables** tab shows the latest and historical properties of tables in the c ### Cache tab -The **Cache** tab allows users to analyze their actual queries' lookback window patterns and compare them to the configured cache policy (for each table). You can identify tables used by the most queries and tables that aren't queried at all, and adapt the cache policy accordingly. +The **Cache** tab lets you analyze your actual queries' lookback window patterns and compare them to the configured cache policy for each table. You can identify tables used by the most queries and tables that aren't queried at all, and adapt the cache policy accordingly. You might get cache policy recommendations on specific tables in Azure Advisor. Currently, cache recommendations are available only from the [main Azure Advisor dashboard](azure-advisor.md#use-azure-advisor-recommendations). They're based on actual queries' lookback window in the past 30 days and an unoptimized cache policy for at least 95 percent of the queries. @@ -140,7 +141,7 @@ On this tab, you can select a metric tile and deep dive to understand its trend ### Ingestion tab (preview tab) -The **Ingestion** tab allows you to monitor the status of queued ingestion operations to the cluster. +The **Ingestion** tab lets you monitor the status of queued ingestion operations to the cluster. In the [queued ingestion](ingest-data-overview.md#continuous-data-ingestion) process, data ingestion is optimized for high throughput. This is done by grouping small chunks of incoming data into batches based on a configurable [ingestion batching policy](/kusto/management/batching-policy?view=azure-data-explorer&preserve-view=true). diff --git a/data-explorer/end-to-end-blob-ingestion.md b/data-explorer/end-to-end-blob-ingestion.md index e051b1bb53..06b49ad3a4 100644 --- a/data-explorer/end-to-end-blob-ingestion.md +++ b/data-explorer/end-to-end-blob-ingestion.md @@ -1,15 +1,16 @@ --- -title: 'End-to-end blob ingestion into Azure Data Explorer' -description: In this article, you learn how to ingest blobs into Azure Data Explorer with an end-to-end example. +title: 'Configure Azure Data Explorer to ingest from Azure Blob Storage' +description: In this tutorial, you learn how to ingest blobs into Azure Data Explorer with an end-to-end example. ms.reviewer: lugoldbe -ms.topic: tutorial +ms.topic: how-to ms.date: 05/10/2023 +ai-usage: ai-assisted ms.custom: - devx-track-arm-template - sfi-ropc-nochange --- -# End-to-end blob ingestion into Azure Data Explorer +# Configure Azure Data Explorer to ingest from Azure Blob Storage Azure Data Explorer is a fast and scalable data exploration service for log and telemetry data. This article gives you an end-to-end example of how to ingest data from Azure Blob storage into Azure Data Explorer. @@ -191,7 +192,7 @@ In this article, you use an Azure Resource Manager (ARM) template to create a re "variables": { }, "resources": [{ - "apiVersion": "2017-04-01", + "apiVersion": "2026-01-01", "type": "Microsoft.EventHub/namespaces", "name": "[parameters('eventHubNamespaceName')]", "location": "[parameters('location')]", @@ -205,7 +206,7 @@ In this article, you use an Azure Resource Manager (ARM) template to create a re "maximumThroughputUnits": 0 } }, { - "apiVersion": "2017-04-01", + "apiVersion": "2026-01-01", "type": "Microsoft.EventHub/namespaces/eventhubs", "name": "[concat(parameters('eventHubNamespaceName'), '/', parameters('eventHubName'))]", "location": "[parameters('location')]", @@ -218,7 +219,7 @@ In this article, you use an Azure Resource Manager (ARM) template to create a re "type": "Microsoft.Storage/storageAccounts", "name": "[parameters('storageAccountName')]", "location": "[parameters('location')]", - "apiVersion": "2018-07-01", + "apiVersion": "2026-04-01", "sku": { "name": "[parameters('storageAccountType')]" }, @@ -227,7 +228,7 @@ In this article, you use an Azure Resource Manager (ARM) template to create a re { "name": "[concat('default/', parameters('containerName'))]", "type": "blobServices/containers", - "apiVersion": "2018-07-01", + "apiVersion": "2026-04-01", "dependsOn": [ "[parameters('storageAccountName')]" ], @@ -245,7 +246,7 @@ In this article, you use an Azure Resource Manager (ARM) template to create a re "tier": "Standard", "capacity": 2 }, - "apiVersion": "2019-09-07", + "apiVersion": "2025-02-14", "location": "[parameters('location')]", "tags": { "Created By": "GitHub quickstart template" @@ -253,7 +254,7 @@ In this article, you use an Azure Resource Manager (ARM) template to create a re }, { "name": "[concat(parameters('kustoClusterName'), '/', parameters('kustoDatabaseName'))]", "type": "Microsoft.Kusto/clusters/databases", - "apiVersion": "2019-09-07", + "apiVersion": "2025-02-14", "location": "[parameters('location')]", "dependsOn": ["[resourceId('Microsoft.Kusto/clusters', parameters('kustoClusterName'))]"], "properties": { @@ -262,7 +263,7 @@ In this article, you use an Azure Resource Manager (ARM) template to create a re } }, { "type": "Microsoft.Kusto/Clusters/principalAssignments", - "apiVersion": "2019-11-09", + "apiVersion": "2025-02-14", "name": "[concat(parameters('kustoClusterName'), '/', parameters('clusterPrincipalAssignmentName'))]", "dependsOn": ["[resourceId('Microsoft.Kusto/clusters', parameters('kustoClusterName'))]"], "properties": { @@ -273,7 +274,7 @@ In this article, you use an Azure Resource Manager (ARM) template to create a re } }, { "type": "Microsoft.Kusto/Clusters/Databases/principalAssignments", - "apiVersion": "2019-11-09", + "apiVersion": "2025-02-14", "name": "[concat(parameters('kustoClusterName'), '/', parameters('kustoDatabaseName'), '/', parameters('databasePrincipalAssignmentName'))]", "dependsOn": ["[resourceId('Microsoft.Kusto/clusters/databases', parameters('kustoClusterName'), parameters('kustoDatabaseName'))]"], "properties": { diff --git a/data-explorer/how-it-works.md b/data-explorer/how-it-works.md index 18057e90a8..388475cc4b 100644 --- a/data-explorer/how-it-works.md +++ b/data-explorer/how-it-works.md @@ -2,7 +2,7 @@ title: How Azure Data Explorer works description: 'Learn more about how Azure Data Explorer works.' ms.reviewer: avnera -ms.topic: how-to +ms.topic: concept-article ms.date: 07/23/2026 ai-usage: ai-assisted --- @@ -63,11 +63,11 @@ For more information on specifying data sort order, see [Row order policy](/kust Azure Data Explorer uses distributed data query technology intended for fast ad hoc analytics on large unstructured data sets. Key features of this technology include: -* Query-generated temporary data is stored in aggregated RAM -* Relevant extents are marked on a query plan, providing snapshot isolation -* Fast and efficient queries are prioritized with short [default timeouts](/kusto/set-timeout-limits?view=azure-data-explorer&preserve-view=true) -* Native support for [cross-cluster queries](/kusto/query/cross-cluster-or-database-queries?view=azure-data-explorer&preserve-view=true) that minimizes inter-cluster data exchange -* Queries are just-in-time compiled into highly efficient machine code, using data statistics from all extents and tailored to column encoding specifics +* Query-generated temporary data is stored in aggregated RAM. +* Relevant extents are marked on a query plan, providing snapshot isolation. +* Fast and efficient queries are prioritized with short [default timeouts](/kusto/set-timeout-limits?view=azure-data-explorer&preserve-view=true). +* Native support for [cross-cluster queries](/kusto/query/cross-cluster-or-database-queries?view=azure-data-explorer&preserve-view=true) that minimizes inter-cluster data exchange. +* Queries are just-in-time compiled into highly efficient machine code, using data statistics from all extents and tailored to column encoding specifics. > [!NOTE] > Azure Data Explorer is designed to work with the [Kusto Query Language (KQL)](/kusto/query/index?view=azure-data-explorer&preserve-view=true), custom-built for Azure Data Explorer. Additionally, [T-SQL](t-sql.md) is supported. diff --git a/data-explorer/includes/iot-hub-get-started-create-device-identity.md b/data-explorer/includes/iot-hub-get-started-create-device-identity.md index bd3a69981c..a1d7795d05 100644 --- a/data-explorer/includes/iot-hub-get-started-create-device-identity.md +++ b/data-explorer/includes/iot-hub-get-started-create-device-identity.md @@ -3,7 +3,7 @@ description: include file services: iot-hub author: spelluru - ms.service: iot-hub + ms.service: azure-iot-hub ms.topic: include ms.date: 09/07/2018 ms.author: spelluru diff --git a/data-explorer/includes/iot-hub-include-create-hub.md b/data-explorer/includes/iot-hub-include-create-hub.md index eefa442250..73c43c4ab0 100644 --- a/data-explorer/includes/iot-hub-include-create-hub.md +++ b/data-explorer/includes/iot-hub-include-create-hub.md @@ -1,7 +1,7 @@ --- title: include file description: include file -ms.service: iot-hub +ms.service: azure-iot-hub services: iot-hub ms.topic: include ms.date: 02/14/2020 diff --git a/data-explorer/includes/iot-hub-pii-note-naming-device.md b/data-explorer/includes/iot-hub-pii-note-naming-device.md index 4176425c11..33bed84bd9 100644 --- a/data-explorer/includes/iot-hub-pii-note-naming-device.md +++ b/data-explorer/includes/iot-hub-pii-note-naming-device.md @@ -1,5 +1,5 @@ --- -ms.service: iot-hub +ms.service: azure-iot-hub ms.topic: include ms.date: 10/26/2018 --- diff --git a/data-explorer/includes/iot-hub-pii-note-naming-hub.md b/data-explorer/includes/iot-hub-pii-note-naming-hub.md index c5ac78a456..d28024a9ec 100644 --- a/data-explorer/includes/iot-hub-pii-note-naming-hub.md +++ b/data-explorer/includes/iot-hub-pii-note-naming-hub.md @@ -1,5 +1,5 @@ --- -ms.service: iot-hub +ms.service: azure-iot-hub ms.topic: include ms.date: 10/26/2018 --- diff --git a/data-explorer/ingest-data-event-grid-overview.md b/data-explorer/ingest-data-event-grid-overview.md index a0efa15292..5dd9aff176 100644 --- a/data-explorer/ingest-data-event-grid-overview.md +++ b/data-explorer/ingest-data-event-grid-overview.md @@ -2,8 +2,8 @@ title: Ingest from storage using Event Grid subscription - Azure Data Explorer description: This article describes Ingest from storage using Event Grid subscription in Azure Data Explorer. ms.reviewer: leshalev -ms.topic: how-to -ms.date: 08/11/2025 +ms.topic: concept-article +ms.date: 07/28/2026 ms.custom: - devx-track-azurepowershell - sfi-ropc-nochange diff --git a/data-explorer/k2bridge.md b/data-explorer/k2bridge.md index 78e07806ed..15ea9f2e71 100644 --- a/data-explorer/k2bridge.md +++ b/data-explorer/k2bridge.md @@ -3,8 +3,9 @@ title: Visualize data from Azure Data Explorer using Kibana description: In this article, you learn how to set up Azure Data Explorer as a data source for Kibana ms.reviewer: guregini ms.topic: how-to -ms.date: 03/12/2020 +ms.date: 07/28/2026 ms.custom: sfi-image-nochange +ai-usage: ai-assisted --- # Visualize data from Azure Data Explorer in Kibana with the K2Bridge open-source connector @@ -46,10 +47,10 @@ Before you can visualize data from Azure Data Explorer in Kibana, have the follo * An Azure subscription. Create a [free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn). * An [Azure Data Explorer cluster and database](create-cluster-and-database.md). You will need the cluster's URL and the database name. * [Helm v3](https://github.com/helm/helm#install), the Kubernetes package manager. -* Azure Kubernetes Service (AKS) cluster or any other Kubernetes cluster. Use version 1.21.2 or newer, with a minimum of three Azure Kubernetes Service nodes. Version 1.21.2 has been tested and verified. If you need an AKS cluster, see how to deploy an AKS cluster [using the Azure CLI](/azure/aks/kubernetes-walkthrough) or [using the Azure portal](/azure/aks/kubernetes-walkthrough-portal). +* Azure Kubernetes Service (AKS) cluster or any other Kubernetes cluster. Use version 1.21.2 or newer, with a minimum of three Azure Kubernetes Service nodes. Version 1.21.2 is tested and verified. If you need an AKS cluster, see how to deploy an AKS cluster [using the Azure CLI](/azure/aks/learn/quick-kubernetes-deploy-cli) or [using the Azure portal](/azure/aks/learn/quick-kubernetes-deploy-portal). * A Microsoft Entra service principal authorized to view data in Azure Data Explorer, including the client ID and client secret. Alternatively, you can use a [system-assigned managed identity](/azure/aks/use-managed-identity). -If you choose to use a Microsoft Entra service principal, you will need to [create a Microsoft Entra service principal](/azure/active-directory/develop/howto-create-service-principal-portal#create-an-azure-active-directory-application). For the installation, you will need the ClientID and a Secret. +If you choose to use a Microsoft Entra service principal, you need to [create a Microsoft Entra service principal](/entra/identity-platform/howto-create-service-principal-portal). For the installation, you need the ClientID and a Secret. We recommend a service principal with viewer permission and discourage you from using higher-level permissions. To assign permissions, see [Manage database permissions in the Azure portal](manage-database-permissions.md) or use management commands to [Manage database security roles](/kusto/management/manage-database-security-roles?view=azure-data-explorer&preserve-view=true). If you choose to use a system assigned identity, you will need to get the agent pool managed identity **ClientID** (located in the generated "[_MC_xxxx_]" [resource group](/azure/aks/faq#why-are-two-resource-groups-created-with-aks)) @@ -93,7 +94,7 @@ By default, the Helm chart of K2Bridge references a publicly available image loc ``` > [!NOTE] - > When using a managed identity, the ADX_CLIENT_ID value is the client ID of the managed identity, located in the generated "[_MC_xxxx_]" resource group. For more information, see [MC_ resource group](/azure/aks/faq#why-are-two-resource-groups-created-with-aks). The ADX_SECRET_ID is only required if you use a Microsoft Entra service principal. + > When you use a managed identity, the `ADX_CLIENT_ID` value is the client ID of the managed identity, located in the generated `[_MC_xxxx_]` resource group. For more information, see [MC_ resource group](/azure/aks/faq#why-are-two-resource-groups-created-with-aks). The `ADX_CLIENT_SECRET` is only required if you use a Microsoft Entra service principal. 1. Optionally, enable Application Insights telemetry. If you're using Application Insights for the first time, [create an Application Insights resource](/azure/azure-monitor/app/create-new-resource). [Copy the instrumentation key](/azure/azure-monitor/app/create-new-resource#copy-the-instrumentation-key) to a variable. @@ -118,7 +119,7 @@ By default, the Helm chart of K2Bridge references a publicly available image loc helm install k2bridge charts/k2bridge -n k2bridge --set settings.adxClusterUrl="$ADX_URL" --set settings.adxDefaultDatabaseName="$ADX_DATABASE" --set settings.aadClientId="$ADX_CLIENT_ID" --set settings.useManagedIdentity=true --set settings.aadTenantId="$ADX_TENANT_ID" [--set image.tag=7.16_latest] [--set settings.collectTelemetry=$COLLECT_TELEMETRY] ``` - In [Configuration](https://github.com/microsoft/K2Bridge/blob/master/docs/configuration.md), you can find the complete set of configuration options. + In [Configuration](https://github.com/microsoft/K2Bridge/blob/main/docs/configuration.md), you can find the complete set of configuration options. 1. The previous command's output suggests the next Helm command to deploy Kibana. Optionally, run this command: @@ -204,7 +205,7 @@ When Azure Data Explorer is configured as a data source for Kibana, you can use > Only kibana's Lucene query syntax is supported. Do not use the KQL option, which stands for Kibana Query Language. > [!Tip] -> In [Searching](https://github.com/microsoft/K2Bridge/blob/master/docs/searching.md), you can find more search rules and logic. +> In [Searching](https://github.com/microsoft/K2Bridge/blob/main/docs/searching.md), you can find more search rules and logic. 1. To filter your search results, use the **Available field** list. The field list is where you can see: diff --git a/data-explorer/kusto-emulator-install.md b/data-explorer/kusto-emulator-install.md index e5ac43d80e..adcf997b8d 100644 --- a/data-explorer/kusto-emulator-install.md +++ b/data-explorer/kusto-emulator-install.md @@ -10,10 +10,12 @@ ms.custom: sfi-image-nochange # Install the Azure Data Explorer Kusto emulator +The Kusto emulator is a local environment that runs the Azure Data Explorer query engine in a Docker container. You can develop and test queries without provisioning an Azure cluster. + You can install the Azure Data Explorer Kusto emulator in the following ways: -- **On your own device**: Consider using this option if you need to provision a local development environment -- **On a CI/CD agent virtual machine (VM)**: Use this option if you require a CI/CD pipeline for running automated tests +- **On your own device**: Use this option if you need to set up a local development environment. +- **On a CI/CD agent virtual machine (VM)**: Use this option if you need a CI/CD pipeline for running automated tests. The emulator is available as a *Linux* Docker container image. @@ -36,7 +38,7 @@ This article focuses on how to install the Linux Docker container on a Windows c - Any Linux distribution that supports Docker Client for Linux - A processor that supports SSE4.2/AVX2 instruction sets - At least 2 GB of RAM (4 GB or more recommended) -- [Docker Client for Linux](https://docs.docker.com/desktop/install/linux-install/) or [Docker Client for Windows](https://docs.docker.com/desktop/windows/install/) +- [Docker Client for Linux](https://docs.docker.com/desktop/setup/install/linux/) or [Docker Client for Windows](https://docs.docker.com/desktop/setup/install/windows-install/) > [!IMPORTANT] > Linux distros only support Linux container images. @@ -209,7 +211,7 @@ MyIngestedSample | summarize sum(Id), avg(Id) ``` -## Stopping the container +## Stop the container 1. You can stop the container by running the following command to obtain the container ID: diff --git a/data-explorer/kusto/management/alter-query-acceleration-policy-command.md b/data-explorer/kusto/management/alter-query-acceleration-policy-command.md index 5ddbb60141..638d100e06 100644 --- a/data-explorer/kusto/management/alter-query-acceleration-policy-command.md +++ b/data-explorer/kusto/management/alter-query-acceleration-policy-command.md @@ -3,7 +3,7 @@ title: .alter query acceleration policy command description: Learn how to use the .alter query acceleration policy command to accelerate queries over external delta tables. ms.reviewer: sharmaanshul ms.topic: reference -ms.date: 06/01/2026 +ms.date: 06/29/2026 --- # `.alter query acceleration policy` command @@ -12,6 +12,9 @@ ms.date: 06/01/2026 Alters the [query acceleration policy](query-acceleration-policy.md) of a specific external delta table. +> [!IMPORTANT] +> If the `AutoUpdateSchema` property is enabled on the external table and you intend to disable the policy, you must first disable `AutoUpdateSchema` by setting it to `false` using [`.alter external table`](external-tables-delta-lake.md) before disabling the query acceleration policy. + For limitations, see [Limitations](query-acceleration-policy.md#limitations). ## Permissions diff --git a/data-explorer/kusto/management/delete-query-acceleration-policy-command.md b/data-explorer/kusto/management/delete-query-acceleration-policy-command.md index a11889582b..55a5b910be 100644 --- a/data-explorer/kusto/management/delete-query-acceleration-policy-command.md +++ b/data-explorer/kusto/management/delete-query-acceleration-policy-command.md @@ -3,7 +3,7 @@ title: .delete query acceleration policy command description: Learn how to use the .delete query acceleration policy command to accelerate queries over external delta tables. ms.reviewer: sharmaanshul ms.topic: reference -ms.date: 09/16/2025 +ms.date: 06/29/2026 --- # `.delete query acceleration policy` command @@ -11,6 +11,9 @@ ms.date: 09/16/2025 Deletes the [`query acceleration policy`](query-acceleration-policy.md) of a specific external delta table. +> [!IMPORTANT] +> If the `AutoUpdateSchema` property is enabled on the external table, you must first disable it by setting `AutoUpdateSchema` to `false` using [`.alter external table`](external-tables-delta-lake.md) before deleting the query acceleration policy. + ## Permissions You must have at least [Database Admin](../access-control/role-based-access-control.md) permissions to run this command. diff --git a/data-explorer/kusto/management/external-tables-delta-lake.md b/data-explorer/kusto/management/external-tables-delta-lake.md index 1c778b2887..6f48729753 100644 --- a/data-explorer/kusto/management/external-tables-delta-lake.md +++ b/data-explorer/kusto/management/external-tables-delta-lake.md @@ -65,6 +65,7 @@ The supported authentication methods are the same as those supported by [Azure S | `fileExtension` | `string` | If set, specifies extension of the files. On write, files names will end with this suffix. On read, only files with this file extension will be read. | | `encoding` | `string` | Specifies how the text is encoded: `UTF8NoBOM` (default) or `UTF8BOM`. | | `dryRun` | `bool` | If set, the external table definition isn't persisted. This option is useful for validating the external table definition, especially in conjunction with the `filesPreview` or `sampleUris` parameter. | +| `AutoUpdateSchema` | `bool` | If set to `true`, the external table automatically tracks and reflects schema changes from the remote delta table. Schema is updated periodically, usually every several minutes, and may not reflect changes immediately. Requires a [query acceleration policy](query-acceleration-policy.md) to be enabled on the table. Only available when the schema is inferred (not user-provided). Default is `false`. | > [!NOTE] > The external delta table is accessed during creation, to infer the partitioning information and, optionally, the schema. Make sure that the table definition is valid and that the storage is accessible. diff --git a/data-explorer/kusto/management/graph/graph-model-create-or-alter.md b/data-explorer/kusto/management/graph/graph-model-create-or-alter.md index 96cc5c802a..89e515fec6 100644 --- a/data-explorer/kusto/management/graph/graph-model-create-or-alter.md +++ b/data-explorer/kusto/management/graph/graph-model-create-or-alter.md @@ -2,16 +2,14 @@ title: .create-or-alter graph_model command description: Learn how to create or alter a graph model using the create-or-alter graph_model command with syntax, parameters, and examples. ms.topic: reference -ms.date: 05/24/2025 +ms.reviewer: royo +ms.date: 07/29/2026 --- -# .create-or-alter graph_model (preview) +# .create-or-alter graph_model > [!INCLUDE [applies](../../includes/applies-to-version/applies.md)] [!INCLUDE [fabric](../../includes/applies-to-version/fabric.md)] [!INCLUDE [azure-data-explorer](../../includes/applies-to-version/azure-data-explorer.md)] -> [!NOTE] -> This feature is currently in preview. Functionality and syntax are subject to change before General Availability. - Creates a new graph model or alters an existing one using the provided model definition payload. ## Permissions diff --git a/data-explorer/kusto/management/graph/graph-model-drop.md b/data-explorer/kusto/management/graph/graph-model-drop.md index 638b2f942b..6063c024a7 100644 --- a/data-explorer/kusto/management/graph/graph-model-drop.md +++ b/data-explorer/kusto/management/graph/graph-model-drop.md @@ -1,18 +1,15 @@ --- title: .drop graph_model command description: Learn how to delete an existing graph model and all its versions using the .drop graph_model command. -ms.reviewer: herauch +ms.reviewer: royo ms.topic: reference -ms.date: 05/28/2025 +ms.date: 07/29/2026 --- -# .drop graph_model (preview) +# .drop graph_model > [!INCLUDE [applies](../../includes/applies-to-version/applies.md)] [!INCLUDE [fabric](../../includes/applies-to-version/fabric.md)] [!INCLUDE [azure-data-explorer](../../includes/applies-to-version/azure-data-explorer.md)] -> [!NOTE] -> This feature is currently in preview. Functionality and syntax are subject to change before General Availability. - Deletes an existing graph model and all its versions from the database, including any associated snapshots. ## Permissions diff --git a/data-explorer/kusto/management/graph/graph-model-overview.md b/data-explorer/kusto/management/graph/graph-model-overview.md index a37b930269..1c94fac27b 100644 --- a/data-explorer/kusto/management/graph/graph-model-overview.md +++ b/data-explorer/kusto/management/graph/graph-model-overview.md @@ -1,18 +1,15 @@ --- title: Graph models in Azure Data Explorer - Overview and usage description: Learn how to define, manage, and query persistent graph structures -ms.reviewer: herauch +ms.reviewer: royo ms.topic: reference -ms.date: 05/24/2025 +ms.date: 07/29/2026 --- -# Graph models overview (preview) +# Graph models overview > [!INCLUDE [applies](../../includes/applies-to-version/applies.md)] [!INCLUDE [fabric](../../includes/applies-to-version/fabric.md)] [!INCLUDE [azure-data-explorer](../../includes/applies-to-version/azure-data-explorer.md)] -> [!NOTE] -> This feature is currently in preview. Functionality and syntax are subject to change before General Availability. - Graph models in Azure Data Explorer enable you to define, manage, and efficiently query persistent graph structures within your database. Unlike transient graphs created using the [make-graph](../../query/make-graph-operator.md) operator, graph models are stored representations that can be queried repeatedly without rebuilding the graph for each query, significantly improving performance for complex relationship-based analysis. ## Overview diff --git a/data-explorer/kusto/management/graph/graph-model-show.md b/data-explorer/kusto/management/graph/graph-model-show.md index 45782e9975..1ee61747c7 100644 --- a/data-explorer/kusto/management/graph/graph-model-show.md +++ b/data-explorer/kusto/management/graph/graph-model-show.md @@ -1,18 +1,15 @@ --- title: .show graph_model command description: Learn how to display specific graph model versions using the .show graph_model command with syntax and examples. -ms.reviewer: herauch +ms.reviewer: royo ms.topic: reference -ms.date: 05/24/2025 +ms.date: 07/29/2026 --- -# .show graph_model (preview) +# .show graph_model > [!INCLUDE [applies](../../includes/applies-to-version/applies.md)] [!INCLUDE [fabric](../../includes/applies-to-version/fabric.md)] [!INCLUDE [azure-data-explorer](../../includes/applies-to-version/azure-data-explorer.md)] -> [!NOTE] -> This feature is currently in preview. Functionality and syntax are subject to change before General Availability. - Shows the details of a specific graph model, including its versions. ## Permissions diff --git a/data-explorer/kusto/management/graph/graph-models-show.md b/data-explorer/kusto/management/graph/graph-models-show.md index 06bcd8489e..df53055fee 100644 --- a/data-explorer/kusto/management/graph/graph-models-show.md +++ b/data-explorer/kusto/management/graph/graph-models-show.md @@ -1,18 +1,15 @@ --- title: .show graph_models command description: Learn how to list all graph models in a database using the .show graph_models command with syntax, parameters, and examples. -ms.reviewer: herauch +ms.reviewer: royo ms.topic: reference -ms.date: 05/24/2025 +ms.date: 07/29/2026 --- -# .show graph_models (preview) +# .show graph_models > [!INCLUDE [applies](../../includes/applies-to-version/applies.md)] [!INCLUDE [fabric](../../includes/applies-to-version/fabric.md)] [!INCLUDE [azure-data-explorer](../../includes/applies-to-version/azure-data-explorer.md)] -> [!NOTE] -> This feature is currently in preview. Functionality and syntax are subject to change before General Availability. - Lists all graph models in the database, showing the latest version for each model by default. ## Permissions diff --git a/data-explorer/kusto/management/graph/graph-persistent-overview.md b/data-explorer/kusto/management/graph/graph-persistent-overview.md index 63a7f52ced..c7190276fa 100644 --- a/data-explorer/kusto/management/graph/graph-persistent-overview.md +++ b/data-explorer/kusto/management/graph/graph-persistent-overview.md @@ -1,18 +1,15 @@ --- title: Persistent graphs overview description: Learn about persistent graphs, including graph models, snapshots, and management commands for scalable graph analytics. -ms.reviewer: herauch +ms.reviewer: royo ms.topic: reference -ms.date: 05/24/2025 +ms.date: 07/29/2026 --- -# Persistent graphs overview (preview) +# Persistent graphs overview > [!INCLUDE [applies](../../includes/applies-to-version/applies.md)] [!INCLUDE [fabric](../../includes/applies-to-version/fabric.md)] [!INCLUDE [azure-data-explorer](../../includes/applies-to-version/azure-data-explorer.md)] -> [!NOTE] -> This feature is currently in preview. Functionality and syntax are subject to change before General Availability. - Persistent graphs enable you to store, manage, and query graph data structures at scale. Unlike transient graphs created with the [make-graph](../../query/make-graph-operator.md) operator, persistent graphs are durable database objects that persist beyond individual query executions, providing enterprise-grade graph analytics capabilities. ## Overview diff --git a/data-explorer/kusto/management/graph/graph-snapshot-data-statistics-show.md b/data-explorer/kusto/management/graph/graph-snapshot-data-statistics-show.md index 77f5969858..efbde80329 100644 --- a/data-explorer/kusto/management/graph/graph-snapshot-data-statistics-show.md +++ b/data-explorer/kusto/management/graph/graph-snapshot-data-statistics-show.md @@ -3,16 +3,13 @@ title: .show graph_snapshot data statistics command description: Learn how to display storage profile statistics for a graph snapshot by using the .show graph_snapshot data statistics command. ms.reviewer: royo ms.topic: reference -ms.date: 06/16/2026 +ms.date: 07/29/2026 --- -# .show graph_snapshot data statistics (preview) +# .show graph_snapshot data statistics > [!INCLUDE [applies](../../includes/applies-to-version/applies.md)] [!INCLUDE [fabric](../../includes/applies-to-version/fabric.md)] [!INCLUDE [azure-data-explorer](../../includes/applies-to-version/azure-data-explorer.md)] -> [!NOTE] -> This feature is currently in preview. Functionality and syntax are subject to change before General Availability. - Displays a storage profile for a specific graph snapshot, including persisted size, compression, index footprint, and element count for nodes, edges, and graph structure data. ## Permissions diff --git a/data-explorer/kusto/management/graph/graph-snapshot-drop.md b/data-explorer/kusto/management/graph/graph-snapshot-drop.md index 6c20b11e6b..19f8304e11 100644 --- a/data-explorer/kusto/management/graph/graph-snapshot-drop.md +++ b/data-explorer/kusto/management/graph/graph-snapshot-drop.md @@ -1,18 +1,15 @@ --- title: .drop graph_snapshot command description: Learn how to delete a specific graph snapshot using the .drop graph_snapshot command with syntax, parameters, and examples. -ms.reviewer: herauch +ms.reviewer: royo ms.topic: reference -ms.date: 05/24/2025 +ms.date: 07/29/2026 --- -# .drop graph_snapshot (preview) +# .drop graph_snapshot > [!INCLUDE [applies](../../includes/applies-to-version/applies.md)] [!INCLUDE [fabric](../../includes/applies-to-version/fabric.md)] [!INCLUDE [azure-data-explorer](../../includes/applies-to-version/azure-data-explorer.md)] -> [!NOTE] -> This feature is currently in preview. Functionality and syntax are subject to change before General Availability. - Deletes a specific graph snapshot from a graph model. ## Permissions diff --git a/data-explorer/kusto/management/graph/graph-snapshot-make.md b/data-explorer/kusto/management/graph/graph-snapshot-make.md index e9879e1543..ba0921a11c 100644 --- a/data-explorer/kusto/management/graph/graph-snapshot-make.md +++ b/data-explorer/kusto/management/graph/graph-snapshot-make.md @@ -1,18 +1,15 @@ --- title: .make graph_snapshot command description: Learn how to create a graph snapshot from a graph model using the .make graph_snapshot command with syntax, parameters, and examples. -ms.reviewer: herauch +ms.reviewer: royo ms.topic: reference -ms.date: 05/24/2025 +ms.date: 07/29/2026 --- -# .make graph_snapshot (preview) +# .make graph_snapshot > [!INCLUDE [applies](../../includes/applies-to-version/applies.md)] [!INCLUDE [fabric](../../includes/applies-to-version/fabric.md)] [!INCLUDE [azure-data-explorer](../../includes/applies-to-version/azure-data-explorer.md)] -> [!NOTE] -> This feature is currently in preview. Functionality and syntax are subject to change before General Availability. - Creates a new graph snapshot from a specified graph model. A graph snapshot is a materialized instance of a graph model that can be efficiently queried. ## Permissions diff --git a/data-explorer/kusto/management/graph/graph-snapshot-overview.md b/data-explorer/kusto/management/graph/graph-snapshot-overview.md index 5f7856b5bb..2dc5f70454 100644 --- a/data-explorer/kusto/management/graph/graph-snapshot-overview.md +++ b/data-explorer/kusto/management/graph/graph-snapshot-overview.md @@ -1,18 +1,15 @@ --- title: Graph snapshots overview description: Learn about graph snapshots, including their structure, benefits, and how to create and query them for efficient graph data analysis. -ms.reviewer: herauch +ms.reviewer: royo ms.topic: reference -ms.date: 02/02/2026 +ms.date: 07/29/2026 --- -# Graph snapshots overview (preview) +# Graph snapshots overview > [!INCLUDE [applies](../../includes/applies-to-version/applies.md)] [!INCLUDE [fabric](../../includes/applies-to-version/fabric.md)] [!INCLUDE [azure-data-explorer](../../includes/applies-to-version/azure-data-explorer.md)] -> [!NOTE] -> This feature is currently in preview. Functionality and syntax are subject to change before General Availability. - A graph snapshot is a database entity that represents a materialized instance of a graph model at a specific point in time. While a [graph model](graph-model-overview.md) defines the structure and data sources, a snapshot is the queryable graph implementation. ## Overview diff --git a/data-explorer/kusto/management/graph/graph-snapshot-show.md b/data-explorer/kusto/management/graph/graph-snapshot-show.md index 18a3230604..4f1da8ebd6 100644 --- a/data-explorer/kusto/management/graph/graph-snapshot-show.md +++ b/data-explorer/kusto/management/graph/graph-snapshot-show.md @@ -1,18 +1,15 @@ --- title: .show graph_snapshot command description: Learn how to display information about a specific graph snapshot using the .show graph_snapshot command. -ms.reviewer: herauch +ms.reviewer: royo ms.topic: reference -ms.date: 05/24/2025 +ms.date: 07/29/2026 --- -# .show graph_snapshot (preview) +# .show graph_snapshot > [!INCLUDE [applies](../../includes/applies-to-version/applies.md)] [!INCLUDE [fabric](../../includes/applies-to-version/fabric.md)] [!INCLUDE [azure-data-explorer](../../includes/applies-to-version/azure-data-explorer.md)] -> [!NOTE] -> This feature is currently in preview. Functionality and syntax are subject to change before General Availability. - Shows detailed information about a specific graph snapshot. ## Permissions diff --git a/data-explorer/kusto/management/graph/graph-snapshot-statistics-show.md b/data-explorer/kusto/management/graph/graph-snapshot-statistics-show.md index a63eb6e119..446ea1f5bd 100644 --- a/data-explorer/kusto/management/graph/graph-snapshot-statistics-show.md +++ b/data-explorer/kusto/management/graph/graph-snapshot-statistics-show.md @@ -1,18 +1,15 @@ --- title: .show graph_snapshot statistics command description: Learn how to display graph snapshot statistics using the .show graph_snapshot statistics command with syntax, parameters, and examples. -ms.reviewer: vilauzon +ms.reviewer: royo ms.topic: reference -ms.date: 02/02/2026 +ms.date: 07/29/2026 --- -# .show graph_snapshot statistics (preview) +# .show graph_snapshot statistics > [!INCLUDE [applies](../../includes/applies-to-version/applies.md)] [!INCLUDE [fabric](../../includes/applies-to-version/fabric.md)] [!INCLUDE [azure-data-explorer](../../includes/applies-to-version/azure-data-explorer.md)] -> [!NOTE] -> This feature is currently in preview. Functionality and syntax are subject to change before General Availability. - Displays detailed statistics for a specific graph snapshot, including performance metrics, resource utilization, and processing details. ## Permissions diff --git a/data-explorer/kusto/management/graph/graph-snapshots-data-statistics-show.md b/data-explorer/kusto/management/graph/graph-snapshots-data-statistics-show.md index 906e9ffa03..7ccb4094be 100644 --- a/data-explorer/kusto/management/graph/graph-snapshots-data-statistics-show.md +++ b/data-explorer/kusto/management/graph/graph-snapshots-data-statistics-show.md @@ -3,16 +3,13 @@ title: .show graph_snapshots data statistics command description: Learn how to display storage profile statistics for graph snapshots by using the .show graph_snapshots data statistics command. ms.reviewer: royo ms.topic: reference -ms.date: 06/16/2026 +ms.date: 07/29/2026 --- -# .show graph_snapshots data statistics (preview) +# .show graph_snapshots data statistics > [!INCLUDE [applies](../../includes/applies-to-version/applies.md)] [!INCLUDE [fabric](../../includes/applies-to-version/fabric.md)] [!INCLUDE [azure-data-explorer](../../includes/applies-to-version/azure-data-explorer.md)] -> [!NOTE] -> This feature is currently in preview. Functionality and syntax are subject to change before General Availability. - Displays a storage profile for graph snapshots, including persisted size, compression, index footprint, and element count for nodes, edges, and graph structure data. ## Permissions diff --git a/data-explorer/kusto/management/graph/graph-snapshots-drop.md b/data-explorer/kusto/management/graph/graph-snapshots-drop.md index 1b1bebf882..10c9a94b4f 100644 --- a/data-explorer/kusto/management/graph/graph-snapshots-drop.md +++ b/data-explorer/kusto/management/graph/graph-snapshots-drop.md @@ -1,18 +1,15 @@ --- title: .drop graph_snapshots command description: Learn how to delete all graph snapshots for a specific graph model using the drop graph_snapshots command. -ms.reviewer: herauch +ms.reviewer: royo ms.topic: reference -ms.date: 05/24/2025 +ms.date: 07/29/2026 --- -# .drop graph_snapshots (preview) +# .drop graph_snapshots > [!INCLUDE [applies](../../includes/applies-to-version/applies.md)] [!INCLUDE [fabric](../../includes/applies-to-version/fabric.md)] [!INCLUDE [azure-data-explorer](../../includes/applies-to-version/azure-data-explorer.md)] -> [!NOTE] -> This feature is currently in preview. Functionality and syntax are subject to change before General Availability. - Deletes all graph snapshots associated with a specific graph model. ## Permissions diff --git a/data-explorer/kusto/management/graph/graph-snapshots-failures-show.md b/data-explorer/kusto/management/graph/graph-snapshots-failures-show.md index a012766fa3..1f1f02bc23 100644 --- a/data-explorer/kusto/management/graph/graph-snapshots-failures-show.md +++ b/data-explorer/kusto/management/graph/graph-snapshots-failures-show.md @@ -1,18 +1,15 @@ --- title: .show graph_snapshots failures command description: Learn how to display failed graph snapshots using the .show graph_snapshots failures command with syntax, parameters, and examples. -ms.reviewer: vilauzon +ms.reviewer: royo ms.topic: reference -ms.date: 02/02/2026 +ms.date: 07/29/2026 --- -# .show graph_snapshots failures (preview) +# .show graph_snapshots failures > [!INCLUDE [applies](../../includes/applies-to-version/applies.md)] [!INCLUDE [fabric](../../includes/applies-to-version/fabric.md)] [!INCLUDE [azure-data-explorer](../../includes/applies-to-version/azure-data-explorer.md)] -> [!NOTE] -> This feature is currently in preview. Functionality and syntax are subject to change before General Availability. - Displays information about failed graph snapshot creation attempts, including failure reasons, error details, and resource consumption statistics. ## Permissions diff --git a/data-explorer/kusto/management/graph/graph-snapshots-show.md b/data-explorer/kusto/management/graph/graph-snapshots-show.md index 489558e577..67e61f82c5 100644 --- a/data-explorer/kusto/management/graph/graph-snapshots-show.md +++ b/data-explorer/kusto/management/graph/graph-snapshots-show.md @@ -3,16 +3,13 @@ title: .show graph_snapshots command description: Learn how to list all graph snapshots for a graph model or all graph models using the .show graph_snapshots command. ms.reviewer: royo ms.topic: reference -ms.date: 05/27/2026 +ms.date: 07/29/2026 --- -# .show graph_snapshots (preview) +# .show graph_snapshots > [!INCLUDE [applies](../../includes/applies-to-version/applies.md)] [!INCLUDE [fabric](../../includes/applies-to-version/fabric.md)] [!INCLUDE [azure-data-explorer](../../includes/applies-to-version/azure-data-explorer.md)] -> [!NOTE] -> This feature is currently in preview. Functionality and syntax are subject to change before General Availability. - Lists all graph snapshots for a specific graph model or for all graph models in the database. ## Permissions diff --git a/data-explorer/kusto/management/graph/graph-snapshots-statistics-show.md b/data-explorer/kusto/management/graph/graph-snapshots-statistics-show.md index fbfa5b5b74..56b378dbe6 100644 --- a/data-explorer/kusto/management/graph/graph-snapshots-statistics-show.md +++ b/data-explorer/kusto/management/graph/graph-snapshots-statistics-show.md @@ -1,18 +1,15 @@ --- title: .show graph_snapshots statistics command description: Learn how to display statistics for all graph snapshots using the .show graph_snapshots statistics command with syntax, parameters, and examples. -ms.reviewer: vilauzon +ms.reviewer: royo ms.topic: reference -ms.date: 02/02/2026 +ms.date: 07/29/2026 --- -# .show graph_snapshots statistics (preview) +# .show graph_snapshots statistics > [!INCLUDE [applies](../../includes/applies-to-version/applies.md)] [!INCLUDE [fabric](../../includes/applies-to-version/fabric.md)] [!INCLUDE [azure-data-explorer](../../includes/applies-to-version/azure-data-explorer.md)] -> [!NOTE] -> This feature is currently in preview. Functionality and syntax are subject to change before General Availability. - Displays detailed statistics for all snapshots of a specific graph model, including performance metrics, resource utilization, and processing details. ## Permissions diff --git a/data-explorer/kusto/management/query-acceleration-policy.md b/data-explorer/kusto/management/query-acceleration-policy.md index 620d9d3291..2799bfb47e 100644 --- a/data-explorer/kusto/management/query-acceleration-policy.md +++ b/data-explorer/kusto/management/query-acceleration-policy.md @@ -3,7 +3,7 @@ title: Query acceleration policy description: Learn how to use the query acceleration policy to accelerate queries over external delta tables. ms.reviewer: sharmaanshul ms.topic: reference -ms.date: 06/01/2026 +ms.date: 06/29/2026 --- # Query acceleration policy @@ -30,7 +30,7 @@ To enable query acceleration in the Fabric UI, see [Query acceleration over OneL * Delta tables with checkpoint V2 aren't supported. * Query performance over accelerated external delta tables that have more than 2.5 million data files may not be optimal. * The feature assumes delta tables with static advanced features, for example column mapping doesn't change, partitions don't change, and so on. To change advanced features, first disable the policy, and once the change is made, re-enable the policy. -* Schema changes on the delta table must also be followed with the respective `.alter` external delta table schema, which might result in acceleration starting from scratch if there was breaking schema change. +* Schema changes on the delta table must also be followed with the respective `.alter` external delta table schema, which might result in acceleration starting from scratch if there was a breaking schema change. To automatically track schema changes, set the `AutoUpdateSchema` property to `true` on the external delta table. For more information, see [Create and alter delta external tables on Azure Storage](external-tables-delta-lake.md). * Parquet files larger than 1 GB won't be cached. * Manual edits to the delta table are not allowed and can lead to unexpected results. diff --git a/data-explorer/kusto/query/graph-function.md b/data-explorer/kusto/query/graph-function.md index 72644800eb..99cee3938f 100644 --- a/data-explorer/kusto/query/graph-function.md +++ b/data-explorer/kusto/query/graph-function.md @@ -3,15 +3,12 @@ title: graph function description: Learn how to use the graph function to reference a persisted graph entity for querying. ms.reviewer: royo ms.topic: reference -ms.date: 05/28/2025 +ms.date: 07/29/2026 --- -# graph function (preview) +# graph function >[!INCLUDE [applies](../includes/applies-to-version/applies.md)] [!INCLUDE [fabric](../includes/applies-to-version/fabric.md)] [!INCLUDE [azure-data-explorer](../includes/applies-to-version/azure-data-explorer.md)] -> [!NOTE] -> This feature is currently in public preview. Functionality and syntax are subject to change before General Availability. - The `graph` function is an intrinsic function that enables querying of a persisted graph entity, similar to the `cluster()`, `database()`, `external_table()`, and `table()` functions. It supports retrieving either the most recent snapshot of the graph, a specific snapshot, or creating a transient graph from the model. ## Permissions diff --git a/data-explorer/kusto/query/graph-mark-components-operator.md b/data-explorer/kusto/query/graph-mark-components-operator.md index f5e15629c4..f124681609 100644 --- a/data-explorer/kusto/query/graph-mark-components-operator.md +++ b/data-explorer/kusto/query/graph-mark-components-operator.md @@ -1,11 +1,11 @@ --- -title: graph-mark-components operator (preview) +title: graph-mark-components operator description: Learn how to use the graph-mark-components operator to find and mark all connected components of a graph. ms.reviewer: royo ms.topic: reference -ms.date: 05/24/2026 +ms.date: 07/29/2026 --- -# graph-mark-components operator (preview) +# graph-mark-components operator > [!INCLUDE [applies](../includes/applies-to-version/applies.md)] [!INCLUDE [fabric](../includes/applies-to-version/fabric.md)] [!INCLUDE [azure-data-explorer](../includes/applies-to-version/azure-data-explorer.md)] [!INCLUDE [monitor](../includes/applies-to-version/monitor.md)] [!INCLUDE [sentinel](../includes/applies-to-version/sentinel.md)] diff --git a/data-explorer/kusto/query/graph-shortest-paths-operator.md b/data-explorer/kusto/query/graph-shortest-paths-operator.md index bc5e29c072..8641c5479e 100644 --- a/data-explorer/kusto/query/graph-shortest-paths-operator.md +++ b/data-explorer/kusto/query/graph-shortest-paths-operator.md @@ -1,12 +1,12 @@ --- -title: graph-shortest-paths Operator (preview) +title: graph-shortest-paths Operator description: Learn how to use the graph-shortest-paths operator to efficiently find the shortest paths from a given set of source nodes to a set of target nodes within a graph ms.reviewer: royo ms.topic: reference -ms.date: 02/17/2025 +ms.date: 07/29/2026 --- -# graph-shortest-paths Operator (preview) +# graph-shortest-paths Operator > [!INCLUDE [applies](../includes/applies-to-version/applies.md)] [!INCLUDE [fabric](../includes/applies-to-version/fabric.md)] [!INCLUDE [azure-data-explorer](../includes/applies-to-version/azure-data-explorer.md)] [!INCLUDE [monitor](../includes/applies-to-version/monitor.md)] [!INCLUDE [sentinel](../includes/applies-to-version/sentinel.md)] diff --git a/data-explorer/kusto/query/tutorials/your-first-graph.md b/data-explorer/kusto/query/tutorials/your-first-graph.md index 65e7df8c6a..ef6fb5eddf 100644 --- a/data-explorer/kusto/query/tutorials/your-first-graph.md +++ b/data-explorer/kusto/query/tutorials/your-first-graph.md @@ -6,7 +6,8 @@ ms.author: spelluru ms.service: azure-data-explorer ms.topic: tutorial ms.custom: mvc -ms.date: 06/10/2026 +ms.reviewer: royo +ms.date: 07/29/2026 #customer intent: As a data analyst, I want to create and query graphs in KQL so that I can analyze interconnected data like organizational hierarchies. --- @@ -204,9 +205,6 @@ reports ## Create a persistent graph model -> [!NOTE] -> This feature is currently in public preview. Functionality and syntax are subject to change before General Availability. - Persistent graphs are stored in the database and can be queried repeatedly without rebuilding the graph structure. Create the same organizational structure as a persistent graph for better performance and reusability. Create functions that return your sample data, and then define a graph model structure: diff --git a/data-explorer/power-bi-data-connector.md b/data-explorer/power-bi-data-connector.md index fe8399638b..d6b7711c9e 100644 --- a/data-explorer/power-bi-data-connector.md +++ b/data-explorer/power-bi-data-connector.md @@ -26,13 +26,13 @@ Power BI supports *Import* and *DirectQuery* connectivity modes. When building P Use **Import** mode when: * Your dataset is small and you don't need near real-time data. -* You perform [aggregation in Kusto](/kusto/query/aggregation-functions?view=azure-data-explorer&preserve-view=true). +* You perform [aggregation in Kusto](/kusto/query/aggregation-functions). Use **DirectQuery** mode when: * Your dataset is large or you need near real-time data. -For more information on connectivity modes, see [Import and Direct Query connectivity modes](/power-bi/desktop-directquery-about). +For more information on connectivity modes, see [Import and DirectQuery connectivity modes](/power-bi/connect-data/desktop-directquery-about). ## Use data in Power BI @@ -109,7 +109,7 @@ The following steps use the StormEvents table from the [help cluster](https://he 1. On the **Navigator** screen, expand the **Samples** database, select **StormEvents**, and then select **Load Data**. - Optionally, if you want to shape your data first, select **Transform data** to launch Power Query Editor. For more information, see [Shape data](/power-bi/fundamentals/desktop-getting-started?source=recommendations&branch=main#shape-data). + Optionally, if you want to shape your data first, select **Transform data** to launch Power Query Editor. For more information, see [Shape data](/power-bi/fundamentals/desktop-getting-started#shape-data). :::image type="content" source="media/power-bi-data-connector/select-table.png" alt-text="Screenshot of Navigator screen, showing that the StormEvents table is selected. The Load button is highlighted."::: diff --git a/data-explorer/pricing-reserved-capacity.md b/data-explorer/pricing-reserved-capacity.md index 18790ac96d..e97c952cd2 100644 --- a/data-explorer/pricing-reserved-capacity.md +++ b/data-explorer/pricing-reserved-capacity.md @@ -3,14 +3,15 @@ title: Prepay for Azure Data Explorer markup to save money description: Learn how to buy Azure Data Explorer reserved capacity to save on your Azure Data Explorer costs. ms.reviewer: avnera ms.topic: how-to -ms.date: 05/21/2025 +ms.date: 07/28/2026 +ai-usage: ai-assisted --- # Prepay for Azure Data Explorer markup units with Azure Data Explorer reserved capacity Save money with Azure Data Explorer by prepaying for the markup units compared to pay-as-you-go prices. With Azure Data Explorer reserved capacity, you make a commitment for Azure Data Explorer use for a period of one or three years to get a significant discount on the Azure Data Explorer markup costs. To purchase Azure Data Explorer reserved capacity, you only need to specify the term, it will apply to all deployments of Azure Data Explorer in all regions. -By purchasing a reservation, you're pre-paying for the markup costs for a period of one or three years. As soon as you buy a reservation, the Azure Data Explorer markup charges that match the reservation attributes are no longer charged at the pay-as-you go rates. Azure Data Explorer clusters that are already running or ones that are newly deployed will automatically get the benefit. This reservation doesn't cover compute, networking, or storage charges associated with the clusters. Savings plans for compute and reserved capacity for networking and storage resources need to be purchased separately. At the end of the reservation term, the billing benefit expires, and the Azure Data Explorer markup units are billed at the pay-as-you go price. Reservations don't auto-renew. For pricing information, see the [Azure Data Explorer pricing page](https://azure.microsoft.com/pricing/details/data-explorer/). +When you purchase a reservation, you prepay for the markup costs for a period of one or three years. As soon as you buy a reservation, the Azure Data Explorer markup charges that match the reservation attributes are no longer charged at the pay-as-you-go rates. Azure Data Explorer clusters that are already running or ones that are newly deployed automatically get the benefit. This reservation doesn't cover compute, networking, or storage charges associated with the clusters. You need to purchase savings plans for compute and reserved capacity for networking and storage resources separately. At the end of the reservation term, the billing benefit expires, and the Azure Data Explorer markup units are billed at the pay-as-you-go price. Reservations don't auto-renew. For pricing information, see the [Azure Data Explorer pricing page](https://azure.microsoft.com/pricing/details/data-explorer/). You can buy Azure Data Explorer reserved capacity in the [Azure portal](https://portal.azure.com). To buy Azure Data Explorer reserved capacity: diff --git a/data-explorer/start-for-free-web-ui.md b/data-explorer/start-for-free-web-ui.md index e3e7840625..b903080b15 100644 --- a/data-explorer/start-for-free-web-ui.md +++ b/data-explorer/start-for-free-web-ui.md @@ -28,7 +28,7 @@ A Microsoft account or a Microsoft Entra user identity to create a free cluster. On your cluster's overview page, you see the following: 1. Your cluster's name, the option to upgrade to a full cluster, and the option to delete the cluster. -1. Your cluster's location, policies, and URI links for connecting to your cluster via our [APIs](/kusto/api/index?view=azure-data-explorer&preserve-view=true) or other tools. +1. Your cluster's location, policies, and URI links for connecting to your cluster via the [Kusto APIs](/kusto/api/index?view=azure-data-explorer&preserve-view=true) or other tools. 1. [Quick actions](#quick-actions) you can take to get started with your cluster. 1. A list of databases in your cluster. 1. A list of data connections in your cluster. diff --git a/data-explorer/web-sync.md b/data-explorer/web-sync.md index f56086374b..300c360544 100644 --- a/data-explorer/web-sync.md +++ b/data-explorer/web-sync.md @@ -2,7 +2,8 @@ title: Access your Azure Data Explorer web UI data anywhere description: This guide teaches you how to access your Azure Data Explorer Web UI Data from anywhere using syncing. ms.topic: how-to -ms.date: 05/13/2025 +ms.date: 07/28/2026 +ai-usage: ai-assisted #customer-intent: As a user, I want to learn how to sync my Azure Data Explorer web UI data so that I can access it from anywhere. --- @@ -61,7 +62,7 @@ If you enabled sync and want to stop syncing your Azure Data Explorer web UI pro ### Important notes when turning sync off - Turning sync off **stops updating cloud data**, but the cloud profile previously uploaded is **not deleted**. - Your existing cloud profile remains the version that other browsers use when sync is turned on again. -- Local browser data will no longer be uploaded or overwritten. +- Local browser data is no longer uploaded or overwritten. ## Turn sync back on @@ -72,7 +73,7 @@ If sync was previously disabled: 3. Confirm that the browser you are enabling sync on contains the state you want to upload as the cloud profile. > [!WARNING] -> When you turn sync back on, **this browser becomes the primary source again** and will overwrite cloud-stored data. +> When you turn sync back on, **this browser becomes the primary source again** and overwrites cloud-stored data. ## Determine the primary source of sync data