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

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

The Azure Service Bus Queue pattern-based discovery in ServiceNow enables automated detection and mapping of Azure Service Bus Queues within your cloud environment.
This discovery is part of the Discovery and Service Mapping Patterns application, which helps populate both CMDB and non-CMDB tables with detailed information about Azure services.
This capability facilitates accurate asset and configuration management related to Azure Service Bus Queues.
Show full answer Show less  

## Key Features

* **Pattern Activation:** The Azure Service Bus Queue pattern is disabled by default and must be enabled to start discovery. From Visibility Content version 6.28.0 onward, activating or deactivating patterns will not be treated as customizations, ensuring they continue to receive updates after upgrades.
* **Discovery Prerequisites:** Proper Microsoft Azure discovery prerequisites must be met, including setting up Azure service accounts correctly. For Azure GovCloud (US), a datacenter-specific URL is required when configuring service accounts.
* **Data Population:** The discovery populates data in both CMDB and non-CMDB tables:
  * **Non-CMDB Tables:** Azure-specific tables store extended inventory details such as batching, partitioning, message size limits, location, resource group, subscription ID, and queue status.
  * **CMDB Tables:** Core configuration items (CIs) such as Cloud Messaging Service are populated with installation status, operational status, type, name, location, and unique identifiers.
* **CI Relationships:** The pattern creates critical relationships among discovered CIs to accurately reflect dependencies and hosting, including links between Service Bus Queues, Cloud Messaging Services, Resource Groups, and Azure Datacenters.

## Practical Benefits for ServiceNow Customers

* Enables comprehensive and up-to-date discovery of Azure Service Bus Queues for effective cloud asset management.
* Supports governance and operational oversight by providing detailed configuration and status data directly within the CMDB and related tables.
* Facilitates seamless upgrades and pattern maintenance without losing activation states, ensuring continuous discovery coverage.
* Improves service mapping accuracy by establishing clear CI relationships, which aids in impact analysis and change management.  
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-queue__section_ipy_53n_jfc}

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

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

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

| Field | Description |
|-|-|
| Enable Batched Operations \[enable_batched_operations\] | Indicates whether batched operations are enabled for the queue. |
| Enable Partitioning \[enable_partitioning\] | Indicates whether message partitioning is enabled for load distribution across multiple message brokers. |
| DC Location \[location\] | The geographic region where the Service Bus queue is deployed. |
| Max Message Size In KB \[max_message_size_in_kb\] | The maximum allowed size of a single message in kilobytes (KB). |
| Max Size In MB \[max_size_in_mb\] | The maximum storage size of the queue in megabytes (MB). |
| Object Id \[object_id\] | The unique identifier for the Service Bus queue. |
| Resource Group \[resource_group\] | Name of the resource group. |
| Subscription ID \[subscription_id\] | The subscription ID. |
| Status \[status\] | The current status of the Service Bus queue. |
| Configuration Item \[configuration_item\] | References the Cloud Messaging Service \[cmdb_ci_cloud_messaging_service\] table. |
[Table 1. Azure Service Bus - Queue \[cmdb_azure_service_bus_queue\]]

## Data stored in CMDB tables

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

| Field | Description |
|-|-|
| Install Status \[install_status\] | Install status of the resource. Default value is Installed. |
| Location \[location\] | The geographic region where the Service Bus queue is deployed. |
| Name \[name\] | The name of the Service Bus queue. |
| Object ID \[object_id\] | The unique identifier for the Service Bus queue. |
| Operational status \[operational_status\] | Operational status of the resource. Default value is Operational. |
| Type \[type\] | Type of resource. The value is set to Microsoft.ServiceBus/namespaces/queues. |
[Table 2. Cloud Messaging Service \[cmdb_ci_cloud_messaging_service\]]

## CI relationships

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

| CI | Relationship | CI |
|-|-|-|
| Cloud Resource \[cmdb_ci_cmp_resource\] | Contains::Contained by | Cloud Messaging Service \[cmdb_ci_cloud_messaging_service\] |
| 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 Service Bus - Queue \[cmdb_azure_service_bus_queue\] | References | Cloud Messaging Service \[cmdb_ci_cloud_messaging_service\] |
[ ]

*[\>]: and then