Connection configuration - Precisely Data Integrity Suite

Data Integrity Suite

Product
Spatial_Analytics
Data_Integration
Data_Enrichment
Data_Governance
Precisely_Data_Integrity_Suite
geo_addressing_1
Data_Observability
Data_Quality
dis_core_foundation
Services
Spatial Analytics
Data Integration
Data Enrichment
Data Governance
Geo Addressing
Data Observability
Data Quality
Core Foundation
ft:title
Data Integrity Suite
ft:locale
en-US
PublicationType
pt_product_guide
copyrightfirst
2000
copyrightlast
2026

This section provides you the details on various fields required to configure Azure Cosmos DB in Data Integrity Suite.

Field Description
Connection name Specifies a unique identifier for this data connection. This is a mandatory field used to distinguish between multiple connections to the same or different Azure Cosmos DB instances. Example: Default, Production-CosmosDB, Analytics-Connection
Description Allows you to provide contextual information about the purpose and scope of this connection. This is an optional field that helps document the connection's intended use. Example: Connection to production Azure Cosmos DB for customer data profiling and quality assessment
Agent to access data Specifies the agent responsible for accessing the Azure Cosmos DB instance. Select from the dropdown list of available agents. If your data is in the cloud, select "None". For on-premise or private network access, select the appropriate agent. Example: None, On-Premise-Agent-01
Host Specifies the Azure Cosmos DB account endpoint URL. This is a mandatory field. The host should be the fully qualified domain name of your Cosmos DB account. Example: mycosmosdb.documents.azure.com
Database Specifies the name of the database within the Azure Cosmos DB account to connect to. This is a mandatory field. Each Cosmos DB account can contain multiple databases. Example: customer_database, analytics_db, product_catalog