Create a Veeva Vault connection

Important

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

Create a Veeva Vault connection in Catalog Explorer to store authentication credentials for Lakeflow Connect ingestion. Any user with the USE CONNECTION privilege on the connection can then create Veeva Vault ingestion pipelines without needing direct access to the credentials.

Alternatively, admin users can create a connection and a pipeline at the same time in the data ingestion UI. See Ingest data from Veeva Vault.

For privilege requirements, see Connect to managed ingestion sources.

Prerequisites

Complete Configure Veeva Vault for OAuth 2.0 M2M authentication. Use the authentication details you obtain to create the connection.

You also need a Unity Catalog volume to use as staging storage for downloaded Veeva archives between pipeline runs. Create a volume in Catalog Explorer before proceeding. For details, see What are Unity Catalog volumes?.

Create a connection

  1. In the Azure Databricks workspace, click Data icon. Catalog > Create > Create a connection.
  2. On the Connection basics page of the Set up connection wizard, specify a unique Connection name.
  3. In the Connection type drop-down menu, select Veeva Vault.
  4. (Optional) Add a comment.
  5. Click Next.
  6. On the Authentication page, specify the following:
    • Client ID: The Microsoft Entra ID Application (client) ID from the app registration. Obtain this from the source setup.
    • 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 for 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. Use the 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). Obtain this from the source setup.
    • 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}). Obtain this from the source setup.
  7. Click Create connection.

Next steps

Ingest data from Veeva Vault.

  • Last updated on