---
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 Service Bus Namespace

# Azure Service Bus Namespace pattern-based discovery {#ariaid-title1}

Release version: Australia  
Updated March 12, 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 Service Bus Namespace pattern-based discovery

The Azure Service Bus Namespace pattern-based discovery enables ServiceNow customers to identify and map Azure Service Bus namespaces within their cloud environments.
This functionality is part of the Discovery and Service Mapping Patterns application, which requires the latest version to ensure accurate detection of Azure services.
The discovery process populates data into both CMDB and non-CMDB tables, supporting comprehensive infrastructure visibility and management.
Show full answer Show less  

## Key Configuration and Requirements

* **REST API Permissions:** Customers must grant appropriate REST API permissions based on details available in the Cloud Discovery patterns spreadsheet, which is updated quarterly and includes pattern names, CI classes, and vendor documentation.
* **Azure Discovery Prerequisites:** Verify prerequisites specific to Microsoft Azure Cloud discovery to ensure successful pattern execution.
* **Resource Inclusion List:** Remove relevant Azure Service Bus namespace resources from the Resource Inclusion List table to prevent duplicate discoveries.
* **Pattern Activation:** The Azure Service Bus Namespace pattern is disabled by default and must be enabled. Activating or deactivating patterns is now non-customizing and patterns reset to the latest version after upgrades while preserving activation status.
* **GovCloud Support:** For Azure GovCloud accounts, configure discovery schedules with datacenter URLs when setting up Azure service accounts to enable proper discovery.

## Data Storage and Tables

The discovery process populates data across several tables to capture detailed resource information:

* **Non-CMDB Tables:** The *Azure - Service Bus Namespace - Extended Inventory (LP)* pattern stores data in non-CMDB Azure tables accessible via ServiceNow navigation paths.
* **CMDB Tables:** The pattern populates the *cmdbazureservicebusnamespace* table with fields such as identity, location, object ID, resource group, status, subscription ID, and configuration item references.
* The *cmdbcicmpresource* table captures cloud resource details including install status, operational status, resource type (set as microsoft.servicebus/namespaces), location, name, object ID, and descriptions.
* **Tag Discovery:** Azure tags associated with the namespaces are collected and stored in the *cmdbkeyvalue* table, preserving tag names and values for enhanced metadata management.

## Configuration Item Relationships

The pattern establishes key relationships to support discovery and service mapping:

* **Resource Group:** Azure Service Bus namespaces are contained within resource groups.
* **Hosting:** Cloud resources are hosted on Azure datacenters.
* **References:** The Azure Service Bus Namespace entries reference corresponding cloud resource records, enabling integrated visibility across CMDB records.

## What Customers Can Expect

By implementing this pattern, ServiceNow customers gain automated discovery and mapping of Azure Service Bus namespaces, complete with detailed metadata, tags, and relationship mapping. This supports improved asset management, operational insight, and cloud governance within the ServiceNow platform.  
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-service-bus-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-service-bus-namespace__cloud-discovery-api-ph-short-prereq}

Verify the Microsoft Azure discovery prerequisites{#azure-service-bus-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-service-bus-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-service-bus-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-service-bus-namespace__activating-disabled-pattern-not-customization}

Configure the Discovery schedule to support GovCloud{#azure-service-bus-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-service-bus-namespace__configure-govcloud-azure-dd}
{#azure-service-bus-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-service-bus-namespace__section_aq4_qkq_hfc}

Discovery and Service Mapping Patterns application populates data in the non-CMDB table when running the Azure - Service Bus 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-service-bus-namespace__section_aq4_qkq_hfc__entry__2}

| Field | Description |
|-|-|
| Identity \[identity\] | The identity information associated with the resource, often used for authentication or access control. |
| Location \[location\] | The geographical location where the resource is hosted. |
| Object Id \[object_id\] | The unique identifier of the resource. |
| Resource Group \[resource_group\] | Name of the resource group. |
| Status \[status\] | The current status or state of the resource. |
| Subscription ID \[subscription_id\] | The subscription ID. |
| Configuration Item \[configuration_item\] | References the Cloud Resource \[cmdb_ci_cmp_resource\] table. |
[Table 1. Azure Service Bus - Namespace \[cmdb_azure_service_bus_namespace\]]

## Data stored in CMDB tables

Discovery and Service Mapping Patterns application populates data in the CMDB when running the Azure - Service Bus Namespace - Extended Inventory(LP) pattern.  
{#azure-service-bus-namespace__entry__18}

| 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 of 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. |
| Resource type \[resource_type\] | Type of resource. The value is set to microsoft.servicebus/namespaces. |
| Description \[short_description\] | Description of the resource or service. |
[Table 2. Cloud Resource \[cmdb_ci_cmp_resource\]]

## CI relationships

The pattern creates these relationships to support discovery.
{#azure-service-bus-namespace__entry__35}

| 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 Service Bus - Namespace \[cmdb_azure_service_bus_namespace\] | References | Cloud Resource \[cmdb_ci_cmp_resource\] |
[ ]

## Azure tag discovery {#azure-service-bus-namespace__section_ezc_jwt_jfc}

The pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table. {#azure-service-bus-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-service-bus-namespace__table_axq_spc_y2c}

*[\>]: and then