---
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 Cosmos DB for PostgreSQL Cluster

# Azure Cosmos DB for PostgreSQL Cluster 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 Cosmos DB for PostgreSQL Cluster pattern-based discovery

The Azure Cosmos DB for PostgreSQL Cluster pattern-based discovery enables ServiceNow customers to automatically discover and map Azure Cosmos DB for PostgreSQL Cluster resources within their Microsoft Azure cloud environments.
This process uses Discovery and Service Mapping Patterns to populate data into both CMDB and non-CMDB tables, ensuring comprehensive visibility and accurate configuration management of these Azure services.
Show full answer Show less  

## Key Features

* **Pattern Activation:** The discovery pattern for Azure Cosmos DB for PostgreSQL Cluster is disabled by default. Starting from Visibility Content version 6.28.0, enabling or disabling patterns does not count as customization, and patterns receive ongoing updates. Previously customized patterns reset to the latest version upon upgrade while retaining their last active state.
* **Data Collection:** The discovery populates detailed resource data into non-CMDB Azure tables (such as `cmdbazurecosmosdbforpostgresqlclustercluster`) and CMDB tables (notably `cmdbciclouddbcluster`), capturing essential attributes like resource IDs, provisioning and operational status, cluster version, location, and vendor information.
* **CI Relationships:** The pattern establishes relationships among configuration items (CIs) to reflect resource group containment, hosting datacenter, and references between Azure Cosmos DB clusters and Cloud Database Clusters, supporting accurate service mapping.
* **Tag Discovery:** Azure resource tags are collected and stored in the `cmdbkeyvalue` table, allowing for enhanced categorization and filtering of resources.
* **Governance and Permissions:** Proper REST API permissions must be granted based on guidelines provided in the Cloud Discovery patterns spreadsheet, which should be periodically updated to include new patterns released quarterly.
* **Microsoft Azure Prerequisites:** Customers must verify Azure discovery prerequisites and ensure relevant resources are removed from the Resource Inclusion List to prevent duplicate discoveries.
* **GovCloud Support:** The discovery process supports Azure GovCloud (US) environments by requiring appropriate datacenter URLs when configuring Azure service accounts.

## What Customers Can Expect

* Automated, accurate discovery of Azure Cosmos DB for PostgreSQL Clusters integrated into the ServiceNow CMDB and related tables.
* Up-to-date data reflecting resource provisioning states, cluster statuses, and operational conditions to support IT service management and cloud governance.
* Clear visibility into resource relationships, enabling better impact analysis and service mapping within the Azure cloud environment.
* Enhanced tagging information to facilitate resource categorization and reporting.
* Ongoing pattern updates delivered through regular Visibility Content releases, ensuring the discovery stays current with Azure service changes.  
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-cosmos-db-postgresql-cluster__selection_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-cosmos-db-postgresql-cluster__cloud-discovery-api-ph-short-prereq}

Verify the Microsoft Azure discovery prerequisites{#azure-cosmos-db-postgresql-cluster__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-cosmos-db-postgresql-cluster__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-cosmos-db-postgresql-cluster__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-cosmos-db-postgresql-cluster__activating-disabled-pattern-not-customization}

Configure the Discovery schedule to support GovCloud{#azure-cosmos-db-postgresql-cluster__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-cosmos-db-postgresql-cluster__configure-govcloud-azure-dd}
{#azure-cosmos-db-postgresql-cluster__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-cosmos-db-postgresql-cluster__section_aq4_qkq_hfc}

Discovery and Service Mapping Patterns application populates data in the non-CMDB table when running the Azure - Cosmos DB for PostgreSQL Cluster - 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-cosmos-db-postgresql-cluster__section_aq4_qkq_hfc__entry__2}

| Field | Description |
|-|-|
| Object Id \[object_id\] | The unique identifier of the resource. |
| Kind \[kind\] | The specific kind or stock-keeping unit (SKU) of the resource. |
| DC Location \[location\] | The Azure region where the resource is deployed. |
| Resource Group \[resource_group\] | The name of the Azure resource group containing the resource. |
| Subscription Id \[subscription_id\] | The unique identifier for the Azure subscription. |
| Tenant Id \[tenant_id\] | The universally unique identifier (UUID) of the Azure Active Directory tenant associated with the resource. |
| Provisioning State \[provisioning_state\] | The current state of the provisioning process for the resource. |
| Configuration Item \[configuration_item\] | References the Cloud DataBase Cluster \[cmdb_ci_cloud_db_cluster\] table. |
[Table 1. Azure Cosmos DB for PostgreSQL Cluster \[cmdb_azure_cosmos_db_for_postgresql_cluster_cluster\]]

## Data stored in CMDB tables

Discovery and Service Mapping Patterns application populates data in the CMDB when running the Azure - Cosmos DB for PostgreSQL Cluster - Extended Inventory(LP) pattern.  
{#azure-cosmos-db-postgresql-cluster__entry__20}

| Field | Description |
|-|-|
| Name \[name\] | The name assigned to the resource. |
| Location \[location\] | The Azure region where the resource is deployed. |
| Cluster ID \[cluster_id\] | The unique identifier of the resource. |
| Cluster Status \[cluster_status\] | The current operational status of the cluster. |
| Cluster Version \[cluster_version\] | The version number of the cluster software. |
| Install Status \[install_status\] | Install status of the resource. Default value is Installed. |
| Operational status \[operational_status\] | Operational status of the resource. Default value is Operational. |
| Description \[short_description\] | Type of resource. The value is set to microsoft.dbforpostgresql/servergroupsv2. |
| Vendor \[vendor\] | Name of vendor: Microsoft. |
[Table 2. Cloud DataBase Cluster \[cmdb_ci_cloud_db_cluster\]]

## CI relationships

The Azure - Cosmos DB for PostgreSQL Cluster - Extended Inventory(LP) pattern creates these relationships to support Azure Cosmos DB for PostgreSQL Cluster discovery.  
{#azure-cosmos-db-postgresql-cluster__entry__41}

| CI | Relationship | CI |
|-|-|-|
| Resource Group \[cmdb_ci_resource_group\] | Contains::Contained by | Cloud DataBase Cluster \[cmdb_ci_cloud_db_cluster\] |
| Cloud DataBase Cluster \[cmdb_ci_cloud_db_cluster\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] |
| Azure Cosmos DB for PostgreSQL Cluster \[cmdb_azure_cosmos_db_for_postgresql_cluster_cluster\] | References | Cloud DataBase Cluster \[cmdb_ci_cloud_db_cluster\] |
[ ]

## Azure tag discovery {#azure-cosmos-db-postgresql-cluster__section_ezc_jwt_jfc}

The pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table. {#azure-cosmos-db-postgresql-cluster__table_axq_spc_y2c__entry__2}

| Field | Description |
|-|-|
| Key \[key\] | Tag name. |
| Value \[value\] | Tag value. |
[Table 3. Key Value \[cmdb_key_value\]]

{#azure-cosmos-db-postgresql-cluster__table_axq_spc_y2c}

*[\>]: and then