--- 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 Event Grid # Azure Event Grid System Topic discovery with Patterns {#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 Event Grid System Topic discovery with Patterns This documentation explains how the Discovery and Service Mapping Patterns application in ServiceNow identifies and maps Azure Event Grid System Topics within your Azure cloud environment. It highlights the prerequisites, configuration steps, and the data storage approach used to support accurate discovery and integration into the ServiceNow Configuration Management Database (CMDB). Show full answer Show less ## Key Features * **Pattern Activation:** The Azure Event Grid System Topic discovery pattern is disabled by default and requires enabling. Starting with Visibility Content version 6.28.0, enabling or disabling patterns is preserved through updates without being treated as customizations. * **Azure GovCloud Support:** Discovery of Azure GovCloud (US) accounts requires configuring the Azure service account with a specific datacenter URL to ensure proper access. * **Data Storage:** The discovery process populates data in both CMDB and non-CMDB tables: * **Non-CMDB Tables:** When running the Azure - Event Grid System Topic - Extended Inventory (LP) pattern, data about Event Grid System Topics is stored in dedicated non-CMDB tables specific to Azure resources. These tables include detailed fields such as kind, provisioning state, resource group, subscription ID, tenant ID, topic type, and metric resource ID. * **CMDB Tables:** The Cloud Messaging Service CI records are created and updated in the CMDB with key attributes like install status, location, name, operational status, type (set to microsoft.eventgrid/systemtopics), and object ID. * **Tag Collection:** Azure tags associated with resources are collected and stored in the cmdbkeyvalue table, capturing key-value pairs to support resource categorization and reporting. * **CI Relationships:** The pattern automatically establishes relationships among configuration items to represent real-world dependencies, such as resource groups containing cloud messaging services, which in turn are hosted on Azure datacenters. The Event Grid System Topic references the Cloud Messaging Service CI. ## Practical Considerations for ServiceNow Customers * Ensure you meet Microsoft Azure discovery prerequisites and update the Discovery and Service Mapping Patterns application to the latest version from the ServiceNow Store for optimal pattern functionality. * Enable the Azure Event Grid System Topic discovery pattern to begin populating your CMDB and non-CMDB tables with relevant Azure Event Grid data. * Configure discovery schedules appropriately, especially if working with Azure GovCloud, by specifying the correct datacenter URLs when setting up Azure service accounts. * Utilize the populated CMDB and non-CMDB tables to gain insights into your Azure Event Grid resources, monitor provisioning and operational status, and leverage tag data for better asset management and reporting. * Understand the CI relationships created to model your Azure environment accurately, supporting impact analysis and service mapping. 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-event-grid-pattern__section_ipy_53n_jfc} Verify the Microsoft Azure discovery prerequisites{#azure-event-grid-pattern__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-event-grid-pattern__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-event-grid-pattern__activating-disabled-pattern-not-customization} Configure the Discovery schedule to support GovCloud{#azure-event-grid-pattern__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-event-grid-pattern__configure-govcloud-azure-dd} {#azure-event-grid-pattern__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-event-grid-pattern__section_aq4_qkq_hfc} Discovery and Service Mapping Patterns application populates data in the non-CMDB table when running the Azure - Event Grid System Topic - 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-event-grid-pattern__section_aq4_qkq_hfc__entry__2} | Field | Description | |-|-| | Kind \[kind\] | The specific kind or stock keeping unit (SKU) of the resource, detailing its capabilities or configuration. | | Metric Resource Id \[metric_resource_id\] | The identifier used for accessing metrics related to the resource. | | Object Id \[object_id\] | The unique identifier of the resource within Azure. | | Provisioning State \[provisioning_state\] | The current status of the resource's provisioning process. | | Resource Group \[resource_group\] | Name of the resource group. | | Subscription Id \[subscription_id\] | The subscription ID. | | Tenant Id \[tenant_id\] | The unique identifier for the Azure Active Directory tenant. | | Topic Type \[topic_type\] | The category or type of the event topic. | | Configuration Item \[configuration_item\] | References the Cloud Messaging Service \[cmdb_ci_cloud_messaging_service\] table. | [Table 1. Azure Event Grid - System Topic \[cmdb_azure_event_grid_system_topic\]] ## Data stored in CMDB tables Discovery and Service Mapping Patterns application populates data in the CMDB when running the Azure - Event Grid System Topic - Extended Inventory(LP) pattern. {#azure-event-grid-pattern__entry__22} | Field | Description | |-|-| | Install Status \[install_status\] | Install status of the resource. Default value is Installed. | | Location \[location\] | The geographical region where the resource is hosted. | | Name \[name\] | The name of the resource. | | Object ID \[object_id\] | The unique identifier of the resource within Azure. | | Operational status \[operational_status\] | Operational status of the resource. Default value is Operational. | | Type \[type\] | Type of resource. The value is set to microsoft.eventgrid/systemtopics. | [Table 2. Cloud Messaging Service \[cmdb_ci_cloud_messaging_service\]] ## CI relationships The pattern creates these relationships to support discovery. {#azure-event-grid-pattern__entry__37} | CI | Relationship | CI | |-|-|-| | Resource Group \[cmdb_ci_resource_group\] | Contains::Contained by | Cloud Messaging Service \[cmdb_ci_cloud_messaging_service\] | | Cloud Messaging Service \[cmdb_ci_cloud_messaging_service\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] | | Azure Event Grid - System Topic \[cmdb_azure_event_grid_system_topic\] | References | Cloud Messaging Service \[cmdb_ci_cloud_messaging_service\] | [ ] ## Azure tag discovery {#azure-event-grid-pattern__section_ezc_jwt_jfc} The pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table. {#azure-event-grid-pattern__table_axq_spc_y2c__entry__2} | Field | Description | |-|-| | Key \[key\] | Tag name. | | Value \[value\] | Tag value. | [Table 3. Key Value \[cmdb_key_value\]] {#azure-event-grid-pattern__table_axq_spc_y2c} *[\>]: and then