---
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 Topic

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

This documentation describes how the Azure Service Bus Topic discovery pattern works within the ServiceNow Discovery and Service Mapping Patterns application.
It enables automated identification and mapping of Azure Service Bus Topic resources in your cloud environment, populating data into both CMDB and non-CMDB tables to provide comprehensive visibility and management of these cloud assets.
Show full answer Show less  

## Key Requirements and Setup

* **REST API Permissions:** Ensure correct permissions by referencing the Cloud Discovery patterns spreadsheet, which lists required user permissions, pattern names, CI classes, and vendor documentation. Keep this spreadsheet updated quarterly.
* **Azure Discovery Prerequisites:** Follow Microsoft Azure discovery prerequisites to guarantee smooth pattern execution.
* **Resource Inclusion List:** Verify that Azure Service Bus Topic resources are not listed in the Resource Inclusion List table to prevent duplicate discoveries.
* **Pattern Activation:** The Azure Service Bus Topic pattern is disabled by default. You must enable it manually. Activating or deactivating patterns no longer counts as customization from version 6.28.0 onward, allowing patterns to receive updates seamlessly.
* **Discovery Scheduling for GovCloud:** For discovering Azure GovCloud (US) accounts, configure the Azure service account with the appropriate datacenter URL.

## Data Storage and Tables

The discovery populates data into two types of tables:

* **Non-CMDB Tables:** When running the *Azure - Service Bus Topic - Extended Inventory(LP)* pattern, detailed topic attributes such as batched operations, partitioning, location, message size limits, subscription count, and resource group are stored in non-CMDB tables. These tables can be accessed via the Azure configuration section in the navigation.
* **CMDB Tables:** The same pattern also populates core cloud topic information into CMDB tables, including install status, operational status, location, name, description, and the unique object ID.

## Key Configuration Item (CI) Relationships

The pattern establishes relationships to support discovery and mapping, linking the Azure Service Bus Topic resource to:

* Cloud Topic CI
* Resource Group CI
* Azure Datacenter CI

These relationships enable a clear understanding of the topic's placement and context within the Azure cloud environment.

## Benefits for ServiceNow Customers

* Automates discovery and accurate CMDB population of Azure Service Bus Topics, improving visibility and governance.
* Keeps discovery patterns current and manageable without customization conflicts.
* Supports comprehensive cloud asset management by integrating Azure-specific details and relationships into your CMDB.
* Enables discovery across different Azure regions, including GovCloud, with proper configuration.  
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-topic__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-topic__cloud-discovery-api-ph-short-prereq}

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

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

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

| Field | Description |
|-|-|
| Enable Batched Operations \[enable_batched_operations\] | Indicates whether batched operations are enabled for the topic. |
| Enable Partitioning \[enable_partitioning\] | Specifies if the topic is partitioned to support scalability. |
| DC Location \[location\] | The geographical region where the topic is deployed. |
| Max Message Size In KB \[max_message_size_in_kb\] | The maximum size of any message that can be sent to the topic, measured in kilobytes (KB). |
| Max Size In MB \[max_size_in_mb\] | The maximum storage limit for the topic in megabytes (MB). |
| Object Id \[object_id\] | The unique identifier for the topic resource. |
| Status \[status\] | The status of the topic resource. For example: Active or Disabled. |
| Subscription Count \[subscription_count\] | The number of active subscriptions associated with the topic. |
| Resource Group \[resource_group\] | Name of the resource group. |
| Subscription ID \[subscription_id\] | The subscription ID. |
| Configuration Item \[configuration_item\] | References the Cloud Topic \[cmdb_ci_cloud_topic\] table. |
[Table 1. Azure Service Bus - Topic \[cmdb_azure_service_bus_topic\]]

## Data stored in CMDB tables

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

| Field | Description |
|-|-|
| Install Status \[install_status\] | Install status of the resource. Default value is Installed. |
| Location \[location\] | The geographical region where the topic is deployed. |
| Name \[name\] | The name of the topic within the Service Bus namespace. |
| Object ID \[object_id\] | The unique identifier of the resource in the following format: /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}/topics/{topicName} |
| Operational status \[operational_status\] | Operational status of the resource. Default value is Operational. |
| Description \[short_description\] | Description of the resource or service. |
[Table 2. Cloud Topic \[cmdb_ci_cloud_topic\]]

## CI relationships

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

| CI | Relationship | CI |
|-|-|-|
| Cloud Resource \[cmdb_ci_cmp_resource\] | Contains::Contained by | Cloud Topic \[cmdb_ci_cloud_topic\] |
| Resource Group \[cmdb_ci_resource_group\] | Contains::Contained by | Cloud Topic \[cmdb_ci_cloud_topic\] |
| Cloud Topic \[cmdb_ci_cloud_topic\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] |
| Azure Service Bus - Topic \[cmdb_azure_service_bus_topic\] | References | Cloud Topic \[cmdb_ci_cloud_topic\] |
[ ]

*[\>]: and then