---
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 Databricks Workspace

# Azure Databricks Workspace 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 Databricks Workspace pattern-based discovery

Azure Databricks Workspace pattern-based discovery enables ServiceNow customers to identify and map Azure Databricks workspace resources within their cloud environments.
This discovery leverages the Discovery and Service Mapping Patterns application to populate data into both CMDB and non-CMDB tables, facilitating comprehensive visibility and management of Azure Databricks resources.
Show full answer Show less  

## Key Features

* **Pattern Activation:** The Azure Databricks Workspace discovery pattern is disabled by default and requires activation. Starting with Visibility Content version 6.28.0, enabling or disabling patterns is non-destructive and patterns update automatically after upgrades.
* **Permissions and Prerequisites:** Proper REST API permissions must be granted as outlined in the Cloud Discovery patterns spreadsheet, which includes pattern names, CI classes, and vendor documentation. Microsoft Azure discovery prerequisites must also be met.
* **Resource Inclusion List Management:** Ensure resources are not duplicated by verifying they are not listed in the Resource Inclusion List table prior to discovery.
* **Discovery Scheduling:** Special configuration is required to discover Azure GovCloud (US) accounts by using datacenter URLs when setting up Azure service accounts.
* **Data Population:** The discovery pattern populates detailed Azure Databricks workspace data in the *cmdbazuredatabricksworkspace* non-CMDB table and the *cmdbcicmpresource* CMDB table, enabling accurate asset tracking.
* **Tag Collection:** Azure resource tags are discovered and stored in the *cmdbkeyvalue* table to support tagging-based management and reporting.
* **CI Relationships:** The discovery creates relationships among Configuration Items (CIs), linking Databricks workspaces to resource groups, cloud resources, and Azure datacenters to maintain an organized CMDB structure.

## Data Details

The following key fields are captured for each Azure Databricks workspace resource:

* **Kind, Location, Object ID, Provisioning State**: Define the resource type, deployment region, unique identifier, and current state.
* **Public Network Access, Resource Group, SKU Name**: Network accessibility, grouping, and pricing tier details.
* **Subscription ID, Tenant ID, Workspace ID**: Azure subscription and tenant identifiers along with workspace-specific IDs.
* **Install and Operational Status**: Status indicators recorded in the CMDB.

## Practical Benefits for ServiceNow Customers

* Automates discovery and mapping of Azure Databricks workspaces to maintain accurate and up-to-date CMDB records.
* Supports compliance and operational management by capturing detailed resource attributes and tags.
* Facilitates better cloud resource governance through established CI relationships and integration with ServiceNow's broader discovery framework.
* Ensures discovery accuracy by managing resource inclusion lists and following Azure-specific prerequisites.  
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-databricks-workspace__section_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-databricks-workspace__cloud-discovery-api-ph-short-prereq}

Verify the Microsoft Azure discovery prerequisites{#azure-databricks-workspace__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-databricks-workspace__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-databricks-workspace__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-databricks-workspace__activating-disabled-pattern-not-customization}

Configure the Discovery schedule to support GovCloud{#azure-databricks-workspace__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-databricks-workspace__configure-govcloud-azure-dd}
{#azure-databricks-workspace__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-databricks-workspace__section_aq4_qkq_hfc}

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 AllConfigurationAzure. You can also search the navigation filter for the specific pattern name.  
{#azure-databricks-workspace__section_aq4_qkq_hfc__entry__2}

| 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. |
[Table 1. Azure Databricks - Workspace \[cmdb_azure_databricks_workspace\]]

## 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.  
{#azure-databricks-workspace__entry__26}

| 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. |
[Table 2. Cloud Resource \[cmdb_ci_cmp_resource\]]

## CI relationships

The pattern creates these relationships to support discovery.
{#azure-databricks-workspace__entry__41}

| 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 {#azure-databricks-workspace__section_ezc_jwt_jfc}

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

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

{#azure-databricks-workspace__table_axq_spc_y2c}

*[\>]: and then