--- 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 Databricks Workspace # Azure Databricks Workspace 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 Databricks Workspace pattern-based discovery The Azure Databricks Workspace pattern-based discovery enables ServiceNow customers to identify and collect detailed information about Azure Databricks workspaces within their Microsoft Azure cloud environments. This discovery is part of the Discovery and Service Mapping Patterns application, which locates Azure services and populates the ServiceNow CMDB and related tables with relevant resource data. The pattern is disabled by default and requires activation to function. Show full answer Show less ## Key Features * **Pattern Activation:** Starting with Visibility Content version 6.28.0, enabling or disabling this discovery pattern no longer counts as a customization, allowing seamless updates without losing activation status. * **Azure GovCloud Support:** Supports discovery of Azure GovCloud (US) accounts by requiring configuration of datacenter URLs when setting up Azure service accounts. * **Data Population:** The discovery populates data into both CMDB and non-CMDB tables: * **Non-CMDB data:** Captured when running the Azure - Databricks Workspace - Extended Inventory (LP) pattern, stored in tables accessible via the Azure namespace in the ServiceNow platform. * **CMDB data:** Populates core resource details into the Cloud Resource \[cmdbcicmpresource\] table, including operational status and resource type. * **CI Relationships:** Automatically creates relationships linking Databricks workspace CIs with resource groups and Azure datacenters to reflect infrastructure hierarchy and hosting context. * **Tag Discovery:** Collects Azure tags and stores them in the Key Value \[cmdbkeyvalue\] table, enabling effective classification and filtering of discovered resources. ## Practical Application for ServiceNow Customers By enabling this pattern, customers gain comprehensive visibility into their Azure Databricks workspaces, including configuration details, operational status, and associated metadata. This supports better asset management, compliance tracking, and operational insight within the ServiceNow CMDB. Configuring the discovery schedule properly, especially for GovCloud environments, ensures accurate and timely data collection. The resulting CI relationships and tagging information enhance CMDB data integrity and enable advanced service mapping and impact analysis. 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-databricks-workspace__section_ipy_53n_jfc} 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 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-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://servicenow-prod.fluidtopics.net/R5W5GP640V_5uNIhVNRPCw "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://servicenow-prod.fluidtopics.net/wA59_lRoV_0PzpuODHnNjA "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