--- 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 Cosmos DB for PostgreSQL Cluster # Azure Cosmos DB for PostgreSQL Cluster 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 Cosmos DB for PostgreSQL Cluster pattern-based discovery This pattern-based discovery in ServiceNow is designed to identify and map Azure Cosmos DB for PostgreSQL Cluster resources within your cloud environment. It leverages the Discovery and Service Mapping Patterns application to automatically find and populate relevant configuration data in both CMDB and non-CMDB tables, helping you maintain accurate and up-to-date asset information. Show full answer Show less ## Key Features * **Pattern Activation:** The Azure Cosmos DB for PostgreSQL Cluster discovery pattern is disabled by default. Starting with Visibility Content version 6.28.0, enabling or disabling this pattern does not count as a customization and will be preserved through updates. Patterns reset to the latest version after upgrades, retaining their last active status. * **Prerequisites:** Ensure Microsoft Azure discovery prerequisites are met, including proper setup of Azure service accounts. For Azure GovCloud (US) accounts, configure discovery schedules with appropriate datacenter URLs. * **Data Collection:** The discovery pattern populates data into: * **Non-CMDB tables:** Extended inventory data is stored in specific Azure tables accessible under Configuration \> Azure. * **CMDB tables:** Key cluster details are stored in the Cloud DataBase Cluster \[cmdbciclouddbcluster\] table, including cluster ID, status, version, location, vendor, and operational state. * **CI Relationships:** The pattern establishes relationships between discovered clusters and their associated Azure resource groups and datacenters to reflect accurate infrastructure dependencies. * **Tag Discovery:** Azure tags are collected and stored in the Key Value \[cmdbkeyvalue\] table, enabling enhanced filtering and reporting capabilities. ## Key Outcomes * **Automated and comprehensive discovery** of Azure Cosmos DB for PostgreSQL Clusters aligned with ServiceNow's CMDB structure. * **Accurate mapping** of resource groups, clusters, and datacenter relationships for improved visibility and impact analysis. * **Support for Azure GovCloud environments** through configurable discovery schedules and service accounts. * **Consistent updates and pattern management** without manual customization overhead, ensuring continuous alignment with Azure service changes. * **Enhanced tagging information** for better asset categorization and lifecycle 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-cosmos-db-postgresql-cluster__selection_ipy_53n_jfc} 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 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-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://servicenow-prod.fluidtopics.net/R5W5GP640V_5uNIhVNRPCw "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://servicenow-prod.fluidtopics.net/wA59_lRoV_0PzpuODHnNjA "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