Azure Data Explorer Cluster pattern-based discovery

  • Release version: Xanadu
  • Updated June 16, 2026
  • 2 minutes to read
  • Summarize
    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 detect and map Azure Data Explorer Clusters within their cloud environments using the Discovery and Service Mapping Patterns application. This facilitates automated identification and integration of Azure resources into both CMDB and non-CMDB tables, enhancing cloud asset visibility and management.

    Show full answer Show less

    Key Features

    • Pattern Activation: The Azure Data Explorer Cluster discovery pattern is disabled by default. Starting with Visibility Content version 6.28.0, enabling or disabling patterns no longer counts as customization, ensuring patterns receive updates and reset to the latest version after upgrades while preserving active state.
    • Discovery Prerequisites: Customers must verify Microsoft Azure discovery prerequisites and use appropriate datacenter URLs, especially for Azure GovCloud (US) accounts, during Azure service account setup to ensure successful discovery.
    • Data Population: The discovery pattern populates data in both CMDB and non-CMDB tables:
      • Non-CMDB Table (cmdbazuredataexplorerclustersdataexplorerclusters): Stores detailed Azure resource attributes such as object ID, resource kind, location, resource group, subscription and tenant IDs, provisioning state, disk encryption status, and public network access.
      • CMDB Table (cmdbciclouddbcluster): Holds configuration items with fields including resource name, location, cluster ID, cluster status, install status, operational status, resource description, and vendor information.
    • CI Relationships: The pattern establishes relationships linking Cloud DataBase Clusters to resource groups and Azure datacenters, supporting comprehensive service mapping.
    • Azure Tag Discovery: Tags associated with Azure resources are collected and stored in the Key Value [cmdbkeyvalue] table, allowing easier categorization and filtering based on tags.

    Practical Implications for ServiceNow Customers

    By enabling this discovery pattern, customers can automatically identify Azure Data Explorer Clusters, maintain up-to-date configuration data, and establish accurate relationships within their CMDB. This supports effective cloud resource management, compliance, and operational insight. Ensuring prerequisite configuration and scheduling discovery appropriately—especially for GovCloud accounts—is essential for successful implementation.

    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

    Verify the Microsoft Azure discovery prerequisites
    For more information, see the prerequisites section in Microsoft Azure Cloud components discovery using patterns.
    Enable the relevant pattern
    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.
    Configure the Discovery schedule to support GovCloud
    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.

    Discovery and Service Mapping Patterns application populates data in both CMDB and non-CMDB tables.

    Data stored in non-CMDB tables

    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 All > Configuration > Azure. You can also search the navigation filter for the specific pattern name.

    Table 1. Azure Data Explorer Cluster [cmdb_azure_data_explorer_clusters_data_explorer_clusters]
    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.

    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.

    Table 2. Cloud DataBase Cluster [cmdb_ci_cloud_db_cluster]
    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.

    CI relationships

    The Azure - Data Explorer Cluster - Extended Inventory(LP) pattern creates these relationships to support Azure Data Explorer Cluster discovery.

    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

    The pattern collects tags and populates them in the Key Value [cmdb_key_value] table.
    Table 3. Key Value [cmdb_key_value]
    Field Description
    Key [key] Tag name.
    Value [value] Tag value.