Azure Event Hub Namespace pattern-based discovery

  • Release version: Xanadu
  • Updated June 16, 2026
  • 2 minutes to read
    • Summarize
    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 discover and map Azure Event Hub Namespace resources within their cloud environments. This discovery is part of the Discovery and Service Mapping Patterns application, which identifies Azure services and populates relevant data into both CMDB and non-CMDB tables. It requires specific Azure prerequisites and configuration to operate effectively, especially for environments like Azure GovCloud (US).

    Show full answer Show less

    Key Features

    • Pattern Activation: The discovery pattern for Azure Event Hub Namespace is disabled by default. Starting from Visibility Content version 6.28.0, enabling or disabling patterns is streamlined and retains the latest updates without being treated as a customization.
    • Discovery Scope: Supports discovery of Azure Event Hub Namespace resources including extended inventory data, accommodating both standard Azure and Azure GovCloud environments.
    • Data Storage: Populates data into:
      • Non-CMDB tables: For example, the cmdbazureeventhubnamespace table includes detailed attributes such as kind, location, TLS version, provisioning state, public network access, resource group, subscription ID, tenant ID, and references to Cloud Messaging Service CIs.
      • CMDB tables: Such as the cmdbcicloudmessagingservice table, which holds install status, location, name, object ID, operational status, and resource type.
    • CI Relationships: The pattern establishes relationships between configuration items including resource groups, cloud messaging services, and Azure datacenters to provide a comprehensive service map.
    • Tag Discovery: Azure resource tags are collected and stored in the cmdbkeyvalue table, enabling enhanced metadata management.

    Practical Implementation

    • Prerequisites: Ensure Microsoft Azure discovery prerequisites are met, including setting up Azure service accounts with datacenter URLs when working with GovCloud accounts.
    • Pattern Activation: Enable the Azure Event Hub Namespace discovery pattern to start collecting data; patterns reset to latest predefined versions after upgrades but retain activation status.
    • Discovery Scheduling: Configure schedules appropriately to support continuous and accurate discovery aligned with your cloud environment's operational needs.

    Key Outcomes

    • Accurate and up-to-date discovery of Azure Event Hub Namespace resources within your cloud infrastructure.
    • Comprehensive visibility into resource attributes, operational status, and relationships, enabling better management and troubleshooting.
    • Integration of Azure-specific metadata, including tags, to enhance asset management and reporting capabilities in ServiceNow CMDB.
    • Support for complex environments such as Azure GovCloud with appropriate configuration guidance.

    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

    Verify the Microsoft Azure discovery prerequisites
    For more information, see the prerequisites section in Microsoft Azure Cloud components discovery using patterns.
    Enable the relevant pattern
    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.
    Configure the Discovery schedule to support GovCloud
    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.

    Discovery and Service Mapping Patterns application populates data in both CMDB and non-CMDB tables.

    Data stored in non-CMDB tables

    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 All > Configuration > Azure. You can also search the navigation filter for the specific pattern name.

    Table 1. Azure Event Hub - Namespace [cmdb_azure_event_hub_namespace]
    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.

    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.

    Table 2. Cloud Messaging Service [cmdb_ci_cloud_messaging_service]
    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.

    CI relationships

    The pattern creates these relationships to support discovery.

    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

    The pattern collects tags and populates them in the Key Value [cmdb_key_value] table.
    Table 3. Key Value [cmdb_key_value]
    Field Description
    Key [key] Tag name.
    Value [value] Tag value.