Our actuals data lives in Databricks Unity Catalog. I want to surface it in Fabric Plan without moving the data. OneLake shortcuts seem like the right mechanism. Has anyone done this successfully?
3 Replies
One thing to verify: Databricks Unity Catalog external tables vs managed tables behave differently with OneLake shortcuts. Managed tables are more straightforward. For external tables, check the access path and make sure your Fabric credential has read access to the underlying storage.
We use exactly this pattern. The performance is very good because Fabric's Direct Lake engine reads Delta files natively. For large Databricks tables, partition pruning is important — make sure your shortcut leverages the Delta table's partition columns.
Viewing 3 replies - 1 through 3 (of 3 total)