Azure Databricks Workspace pattern-based discovery

  • Release version: Yokohama
  • 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 Databricks Workspace pattern-based discovery

    The Azure Databricks Workspace pattern-based discovery in ServiceNow enables automated detection and inventory of Azure Databricks workspaces within your cloud environment. This discovery uses pattern-based methods to populate detailed information about Databricks workspaces into both CMDB and non-CMDB tables, ensuring accurate configuration management and visibility of your Azure resources.

    Show full answer Show less

    Key Features

    • Pattern Activation: The Azure Databricks Workspace discovery pattern is disabled by default and must be enabled to function. Starting with Visibility Content version 6.28.0, enabling or disabling patterns is non-destructive and patterns reset to the latest version upon upgrade while preserving activation state.
    • Prerequisites: Verify Microsoft Azure discovery prerequisites and set up Azure service accounts correctly, including special configuration for Azure GovCloud (US) accounts by using appropriate datacenter URLs.
    • Data Population: The discovery populates resource data into:
      • Non-CMDB Tables: Specifically, the cmdbazuredatabricksworkspace table with fields such as kind, location, object ID, provisioning state, public network access, resource group, SKU name, subscription ID, tenant ID, and workspace ID.
      • CMDB Tables: The cmdbcicmpresource table is populated with install status, location, name, object ID, operational status, and resource type (set to microsoft.databricks/workspaces).
    • CI Relationships: The pattern establishes relationships between discovered configuration items, linking Databricks workspaces to resource groups, Azure datacenters, and cloud resources to maintain accurate dependency mapping.
    • Tag Collection: Azure tags are discovered and stored in the cmdbkeyvalue table, capturing tag names and values to enhance resource metadata and support governance.

    Practical Benefits for ServiceNow Customers

    • Automates comprehensive discovery of Azure Databricks workspaces, reducing manual inventory efforts.
    • Improves configuration accuracy by integrating detailed workspace data into your CMDB and related tables.
    • Supports compliance and operational management by maintaining up-to-date resource statuses and relationships.
    • Facilitates enhanced governance through tag collection and structured metadata storage.
    • Provides clear guidance on enabling patterns and configuring discovery schedules, especially for specialized environments like Azure GovCloud.

    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 - Databricks Workspace - 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 Databricks - Workspace [cmdb_azure_databricks_workspace]
    Field Description
    Kind [kind] The model or configuration type of the resource.
    Location [location] Geographical region where the resource is deployed.
    Object Id [object_id] The unique identifier of the resource.
    Provisioning State [provisioning_state] The current provisioning state of the resource.
    Public Network Access [public_network_access] Indicates whether public network access is enabled for the resource.
    Resource Group [resource_group] Name of the resource group.
    SKU name [sku_name] The stock keeping unit (SKU) that defines the resource's pricing tier.
    Subscription ID [subscription_id] The subscription ID.
    Tenant ID [tenant_id] The identifier for the Azure Active Directory tenant.
    Workspace ID [workspace_id] The unique identifier for the workspace associated with the resource.
    Configuration Item [configuration_item] References the Cloud Resource [cmdb_ci_cmp_resource] table.

    Data stored in CMDB tables

    Discovery and Service Mapping Patterns application populates data in the CMDB when running the Azure - Databricks Workspace - Extended Inventory(LP) pattern.

    Table 2. Cloud Resource [cmdb_ci_cmp_resource]
    Field Description
    Install Status [install_status] Install status of the resource. Default value is Installed.
    Location [location] Geographical region where the resource is deployed.
    Name [name] The name assigned to the resource.
    Object ID [object_id] The unique identifier of the resource.
    Operational status [operational_status] Operational status of the resource. Default value is Operational.
    Resource type [resource_type] Type of resource. The value is set to microsoft.databricks/workspaces.

    CI relationships

    The pattern creates these relationships to support discovery.

    CI Relationship CI
    Resource Group [cmdb_ci_resource_group] Contains::Contained by Cloud Resource [cmdb_ci_cmp_resource]
    Cloud Resource [cmdb_ci_cmp_resource] Hosted on::Hosts Azure Datacenter [cmdb_ci_azure_datacenter]
    Azure Databricks - Workspace [cmdb_azure_databricks_workspace] References Cloud Resource [cmdb_ci_cmp_resource]

    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.