--- 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 Log Analytics Workspace # Azure Log Analytics 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 Log Analytics Workspace pattern-based discovery The Azure Log Analytics Workspace pattern-based discovery in ServiceNow enables automated detection and mapping of Azure Log Analytics workspaces within your cloud environment. This capability integrates with the Discovery and Service Mapping Patterns application to populate detailed information into the CMDB and related tables, supporting comprehensive cloud resource management and visibility. Show full answer Show less ## Key Features * **Pattern Activation:** The pattern for discovering Azure Log Analytics Workspaces is disabled by default but can be enabled without impacting upgrade updates, ensuring you always use the latest pattern version. * **Discovery Prerequisites:** Requires verifying REST API permissions, removing resources from the Resource Inclusion List to prevent duplication, and configuring discovery schedules, especially for Azure GovCloud (US) environments. * **Data Population:** Information is stored both in CMDB tables (e.g., `cmdbcicmpresource` for cloud resources) and non-CMDB tables (e.g., Azure-specific tables accessible via the Configuration menu). * **CI Relationships:** The pattern creates relationships linking Log Analytics workspaces with resource groups, cloud resources, and Azure datacenters, enhancing service mapping accuracy. * **Tag Collection:** Azure tags associated with discovered resources are collected and stored in the `cmdbkeyvalue` table, facilitating tag-based filtering and management. ## Key Outcomes * **Accurate Cloud Resource Discovery:** Enables you to identify and track Azure Log Analytics workspaces with detailed attributes such as object ID, location, subscription, provisioning state, and tenant information. * **Enhanced CMDB Data Quality:** Populates and maintains structured data in CMDB and non-CMDB tables, supporting effective asset management and operational insights. * **Improved Service Mapping:** Establishes clear relationships between Azure resources and their groups or datacenters, facilitating better dependency mapping and impact analysis. * **Governance and Compliance Support:** Tag discovery allows for categorizing and managing resources based on organizational requirements and policies. 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-log-analytics-workspace__selection_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-log-analytics-workspace__cloud-discovery-api-ph-short-prereq} Verify the Microsoft Azure discovery prerequisites{#azure-log-analytics-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-log-analytics-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-log-analytics-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-log-analytics-workspace__activating-disabled-pattern-not-customization} Configure the Discovery schedule to support GovCloud{#azure-log-analytics-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-log-analytics-workspace__configure-govcloud-azure-dd} {#azure-log-analytics-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-log-analytics-workspace__section_aq4_qkq_hfc} Discovery and Service Mapping Patterns application populates data in the non-CMDB table when running the Azure - Log Analytics 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-log-analytics-workspace__section_aq4_qkq_hfc__entry__2} | Field | Description | |-|-| | Object Id \[object_id\] | The unique identifier of the Azure resource. | | Kind \[kind\] | The specific kind or variant of the resource. | | DC Location \[location\] | The geographical region where the resource is deployed. | | Resource Group \[resource_group\] | The Azure resource group to which the resource belongs. | | Subscription Id \[subscription_id\] | The unique identifier of the Azure subscription containing the resource. | | Tenant Id \[tenant_id\] | The identifier of the Azure Active Directory tenant associated with the resource. | | Provisioning State \[provisioning_state\] | The current lifecycle state of the resource. For example: Succeeded, Creating, or Failed. | | Configuration Item \[configuration_item\] | References the Cloud Resource \[cmdb_ci_cmp_resource\] table. | | Customer Id \[customer_id\] | The unique identifier of the Log Analytics workspace or customer instance. | [Table 1. Azure Log Analytics - Workspace \[cmdb_azure_log_analytics_workspace\]] ## Data stored in CMDB tables Discovery and Service Mapping Patterns application populates data in the CMDB when running the Azure - Log Analytics Workspace - Extended Inventory(LP) pattern. {#azure-log-analytics-workspace__entry__22} | Field | Description | |-|-| | Object ID \[object_id\] | The unique identifier of the Azure resource. | | Name \[name\] | The name of the resource. | | Location \[location\] | The geographical region where the resource is deployed. | | 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. | | Resource type \[resource_type\] | Type of resource. The value is set to microsoft.operationalinsights/workspaces. | [Table 2. Cloud Resource \[cmdb_ci_cmp_resource\]] ## CI relationships The Azure - Log Analytics Workspace - Extended Inventory(LP) pattern creates these relationships to support Azure Log Analytics Workspace discovery. {#azure-log-analytics-workspace__entry__37} | 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 Log Analytics - Workspace \[cmdb_azure_log_analytics_workspace\] | References | Cloud Resource \[cmdb_ci_cmp_resource\] | [ ] ## Azure tag discovery {#azure-log-analytics-workspace__section_ezc_jwt_jfc} The pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table. {#azure-log-analytics-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-log-analytics-workspace__table_axq_spc_y2c} *[\>]: and then