Veeva Vault connector reference

Important

This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Azure Databricks previews.

This page provides technical reference information for the Veeva Vault connector.

Connection parameters

The following parameters are required when creating a Veeva Vault connection in Catalog Explorer:

Parameter	Description
Client ID	The Microsoft Entra ID Application (client) ID from the app registration.
Client Secret	The Microsoft Entra ID client secret value. If lost, generate a new one in Microsoft Entra ID — it cannot be retrieved after creation.
OAuth scope	The OAuth 2.0 scope included in the token request to the Microsoft Entra ID token endpoint. Typically set to <client_id>/.default to request all permissions pre-consented on the service principal.
Staging volume	The Unity Catalog volume used to cache downloaded Veeva archives between pipeline triggers. Format: catalog.schema.volume.
Token Endpoint	The Microsoft Entra ID OAuth 2.0 v2 token endpoint (for example, https://login.microsoftonline.com/{tenant-id}/oauth2/v2.0/token).
Vault DNS	Your Vault hostname, without https:// (for example, your-company.veevavault.com).
Vault Session ID URL	The Session ID URL from the Veeva OAuth 2.0 / OpenID Connect profile (for example, https://login.veevavault.com/auth/oauth/session/{profile-id}).

Data type mappings

The connector automatically transforms Veeva Vault data types to Delta-compatible types:

Veeva Vault type	Delta type
Number	DOUBLE
Boolean	BOOLEAN
Date	DATE
DateTime	TIMESTAMP
String	STRING
ID	STRING
LongText	STRING
Picklist	STRING
Object	STRING
Richtext	STRING

Note

id fields are always stored as STRING regardless of Veeva's declared type. This is required for Lakeflow Spark Declarative Pipelines's primary-key functionality to work correctly.

Supported objects

The connector supports ingestion from all Veeva Vault object types:

• Standard objects (__v)
• Custom objects (__c)
• System tables
• Audit trail tables

You can configure a pipeline to ingest specific objects or all objects from a Vault schema.