Databricks has introduced the beta release of the Workday Data Connect federation connector for Unity Catalog, allowing enterprise data teams to directly query Workday HR and finance data in place without duplications. This innovation combines trusted source data with Databricks’ Data + AI platform, offering a governed, unified experience for analytics and AI development.
- Zero-copy federation enables real-time access to Workday HR and finance data.
- Unity Catalog enforces consistent, fine-grained governance and auditing for federated data.
- Supports flexible data usage patterns: live queries, durable copies, and on-demand lookups.
Infrastructure signal
The Workday Data Connect federation connector leverages Unity Catalog's catalog federation to access Workday Data Cloud's Iceberg tables directly from their native cloud storage. This new approach eliminates data duplication by removing ingestion pipelines and enabling read-only, zero-copy queries that preserve Workday as the single system of record. Databricks compute executes the queries locally while Workday handles the storage and metadata through Iceberg REST catalogs.
From an infrastructure perspective, this change reduces cloud storage costs related to data replication and ingestion processing. It also simplifies data management by compressing multiple data access methods into a unified federated model governed by Unity Catalog. By accessing live data rather than snapshots, organizations can improve query freshness and operational efficiency while maintaining secure, governed access controls built into the underlying cloud infrastructure.
Developer impact
Developers and analysts benefit from immediate, governed access to Workday HR and finance data alongside enterprise datasets without needing to maintain ETL pipelines or local copies. They can query federated Workday data through Databricks SQL, AI-powered notebooks, and BI tools such as Databricks Genie, enabling faster exploration and data-driven decision-making with fresh data.
With three complementary data access methods available—federated live views, durable copies for historical reporting, and on-demand lookups—development teams can select optimal strategies based on use case. Integration with Unity Catalog also improves observability and auditability across federated datasets, ensuring data lineage and governance compliance remain transparent throughout the workflow.
What teams should watch
Cloud platform, data engineering, and governance teams should prioritize enabling the Workday Data Connect federation in Unity Catalog, especially if they seek to unify Workday data with broader enterprise analytics without increasing storage costs or operational complexity. Attention should be given to coordinating between Workday and Databricks workspace administrators to enable the feature in Beta, noting requirements for Unity Catalog activation and Databricks Runtime version 19 or higher.
Security teams and data governance leads must evaluate and extend catalog-, schema-, and table-level permission policies via Unity Catalog to secure federated Workday data. Observability and auditing capabilities should be incorporated into existing workflows to track query activity and data lineage. Additionally, teams planning historical analysis or slowly changing dimensions should continue leveraging Lakeflow Connect ingestion connectors for durable, versioned Workday data copies.