M365Con 2027 – free online conference · 11–22 Jan 2027 · 120 sessions m365con.net

OneLake shortcuts

Concept

Pointers in Microsoft Fabric's OneLake that reference data stored elsewhere, inside Fabric or in external storage, without copying it. The data stays at the target path while the shortcut appears in a lakehouse or other item.

✦ CONCEPTOneLake shortcutsM365.FM
Title graphic: OneLake shortcuts (Concept)

Often discussed together

Episodes about OneLake shortcuts often also cover OneLake, Fabric Data Warehouse, Fabric lakehouse, Fabric Mirroring, Row-level security (RLS) and Apache Spark.

Description

OneLake shortcuts are pointers in Microsoft Fabric's OneLake that reference data stored in another location, either inside Fabric or in external storage, without copying that data. The data stays at its target path, while the shortcut appears as an entry in a lakehouse or another Fabric item. Because only a reference is created, users and workloads can read the data as if it were part of the item they are working in, while the original location remains the single place where the data actually lives.

The main purpose of OneLake shortcuts is to avoid physical data movement. Without shortcuts, making the same data available in several places typically means building ingestion pipelines and storing duplicate copies. With a shortcut, one team can expose data to another team or workspace by reference. This is why shortcuts come up in discussions of data architecture in Fabric: they change the question from how to move data to where the data should live and who should be able to reach it.

The M365.FM episode "Build ETL with Microsoft Fabric Dataflows Gen2" covers shortcuts from a cost and capacity angle. It lists factors that raise compute usage, such as cross-region access with higher latency, repeated transformations and redundant ingestion pipelines, and contrasts them with OneLake shortcuts, which the episode says reduce physical data movement and therefore lower storage and compute costs. In that context, shortcuts are presented as one way to keep ETL operations efficient and predictable, alongside managing compute resources carefully and using managed staging.

Shortcuts also appear in the governance and data mesh discussion. The episode "Use Microsoft Fabric Domains for Data Mesh Governance" maps data mesh principles to Fabric features. Under the principle of data as a product, it names shared access to high-quality data through OneLake Shortcuts. In that model, domain teams own and manage their own data and workspaces, and shortcuts are one mechanism for letting other teams consume that data without taking over ownership or duplicating it. The episode pairs this with semantic models, metadata-rich catalogs, role-based access and cataloging for compliance.

A third episode, "Build a Trusted Semantic Layer in Microsoft Fabric", places OneLake shortcuts on the technical side of a split between governance and engineering. According to the episode, the governance side produces policies, sensitivity labels and data ownership definitions, while the engineering side, owned by data engineers, Fabric administrators and developers, produces validated datasets, automated workflows and OneLake shortcuts. The episode argues that separating these concerns lets an organization address governance and security effectively, with shortcuts belonging to integration and data availability rather than to policy setting.

In practice, decisions around OneLake shortcuts concern where data should be stored, which team owns the target location, and how access is controlled when the same data is surfaced in several lakehouses or items. Since a shortcut is only a reference, the target path remains the authoritative copy, and ownership, quality and access rules defined there continue to matter for every place the shortcut appears. Shortcuts therefore connect naturally to topics such as lakehouses, domains, data products and ETL design in Microsoft Fabric.

Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.

TypeConcept
DocumentationOneLake shortcuts – Microsoft Learn learn.microsoft.com

Episodes about OneLake shortcuts

Episodes in which OneLake shortcuts is discussed:

Timeline of episodes about OneLake shortcuts

Frequently asked questions

Questions marked with AI were written with AI from the facts on this page.

What is a OneLake shortcut? (AI)

A OneLake shortcut is a pointer in Microsoft Fabric's OneLake that references data stored elsewhere, inside Fabric or in external storage. The data stays at its target path while the shortcut appears in a lakehouse or other item.

Why are OneLake shortcuts used instead of copying data? (AI)

Shortcuts avoid physical data movement. The episode "Build ETL with Microsoft Fabric Dataflows Gen2" says this reduces both storage and compute costs, since redundant ingestion pipelines and repeated copies are not needed.

How do OneLake shortcuts relate to data mesh and governance? (AI)

The episode "Use Microsoft Fabric Domains for Data Mesh Governance" names OneLake Shortcuts as the way to share high-quality data as a product between domain teams. The episode "Build a Trusted Semantic Layer in Microsoft Fabric" lists shortcuts as an engineering output, separate from governance policies such as sensitivity labels.

Glossary

Community wiki

Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.

Experts and companies for this topic

Nobody has listed this topic yet. Add it to your profile.

Sources

Maintained by Mirko Peters (Microsoft MVP) · Last updated: