Azure Data Explorer Cluster pattern-based discovery

  • Release version: Zurich
  • 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 discover and map Azure Data Explorer Cluster resources within their Microsoft Azure cloud environments. This capability is part of the Discovery and Service Mapping Patterns application and supports automated population of Configuration Management Database (CMDB) and non-CMDB tables with detailed Azure resource data. It is essential for customers managing Azure cloud services to maintain accurate and up-to-date CMDB data for operational visibility and service management.

    Show full answer Show less

    Key Features

    • Pattern Activation: The Azure Data Explorer Cluster discovery pattern is disabled by default and requires activation. With Visibility Content version 6.28.0 and later, enabling or disabling patterns does not count as customization, allowing seamless updates while retaining activation status.
    • Prerequisites: Customers must meet Microsoft Azure discovery prerequisites and configure the Azure service account correctly, especially when working with Azure GovCloud (US), which requires a specific datacenter URL.
    • Data Population:
      • Non-CMDB Tables: Running the Azure - Data Explorer Cluster - Extended Inventory (LP) pattern populates detailed resource information in non-CMDB tables under the Azure namespace. Key fields include Object Id, Kind, Location, Resource Group, Subscription Id, Tenant Id, Provisioning State, and configuration references.
      • CMDB Tables: The same pattern also populates the Cloud DataBase Cluster CMDB table with operational and install statuses, location, cluster ID, vendor information, and descriptive metadata.
    • CI Relationships: The discovery establishes important configuration item relationships, such as resource group containment, hosting on Azure datacenters, and references between Azure Data Explorer Clusters and Cloud DataBase Clusters, enriching the CMDB topology.
    • Tag Discovery: The pattern collects Azure tags and stores them in the Key Value table, facilitating enhanced filtering, reporting, and operational management based on resource metadata.

    Practical Benefits

    • Automates discovery and mapping of Azure Data Explorer Clusters, reducing manual effort and increasing accuracy.
    • Ensures customers have comprehensive visibility into Azure cluster resources, their statuses, configurations, and relationships within their ServiceNow CMDB.
    • Supports compliance and governance efforts by capturing provisioning states, encryption settings, and network accessibility details.
    • Enables advanced service mapping and impact analysis through well-defined CI relationships and tag management.
    • Facilitates smooth upgrades and pattern maintenance without losing activation settings, ensuring continuous operational support.

    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 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.