---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Azure Data Explorer Cluster

# Azure Data Explorer Cluster pattern-based discovery {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Azure Data Explorer Cluster pattern-based discovery

Azure Data Explorer Cluster pattern-based discovery in ServiceNow enables automated detection and mapping of Azure Data Explorer Clusters within your cloud environment.
This functionality is part of the Discovery and Service Mapping Patterns application, which identifies Azure services and populates data into both CMDB and non-CMDB tables for comprehensive asset and configuration management.
Show full answer Show less  

## Key Features

* **Pattern-based Discovery:** Uses specific patterns to find Azure Data Explorer Clusters and related resources.
* **Permissions and Prerequisites:** Requires REST API permissions and adherence to Microsoft Azure discovery prerequisites, including removing duplicate resources from the Resource Inclusion List.
* **Pattern Activation:** Patterns like the Azure Data Explorer Cluster are disabled by default and must be enabled; changes to pattern activation persist through upgrades without being treated as customizations.
* **GovCloud Support:** Special configuration is needed to discover Azure GovCloud (US) accounts by using datacenter-specific URLs.
* **Data Population:** Discovery populates information into both CMDB and non-CMDB tables, facilitating detailed visibility into Azure resources and their configurations.
* **Tag Collection:** Azure tags are collected and stored in the Key Value table to enhance resource categorization and filtering.

## Data Captured and CMDB Integration

The discovery populates detailed attributes of Azure Data Explorer Clusters, including identifiers, location, subscription and tenant IDs, provisioning state, encryption status, and network access in the **non-CMDB table** . Corresponding entries are created in the **CMDB Cloud DataBase Cluster table** capturing operational status, installation details, vendor information, and descriptive metadata.

Relationships between Azure Data Explorer Clusters and other CIs such as Resource Groups and Azure Datacenters are automatically established to reflect resource dependencies and hosting environments.

## Practical Benefits for ServiceNow Customers

* Automates accurate discovery and inventory of Azure Data Explorer Clusters for improved cloud asset management.
* Supports compliance and operational visibility by providing up-to-date configuration and operational status within the CMDB.
* Enhances cloud governance through tag collection and detailed relationship mapping.
* Allows seamless upgrades and pattern updates without losing activation settings, ensuring ongoing discovery effectiveness.  
Discovery and Service Mapping Patterns finds Azure services on your cloud environment. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.

## Pattern-based discovery and mapping requirements {#azure-data-explorer-cluster__selection_ipy_53n_jfc}

Verify the REST API permissions
:   Download the [Cloud Discovery patterns spreadsheet](https://downloads.docs.servicenow.com/resource/enus/api/servicenow-discovery-patterns-api-details.xlsx) so you can grant user permissions required for running the Discovery patterns. In addition to permissions, the spreadsheet also includes useful information such as pattern names, types, CI Classes, and links to vendor documentation. New patterns are available quarterly, so check periodically to be sure you have the latest version of the spreadsheet.{#azure-data-explorer-cluster__cloud-discovery-api-ph-short-prereq}

Verify the Microsoft Azure discovery prerequisites{#azure-data-explorer-cluster__verify-azure-discovery-prerequisites-dlentry}
:   For more information, see the prerequisites section in [Microsoft Azure Cloud discovery using patterns](https://www.servicenow.com/docs/e2521~KHAw8EO7j1nC9QMA "Discovery uses multiple patterns to discover components of the Microsoft Azure Cloud deployment during horizontal discovery. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.").

Remove resources from the Resource Inclusion List table{#azure-data-explorer-cluster__remove-resource-inclusion-list-azure}
:   Verify that the relevant resource isn't listed in the Resource Inclusion List \[sa_cloud_inventory_resource_whitelist\] table to avoid duplicate discovery. For more information on removing resources from the Resource
    Inclusion List, see [Microsoft Azure resource inventory discovery](https://www.servicenow.com/docs/tO3nNqXv4zOe7q99krvAnA "The ServiceNow Discovery application uses the Azure Resource Inventory (LP) pattern to find resources available through Azure that don’t have a dedicated pattern. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.").

Enable the relevant pattern{#azure-data-explorer-cluster__enable-pattern-reuse-dlentry}
:   The pattern for this service is disabled by default. Starting with Visibility Content version 6.28.0, activating or deactivating a pattern won't be considered a customization, and it will continue to receive updates. Patterns that were previously activated or deactivated will reset to the latest predefined version after upgrading while retaining the last active field value. For more information on enabling patterns, see [Activate a disabled pattern](https://www.servicenow.com/docs/aypCYVQdO8oFebLMLEI89g "If you want to use a pattern for discovery that's disabled by default, activate it manually.").{#azure-data-explorer-cluster__activating-disabled-pattern-not-customization}

Configure the Discovery schedule to support GovCloud{#azure-data-explorer-cluster__configure-govcloud-azure-dlentry}
:   Discovering Azure GovCloud (US) accounts requires using a datacenter URL when setting up an Azure service account. For more information, see [Set up Azure service accounts](https://www.servicenow.com/docs/XKQpJvxWTKNL58XCkRHVxA "Create and configure cloud service accounts at ServiceNow AI Platform for the corresponding Microsoft Azure accounts.").{#azure-data-explorer-cluster__configure-govcloud-azure-dd}
{#azure-data-explorer-cluster__configure-govcloud-azure-dd} Discovery and Service Mapping Patterns application populates data in both CMDB and non-CMDB tables.

## Data stored in non-CMDB tables {#azure-data-explorer-cluster__section_aq4_qkq_hfc}

Discovery and Service Mapping Patterns application populates data in the non-CMDB table when running the Azure - Data Explorer Cluster - Extended Inventory(LP) pattern.

You can review the non-CMDB
Azure tables by navigating to AllConfigurationAzure. You can also search the navigation filter for the specific pattern name.  
{#azure-data-explorer-cluster__section_aq4_qkq_hfc__entry__2}

| Field | Description |
|-|-|
| Object Id \[object_id\] | The unique identifier of the Azure resource. |
| Kind \[kind\] | The specific kind or stock-keeping unit (SKU) of the resource. |
| DC Location \[location\] | The Azure region where the resource is deployed. |
| Resource Group \[resource_group\] | The name of the resource group that contains the resource. |
| Subscription Id \[subscription_id\] | The unique identifier of the Azure subscription. |
| Tenant Id \[tenant_id\] | The unique identifier of the Azure Active Directory tenant. |
| Provisioning State \[provisioning_state\] | The current provisioning state of the resource. |
| Configuration Item \[configuration_item\] | References the Cloud DataBase Cluster \[cmdb_ci_cloud_db_cluster\] table. |
| Enable Disk Encryption \[enable_disk_encryption\] | Specifies whether disk encryption is enabled on the resource. |
| Public Network Access \[public_network_access\] | Indicates if the resource is accessible over a public network. |
[Table 1. Azure Data Explorer Cluster \[cmdb_azure_data_explorer_clusters_data_explorer_clusters\]]

## Data stored in CMDB tables

Discovery and Service Mapping Patterns application populates data in the CMDB when running the Azure - Data Explorer Cluster - Extended Inventory(LP) pattern.  
{#azure-data-explorer-cluster__entry__24}

| Field | Description |
|-|-|
| Name \[name\] | The name assigned to the Azure resource. |
| Location \[location\] | The Azure region where the resource is deployed. |
| Cluster ID \[cluster_id\] | The unique identifier of the Azure resource. |
| Cluster Status \[cluster_status\] | The current operational status of the Kusto cluster. |
| Install Status \[install_status\] | Install status of the resource. Default value is Installed. |
| Operational status \[operational_status\] | Operational status of the resource. Default value is Operational. |
| Description \[short_description\] | Type of resource. The value is set to microsoft.kusto/clusters. |
| Vendor \[vendor\] | Name of vendor: Microsoft. |
[Table 2. Cloud DataBase Cluster \[cmdb_ci_cloud_db_cluster\]]

## CI relationships

The Azure - Data Explorer Cluster - Extended Inventory(LP) pattern creates these relationships to support Azure Data Explorer Cluster discovery.  
{#azure-data-explorer-cluster__entry__43}

| CI | Relationship | CI |
|-|-|-|
| Resource Group \[cmdb_ci_resource_group\] | Contains::Contained by | Cloud DataBase Cluster \[cmdb_ci_cloud_db_cluster\] |
| Cloud DataBase Cluster \[cmdb_ci_cloud_db_cluster\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] |
| Azure Data Explorer Cluster \[cmdb_azure_data_explorer_clusters_data_explorer_clusters\] | References | Cloud DataBase Cluster \[cmdb_ci_cloud_db_cluster\] |
[ ]

## Azure tag discovery {#azure-data-explorer-cluster__section_ezc_jwt_jfc}

The pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table. {#azure-data-explorer-cluster__table_axq_spc_y2c__entry__2}

| Field | Description |
|-|-|
| Key \[key\] | Tag name. |
| Value \[value\] | Tag value. |
[Table 3. Key Value \[cmdb_key_value\]]

{#azure-data-explorer-cluster__table_axq_spc_y2c}

*[\>]: and then