---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/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 Service Bus Namespace

# Azure Service Bus 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 Service Bus Namespace pattern-based discovery

Azure Service Bus Namespace pattern-based discovery enables ServiceNow customers to detect and map Azure Service Bus namespaces within their cloud environments using Discovery and Service Mapping Patterns.
This process helps maintain accurate and up-to-date CMDB data by automatically identifying Azure resources and their relationships.
Show full answer Show less  

## Key Features

* **Pattern Activation:** The Azure Service Bus Namespace discovery pattern is disabled by default and requires activation. Starting with Visibility Content version 6.28.0, enabling or disabling patterns is not considered a customization, ensuring patterns remain updatable after upgrades.
* **Discovery Schedule Configuration:** To discover Azure GovCloud (US) accounts, configuration must include the appropriate datacenter URL in the Azure service account setup.
* **Data Population:** The discovery pattern populates data in both CMDB and non-CMDB tables. Non-CMDB data is created when running the extended inventory pattern, and can be reviewed under Configuration \> Azure in the ServiceNow interface.
* **Azure Tag Collection:** Tags associated with Azure resources are collected and stored in the Key Value \[cmdbkeyvalue\] table, supporting better resource categorization and management.

## Data Model and Configuration Items (CIs)

The pattern captures detailed attributes of Azure Service Bus namespaces and stores them across specific tables:

* **Azure Service Bus Namespace \[cmdbazureservicebusnamespace\]:** Stores identity, location, object ID, resource group, status, subscription ID, and links to the Cloud Resource CI.
* **Cloud Resource \[cmdbcicmpresource\]:** Contains install status, location, name, object ID, operational status, resource type (set to microsoft.servicebus/namespaces), and description.

## Configuration Item Relationships

The pattern establishes essential relationships to depict resource hierarchy and hosting context:

* Resource groups contain Azure Service Bus Namespace cloud resources.
* Cloud resources are hosted on Azure datacenters.
* Namespaces reference the corresponding cloud resource CIs.

## Practical Implications for ServiceNow Customers

By enabling and configuring this discovery pattern, customers can achieve automated, accurate detection of Azure Service Bus namespaces, support compliance and operational visibility, and maintain a comprehensive CMDB with relational integrity. This facilitates improved cloud resource management and supports governance initiatives.  
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-service-bus-namespace__section_ipy_53n_jfc}

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 components discovery using patterns](https://www.servicenow.com/docs/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-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/R5W5GP640V_5uNIhVNRPCw "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/wA59_lRoV_0PzpuODHnNjA "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