---
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 Event Hub Namespace

# Azure Event Hub Namespace 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 Event Hub Namespace pattern-based discovery

The Azure Event Hub Namespace pattern-based discovery enables ServiceNow customers to identify and map Azure Event Hub Namespace resources within their cloud environment.
This discovery uses patterns provided by the Discovery and Service Mapping Patterns application to populate configuration and inventory data into the CMDB and related non-CMDB tables, facilitating effective cloud resource management and visibility.
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. Activation or deactivation does not count as customization and patterns receive automatic updates.
* **Prerequisites and Permissions:** Users must verify REST API permissions and Azure discovery prerequisites, including removal of resources from the Resource Inclusion List to prevent duplicate discovery.
* **Azure GovCloud Support:** Discovery can be configured to support Azure GovCloud accounts by specifying the appropriate datacenter URL when setting up Azure service accounts.
* **Data Population:**
  * Populates detailed Azure Event Hub Namespace data into the *cmdbazureeventhubnamespace* non-CMDB table.
  * Populates related Cloud Messaging Service data into the *cmdbcicloudmessagingservice* CMDB table.
  * Collects Azure tags and stores them in the *cmdbkeyvalue* table for metadata management.
* **CI Relationships:** The pattern automatically creates relationships among resource groups, cloud messaging services, and Azure datacenters to support comprehensive service mapping.

## Data and Configuration Details

The discovery captures key fields such as resource kind, location, provisioning state, security configurations (like minimum TLS version and public network access), subscription and tenant IDs, and operational status. This detailed data supports accurate representation and management of Azure Event Hub Namespaces within ServiceNow.

## Practical Benefits for Customers

* Enables proactive visibility and management of Azure Event Hub Namespace resources within ServiceNow CMDB.
* Supports automated discovery workflows with minimal manual customization, ensuring up-to-date asset and service data.
* Improves cloud resource governance through detailed tagging and relationship mapping.
* Facilitates integration with Azure GovCloud environments, expanding discovery capabilities to government cloud regions.  
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-event-hub-namespace__section_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-event-hub-namespace__cloud-discovery-api-ph-short-prereq}

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 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-event-hub-namespace__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-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://www.servicenow.com/docs/aypCYVQdO8oFebLMLEI89g "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://www.servicenow.com/docs/XKQpJvxWTKNL58XCkRHVxA "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