--- 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 Hub Namespace # Azure Event Hub Namespace 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 Event Hub Namespace pattern-based discovery The Azure Event Hub Namespace pattern-based discovery enables ServiceNow customers to automatically discover and map Azure Event Hub Namespace resources within their cloud environment. This discovery populates data both in the Configuration Management Database (CMDB) and non-CMDB tables, facilitating comprehensive visibility and management of these Azure resources. The pattern is part of the Discovery and Service Mapping Patterns application in ServiceNow, requiring activation and proper configuration to operate effectively. Show full answer Show less ## Key Features * **Pattern Activation:** The Azure Event Hub Namespace discovery pattern is disabled by default and must be enabled manually. Starting with Visibility Content version 6.28.0, enabling or disabling patterns does not count as customization, and patterns will update to the latest predefined version after upgrades. * **Prerequisites:** Customers must meet Microsoft Azure discovery prerequisites and configure Azure service accounts correctly, especially for Azure GovCloud (US) environments, which require specific datacenter URLs. * **Data Storage:** * Non-CMDB tables store detailed Azure-specific resource attributes when running the extended inventory pattern. * CMDB tables hold key configuration items representing cloud messaging services. * **Tag Collection:** The pattern collects Azure tags and stores them in the Key Value table for enhanced resource metadata management. * **CI Relationships:** The discovery creates relationships between the Event Hub Namespace, resource groups, cloud messaging services, and Azure datacenters to support accurate mapping and service management. ## Data and Configuration Details The discovery populates important fields such as resource kind, location, TLS version, provisioning state, public network access, subscription and tenant IDs, and configuration item references. In the CMDB, it captures install and operational status, resource type, and unique identifiers, enabling customers to track and manage Azure Event Hub Namespace resources effectively. ## Practical Benefits By leveraging this pattern-based discovery, ServiceNow customers can automate the detection and mapping of Azure Event Hub Namespace resources, ensuring up-to-date and accurate CMDB data. This supports better operational insights, compliance tracking, and cloud resource management within the ServiceNow platform. 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-hub-namespace__section_ipy_53n_jfc} Verify the Microsoft Azure discovery prerequisites{#azure-event-hub-namespace__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-hub-namespace__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-hub-namespace__activating-disabled-pattern-not-customization} Configure the Discovery schedule to support GovCloud{#azure-event-hub-namespace__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-hub-namespace__configure-govcloud-azure-dd} {#azure-event-hub-namespace__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-hub-namespace__section_aq4_qkq_hfc} Discovery and Service Mapping Patterns application populates data in the non-CMDB table when running the Azure - Event Hub Namespace - 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-hub-namespace__section_aq4_qkq_hfc__entry__2} | Field | Description | |-|-| | Kind \[kind\] | The nature or subtype of the resource, often describing its specific role or variation. | | Location \[location\] | The geographical location where the resource is hosted. | | Minimum TLS Version \[minimum_tls_version\] | The minimum Transport Layer Security (TLS) version required by the resource for secure connections. | | Object Id \[object_id\] | The unique identifier of the resource. | | Provisioning State \[provisioning_state\] | The current status of the resource provisioning process. | | Public Network Аccess \[public_network_access\] | Indicates whether the resource can be accessed via the public network. | | Resource Group \[resource_group\] | Name of the resource group. | | Subscription ID \[subscription_id\] | The subscription ID. | | Tenant ID \[tenant_id\] | The identifier of the Azure Active Directory tenant. | | Configuration Item \[configuration_item\] | References the Cloud Messaging Service \[cmdb_ci_cloud_messaging_service\] table. | [Table 1. Azure Event Hub - Namespace \[cmdb_azure_event_hub_namespace\]] ## Data stored in CMDB tables Discovery and Service Mapping Patterns application populates data in the CMDB when running the Azure - Event Hub Namespace - Extended Inventory(LP) pattern. {#azure-event-hub-namespace__entry__24} | Field | Description | |-|-| | Install Status \[install_status\] | Install status of the resource. Default value is Installed. | | Location \[location\] | The geographical location where the resource is hosted. | | Name \[name\] | The name given 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. | | Type \[type\] | Type of resource. The value is set to microsoft.eventhub/namespaces. | [Table 2. Cloud Messaging Service \[cmdb_ci_cloud_messaging_service\]] ## CI relationships The pattern creates these relationships to support discovery. {#azure-event-hub-namespace__entry__39} | 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 Hub - Namespace \[cmdb_azure_event_hub_namespace\] | References | Cloud Messaging Service \[cmdb_ci_cloud_messaging_service\] | [ ] ## Azure tag discovery {#azure-event-hub-namespace__section_ezc_jwt_jfc} The pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table. {#azure-event-hub-namespace__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-hub-namespace__table_axq_spc_y2c} *[\>]: and then