--- sourceDocument: Yokohama IT Operations Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama 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: Yokohama * * Updated August 11, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 The Azure Data Explorer Cluster pattern-based discovery enables ServiceNow customers to identify and map Azure Data Explorer resources within their cloud environment. This discovery is part of the Discovery and Service Mapping Patterns application, which finds Azure services and populates configuration data into both CMDB and non-CMDB tables. It supports detailed inventory and relationship mapping of Azure Data Explorer Clusters, essential for maintaining accurate cloud asset management and operational visibility. Show full answer Show less ## Key Features * **Pattern Activation:** The Azure Data Explorer Cluster discovery pattern is disabled by default. From Visibility Content version 6.28.0 onward, enabling or disabling patterns is not considered a customization and patterns automatically update to the latest version after upgrades while preserving activation status. * **Prerequisites:** Customers must verify Microsoft Azure discovery prerequisites and configure Azure service accounts appropriately, especially when discovering Azure GovCloud (US) environments, which require using datacenter-specific URLs. * **Data Population:** * **Non-CMDB tables:** Inventory data such as resource IDs, SKU types, locations, provisioning states, and encryption/network settings are stored in tables like *cmdbazuredataexplorerclustersdataexplorerclusters*. * **CMDB tables:** Operational and status information about the clusters, including names, cluster IDs, statuses, and vendor details, are stored in *cmdbciclouddbcluster*. * **CI Relationships:** The discovery pattern establishes relationships between cloud database clusters, Azure resource groups, and Azure datacenters, enhancing configuration item context and impact analysis. * **Tag Collection:** Tags assigned to Azure resources are collected and stored in the *cmdbkeyvalue* table, enabling tag-based filtering and management. ## What You Can Expect * Automated discovery and inventory of Azure Data Explorer Clusters with up-to-date configuration details aligned with Azure resource attributes. * Accurate mapping of cluster relationships within your Azure environment for improved service visibility and operational insights. * Support for Azure GovCloud environments by configuring discovery schedules with appropriate datacenter URLs. * Integration of both CMDB and non-CMDB data to provide a comprehensive view of Azure Data Explorer resources, including security and network access settings. * Collection of Azure resource tags to support enhanced categorization and management within ServiceNow CMDB. Discovery and Service Mapping Patterns finds Azure services on your cloud environment. Discovering some of these resources may 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 Microsoft Azure discovery prerequisites{#azure-data-explorer-cluster__verify-azure-discovery-prerequisites-dlentry} : For more information, see the prerequisites section in [Microsoft Azure Cloud components discovery using patterns](https://servicenow-prod.fluidtopics.net/JeDZ0tlC9eLF5fei5qSv3w "Discovery uses multiple patterns to discover components of the Microsoft Azure Cloud deployment during horizontal discovery. Discovering some of these resources may 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://servicenow-prod.fluidtopics.net/R5W5GP640V_5uNIhVNRPCw "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://servicenow-prod.fluidtopics.net/wA59_lRoV_0PzpuODHnNjA "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