Workday Activity Logging connector

Important

This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Workday Activity Logging from the Previews page. See Manage Azure Databricks previews.

The managed Workday Activity Logging connector in Lakeflow Connect ingests user activity log events from Workday into Azure Databricks.

Feature availability

Feature	Availability
UI-based pipeline authoring	Not supported
API-based pipeline authoring	Supported
Declarative Automation Bundles	Supported
Incremental ingestion	Supported
Unity Catalog governance	Supported
Orchestration using Databricks Workflows	Supported
API-based column selection and deselection	Supported
API-based row filtering	Not supported
SCD Type 2	Not supported
Automated schema evolution: New and deleted columns	Supported
Automated schema evolution: Data type changes	Not supported
Automated schema evolution: Column renames	Supported Treated as a new column (new name) and deleted column (old name).

Authentication methods

Authentication method	Availability
OAuth refresh token	Supported
OAuth U2M	Not supported
OAuth M2M	Not supported
Basic authentication (username/password)	Not supported

What to know before you start

Note

Before starting, review the Azure Databricks user persona, supported interfaces, ingestion frequency, and common patterns.

Start ingesting from Workday

1. Configure Workday for ingestion (Admins). Enable activity logging and create an integration system user, security group, OAuth client, and refresh token.
2. Create a Unity Catalog connection (Admins). Create a connection in Catalog Explorer so non-admins can create pipelines.
3. Create an ingestion pipeline (Admins or non-admins). Use Declarative Automation Bundles or a Databricks notebook to create a pipeline from an existing connection.