Integrations · NoSQL · Available now

Azure Cosmos DB test data, inside your network

Azure Cosmos DB for NoSQL connector (azure-cosmos): container discovery, field shapes inferred from a bounded sample inside your network, partition-key-aware keys, RU-budgeted paged queries and nested items carried as JSON text.

Available now NoSQL

Shipped in the standard agent and backed by recorded conformance evidence.

Azure Cosmos DB has no foreign keys. DataNivra cannot discover relationships from Azure Cosmos DB: they come from an industry pack’s relationship mappings or relationships you declare. Without declared relationships, subsets do not follow relationships and the orphan check cannot cover them.

The console warns before a build that has none, and the certificate records RELATIONSHIPS_NOT_DECLARED for that source instead of reporting zero orphans as a check.

What works today

Azure Cosmos DB for NoSQL connector (azure-cosmos): container discovery, field shapes inferred from a bounded sample inside your network, partition-key-aware keys, RU-budgeted paged queries and nested items carried as JSON text.

Read-only account key as a secret reference; https endpoints are verified (plain http only for a loopback emulator). Queries page with continuation tokens under a request-unit budget and 429 responses back off.

Authentication: read-only account key (secret reference).

Known limitations

  • Run against one real Azure Cosmos DB for NoSQL account (provisioned throughput, single region) and the Linux emulator; serverless, autoscale and multi-region accounts are untested.
  • Requires agent 0.4.0 or later; earlier agent images do not include the azure-cosmos driver.
  • API for NoSQL only; account keys only (Microsoft Entra ID data-plane roles are not supported).
  • Read-only access is attested, not verified.
  • Fields are inferred from a bounded sample; a later item whose field type differs stops the read with FIELD_TYPE_DRIFT.
  • Cosmos DB declares no relationships: they come from industry packs or explicit mappings.

Capability matrix

Each capability is tracked separately and shown at the level the recorded conformance evidence supports. A connector that only discovers metadata is never presented as equivalent to one that runs the whole workflow.

Capabilities of Azure Cosmos DB
CapabilityLevel
DiscoverySupported
ClassificationSupported
ProfilingSupported
MaskingSupported
Deterministic maskingSupported
Entity-aware subsettingSupported
Relationship preservationSupported
Synthetic workflowsSupported
CertificationSupported
ProvisioningSupported
CI/CDSupported
Evidence generationSupported

Read-only proof

Attested: Cosmos DB cannot tell a read-only key from a read-write key without attempting a write, which the connector never does. Use one of the account's read-only keys and attest it; without the attestation the source is refused.

Conformance evidence

DataNivra runs every connector through a common conformance kit on synthetic data: no write statements, proven read-only access, secret redaction, schema and relationship discovery, bounded streaming, cancellation, clear reason codes, egress canaries and no raw values in logs, then the discover, mask, subset, certify and provision workflow. The published status is computed from those results.

Environments whose conformance run met the preview minimum
Engine or serviceVersionEnvironmentDriverAuthenticationVerified on
Azure Cosmos DB for NoSQLservicemanaged-serviceazure-cosmos 4.17.1read-only account key (attested)2026-10-12

Connector version 0.1.0, last verified 2026-10-12.

What crosses the boundary

Connectors run inside the agent in your network. Only metadata, aggregates and evidence reach DataNivra Cloud:

  • Schema, table and column names and data types (for file sets, operator-declared or opaque table names — never data-derived file names).
  • Aggregates such as row-count estimates, null and distinct ratios; counts from 1 to 10 are reported as 10 (small-cell protection).
  • Classification findings (which column looks like which kind of sensitive data) and relationship metadata.
  • Evidence metadata: checksums, gate outcomes, engine and policy versions, and templated error codes.

Never sent:

  • Any cell value, row, sample, minimum/maximum or top-k value — masked or not.
  • Credentials, connection strings or resolved secret values: DataNivra stores only the secret reference.
  • Free text copied from your data, or exception messages that contain values.

See the customer-resident architecture and how to verify these claims yourself.

Setup outline

  1. Use agent 0.4.0 or later: the standard agent image includes the Cosmos DB driver (azure-cosmos).
  2. Copy one of the account’s read-only keys into your secret store (Keys → Read-only keys, or az cosmosdb keys list --type read-only-keys). Never use a primary or secondary read-write key.
  3. Cosmos DB cannot tell a read-only key from a read-write key without writing, so you attest it with "read_only_attested": true; without the attestation the source is refused. HTTPS with certificate verification is the default.
  4. In the console, register the source with the secret reference of that document (for example vault://tdm/source-connection) and the agent that can reach it, then run discovery.
  5. The agent runs connector-generated SELECT queries only, pages them under a request-unit budget and infers field shapes from a bounded sample read inside your network. Relationships come from an industry pack or an explicit mapping.

Example connection document, stored in your secret store and resolved by the agent locally (DataNivra only ever sees its reference):

{
  "kind": "AZURE_COSMOS_DB",
  "endpoint": "https://example-account.documents.azure.com:443/",
  "databases": ["enrollment", "claims"],
  "account_key_ref": "azure-kv://kv-tdm/claims-cosmos-readonly-key",
  "read_only_attested": true,
  "key_fields": { "enrollment.members": ["member_id"] }
}

Next: install the agent, then follow the getting started guide.

All integrations · NoSQL test data management · Guides · Start free