The bottom line
Use managed Lakehouse tables for analytics-facing data that Power BI needs via Direct Lake. Use Shortcuts for raw or external data you want to keep in place. Use unmanaged tables when you need to share Delta data across multiple Lakehouses without duplication.
In This Article
The Lakehouse Storage Options
A Fabric Lakehouse has two storage areas: Tables and Files. Tables holds managed Delta tables — created via spark.sql CREATE TABLE or via the DataFrame saveAsTable() method. These appear automatically in the SQL analytics endpoint and are queryable by Power BI via Direct Lake. Files holds unstructured or semi-structured files — raw CSVs, Parquet files, JSON, images — and also Delta tables you want to manage manually without registering them in the catalog.
On top of these, Fabric Shortcuts let you mount external data — from ADLS, Amazon S3, Google Cloud Storage, or other Fabric Lakehouses — as a virtual path inside the Lakehouse. Shortcuts can point to either the Tables or Files section, with different behaviours in each case.
Managed Tables: When They Are Right
Managed Lakehouse tables are the right choice when: the table is the output of a transformation pipeline (Silver or Gold layer in medallion architecture), Power BI needs to read it via Direct Lake, and you want automatic Delta log management (VACUUM, OPTIMIZE) handled by Fabric. The SQL analytics endpoint exposes managed tables immediately with no additional configuration.
The trade-off for managed tables is that Fabric owns the storage location — it is inside the OneLake path for the specific Lakehouse workspace. If you delete the Lakehouse, the managed table data is deleted. If you need to share the same physical Delta table across multiple Lakehouses or workspaces without duplication, managed tables are not the right choice — you want Shortcuts or unmanaged external tables.
Shortcuts: The Right Tool for External Data
Shortcuts are the Fabric answer to "I have data in ADLS (or S3, or another Lakehouse) and I do not want to copy it." They create a virtual reference to external storage that appears as a folder inside the Lakehouse Files or Tables section. Shortcuts in the Files section behave like regular file paths — Spark can read them, but they do not appear in the SQL endpoint. Shortcuts in the Tables section appear in the SQL endpoint and can be queried via Direct Lake if they point to Delta-formatted data.
The operational constraint with Shortcuts is that Fabric Spark cannot write to a Shortcut destination unless you have write access to the source storage account. Read-only Shortcuts are the most common pattern — you bring external Bronze-layer data into scope without moving it, then transform it into managed Gold-layer tables within the Lakehouse.
The Medallion Architecture in Fabric
The pattern that works cleanly in Fabric for a mid-size manufacturing or FMCG data platform: one Lakehouse per medallion tier, all within the same Fabric workspace. Bronze Lakehouse holds raw ingested data — Shortcuts pointing to ADLS landing zones for ERP extracts, IoT historian feeds, and file drops. Silver Lakehouse holds cleansed and conformed data — managed Delta tables written by Fabric notebooks running transformation logic. Gold Lakehouse holds business-ready aggregations — managed Delta tables optimised for Power BI Direct Lake.
With one workspace and three Lakehouses, the SQL analytics endpoint for the Gold Lakehouse is the single connection point for Power BI. You never expose Bronze or Silver data to Power BI report authors. Cross-Lakehouse Shortcuts allow the Silver transformation notebooks to read from Bronze without copying data.
Three Lakehouses in one workspace is not over-engineering. It is the minimum structure that lets you evolve Bronze ingestion patterns without breaking Silver transformation logic or Gold reporting.
The Decision Framework
Use managed Lakehouse tables when: the data is a transformation output (Silver or Gold), Power BI needs Direct Lake access, or you want Fabric to handle Delta maintenance operations automatically. Use Files-section Shortcuts when: you want to reference external raw data without copying it, and you do not need SQL endpoint access. Use Tables-section Shortcuts when: you want to expose external Delta data through the SQL endpoint without copying it, accepting that Fabric cannot run OPTIMIZE or VACUUM on it.
The one situation where none of these fit cleanly is when you need to share a Gold-layer table between two Fabric workspaces for different business units. The right pattern there is a cross-workspace Shortcut: Workspace A owns the Gold managed table; Workspace B creates a Tables-section Shortcut pointing to it. Both workspaces see the same physical Delta data.
The Fabric Lakehouse architecture rewards upfront design decisions. Getting the managed table vs Shortcut vs external table choice right at the start avoids expensive refactors later. If you are designing a Fabric data platform for manufacturing, FMCG, or supply chain and want a second opinion on the architecture before you build it, I am happy to review it.
Free Assessment
Where does your operation sit on the data maturity curve?
8 questions. 3 minutes. You get a scored breakdown across data infrastructure, analytics readiness, and automation potential — with a specific next step for your industry.