Databricks Integrates Workday Data into Unity Catalog
Databricks has released a public beta of its Workday Data Connect connector, enabling zero-copy access to HR and financial data directly within the Unity Catalog governance framework.

Databricks has launched the public beta of its Workday Data Connect federation connector for Unity Catalog. This integration allows data teams to access Workday HR and financial data directly from cloud storage without setting up ingestion pipelines or generating duplicate data. Built on the partnership established at Workday Rising 2025, this tool makes Databricks one of the first launch partners to offer native federation capabilities for the Workday Data Cloud.
The connector functions through catalog federation rather than standard query federation. Instead of pushing queries to an external database, Databricks retrieves table metadata from Workday's Iceberg REST catalog. Databricks compute then reads the shared Iceberg tables directly from Workday's managed object storage to execute queries. This zero-copy, read-only setup ensures that Workday remains the absolute system of record. Administrators can govern this external data using Unity Catalog to apply catalog, schema, and table-level permissions, while tracking lineage and auditing.
For practitioners, this integration simplifies the process of combining workforce and financial metrics with other enterprise data. Users can query the federated catalog using standard SQL or natural-language tools like Databricks Genie to analyze headcount trends, attrition, and financial planning. To deploy the connector, organizations need a Unity Catalog-enabled workspace running Databricks Runtime 19 or above, and a workspace administrator must enable the feature from the Previews page.
This federation connector represents one of three native pathways Databricks now offers for Workday integration. While the new federation connector is designed for querying data in place, teams can also use Lakeflow Connect for incremental ingestion into Delta tables when historical tracking is required. Alternatively, they can use a JDBC connection for real-time, ad-hoc lookups via Live Data Query.
This is our own summary of reporting by Databricks AI



