OneLake explained: the storage layer behind Microsoft Fabric

OneLake is the part of Microsoft Fabric that quietly does the most work. Here is what it is, why Microsoft calls it the OneDrive for data, and what it changes for businesses that have always struggled with copies of the same data sitting in different systems.

What OneLake is

OneLake is a single, tenant-wide data lake that ships with Microsoft Fabric. Every workload in Fabric (Power BI, Data Factory, Synapse, Real-Time Analytics, Data Science) reads from and writes to the same OneLake. You do not provision it, configure it, or choose where it lives - it is just there the moment your tenant is enabled.

Why Microsoft calls it OneDrive for data

OneDrive solved a real problem: you used to email documents around and end up with five versions, none of which agreed. OneLake aims to do the same for business data. Instead of every system having its own copy of customer, product, or sales data, OneLake holds one version and every tool references it in place. No more copying data from the warehouse to Power BI, from Power BI to Excel, from Excel into a slide. One source, many tools.

Shortcuts: the bit that does the heavy lifting

Shortcuts let OneLake reference data that lives elsewhere (Azure Data Lake, Amazon S3, Google Cloud Storage, Dataverse) without copying it. The data physically stays where it is, but every Fabric workload can query it as if it were inside OneLake. This is the feature that quietly makes most legacy storage problems go away, because you do not have to migrate everything before you can use it.

What changes for your business

Three practical things. First, less duplication: finance, ops, and marketing all report on the same numbers. Second, less ETL: data does not have to be copied between systems before it can be used. Third, faster analytics projects: a new dashboard, a new model, or a new Copilot use case starts from data that already exists and is already trusted, instead of a fresh extract.

What it does not change

OneLake does not magically make messy data tidy. If your source systems disagree on what a customer is, OneLake will faithfully store the disagreement. The platform makes governance easier (one place to define what good looks like) but the work of agreeing on definitions still has to happen.

The open format underneath

OneLake stores everything in the open Delta Lake format. That matters more than it sounds. It means your data is not locked into a Microsoft-only format - other tools that understand Delta (Databricks, Snowflake, open-source Spark) can read OneLake data directly, without exports or copies. If you ever wanted to use a non-Microsoft analytics tool alongside Fabric, you could, and your data would still be in one canonical place. That openness is unusual for a major cloud vendor and is a real factor when comparing Fabric to alternatives that lock data into proprietary formats.

How OneLake handles security

Permissions in OneLake work at multiple levels. Workspace-level controls govern who can see a whole area. Item-level controls limit access to a specific lakehouse or warehouse. OneLake security adds fine-grained controls down to the table, column, or row, so a finance lakehouse can be shared with the wider business but salaries hidden from anyone outside HR. Sensitivity labels from Microsoft Purview travel with the data too, which means a piece of data classified as confidential stays classified when it is exported to Excel or embedded in a Teams channel.

What it means for your existing data estate

The single most freeing thing about OneLake is that it does not demand a migration. Most businesses we work with start by leaving the bulk of their data exactly where it is (Azure Data Lake, S3, on-prem warehouses) and use shortcuts to bring it into Fabric virtually. That gets reporting and Copilot working on the existing estate in days, not months. Migration becomes a choice you make later, system by system, based on cost and convenience rather than necessity.

Where to start

If you are evaluating Fabric, start by mapping the data sources you currently report on and which ones could live in OneLake natively versus which would be referenced via shortcuts. Our Microsoft Fabric and data readiness pages cover how we run that exercise with clients.

Let's talk

Ready to talk to a real human?

Whether you have a quick question or a bigger project, the Axon team is here to help.