--- 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 Log Analytics Workspace # Azure Log Analytics 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 Log Analytics Workspace pattern-based discovery The Azure Log Analytics Workspace pattern-based discovery in ServiceNow enables automated identification and mapping of Azure Log Analytics Workspaces within your cloud environment. Utilizing Discovery and Service Mapping Patterns, it helps keep your Configuration Management Database (CMDB) and related tables updated with detailed Azure resource information, enhancing visibility and management of your Azure cloud services. Show full answer Show less ## Key Features * **Pattern Activation:** The discovery pattern for Azure Log Analytics Workspace is disabled by default and must be enabled. From Visibility Content version 6.28.0 onward, activating or deactivating patterns does not count as customization, ensuring patterns receive updates after upgrades. * **Azure GovCloud Support:** Discovery of Azure GovCloud (US) accounts requires configuring Azure service accounts with appropriate datacenter URLs. * **Data Population:** The discovery populates data into both CMDB and non-CMDB tables: * **Non-CMDB Tables:** The Azure - Log Analytics Workspace - Extended Inventory (LP) pattern writes detailed workspace data to non-CMDB tables, accessible via the ServiceNow Azure configuration navigation. * **CMDB Tables:** It also populates the Cloud Resource \[cmdbcicmpresource\] table with resource details such as name, location, install status, operational status, and resource type. * **CI Relationships:** The pattern establishes relationships linking Azure Log Analytics Workspaces to resource groups and datacenters, supporting comprehensive service mapping. * **Tag Discovery:** Tags associated with Azure resources are collected and stored in the Key Value \[cmdbkeyvalue\] table, facilitating tag-based filtering and management. ## Practical Considerations * Ensure you meet Microsoft Azure discovery prerequisites to enable smooth discovery processes. * Activate the relevant Azure Log Analytics Workspace discovery pattern to start data collection. * Configure discovery schedules appropriately, especially when working with Azure GovCloud environments. * Review discovered data in both CMDB and non-CMDB tables to gain comprehensive insights into your Azure resources. ## Key Outcomes By leveraging this pattern-based discovery, ServiceNow customers can expect: * Accurate and up-to-date inventory of Azure Log Analytics Workspaces within the CMDB. * Clear visibility into workspace properties, states, and associated Azure resource groups and datacenters. * Enhanced service mapping and dependency tracking through established CI relationships. * Improved resource management using discovered tags and metadata. * Streamlined discovery processes compliant with Azure and GovCloud requirements. 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-log-analytics-workspace__selection_ipy_53n_jfc} 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 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-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://servicenow-prod.fluidtopics.net/R5W5GP640V_5uNIhVNRPCw "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://servicenow-prod.fluidtopics.net/wA59_lRoV_0PzpuODHnNjA "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