Azure Blob Storage / Data Lake Storage test data, inside your network

What works today

Built-in file-set connector for Parquet or CSV files in an Azure Blob container or ADLS Gen2 filesystem, with account-key, SAS or service-principal authentication.

Grant the identity only the Storage Blob Data Reader role on the container.

Authentication: account key; SAS token; service principal.

Known limitations

• Verified against a real Azure Storage account with hierarchical namespace (Data Lake Storage Gen2) using a read + list SAS; account-key and service-principal authentication were verified against Azurite, Microsoft's local emulator, only.
• SAS tokens as copied from the Azure portal or CLI (without a leading '?') need agent 0.2.0 or later; agent 0.1.0 accepts them only with the leading '?'.
• Read-only access cannot be proven for object stores: it is attested by the operator, and the source is refused without that attestation.

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.

Read-only proof

Read-only access is by operator attestation (read_only_attested); without it the check fails closed.

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.

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

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. Grant the service principal (or SAS) read access only, for example the Storage Blob Data Reader role on the container.
2. Read-only access is by your attestation: set read_only_attested once the role assignment is in place.
3. Store the connection document with the client secret, account key or SAS token as a secret reference, or omit credentials so the agent uses the default Azure credential of its host (for example a managed identity).
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.

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

{
  "kind": "AZURE_BLOB",
  "account_name": "tdmextractsexample",
  "container": "exports",
  "prefix": "claims/",
  "format": "parquet",
  "tenant_id": "00000000-0000-0000-0000-000000000000",
  "client_id": "00000000-0000-0000-0000-000000000000",
  "client_secret_ref": "vault://tdm/adls-reader#client_secret",
  "read_only_attested": true
}

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