OneLake doesn't ask you to migrate anything, and that's the whole difference

For fifteen years, every data project started the same way: before answering the first business question, you had to move the information. Copy it from the ERP, from the SQL Server at headquarters, from the sales team's Excel files, and drop it into a new repository. That upfront migration was half the budget and almost all the risk, and it happened before anyone had seen a single dashboard.

OneLake, the storage layer of Microsoft Fabric, changes the starting point: it links your sources where they already are.

What a shortcut is, in plain English

A shortcut is a link. From Fabric, a folder or a table that lives somewhere else (another storage account, another account, another service) appears as if it were inside your data lake, and you query it the same way. The information is not copied or duplicated: it is referenced.

Mirroring is its close relative: an operational database is continuously reflected in OneLake, without you building or maintaining the copy process, and without penalizing the database that is serving your operations. And for everything else (business systems, files, on-premises services) there are the usual connectors.

Three paths, and each source comes in through the one that suits it.

Why this changes the cost of getting started

When you don't have to migrate to get started, the whole project is reordered:

• The first dashboard arrives in weeks, not quarters, because it is not waiting for a migration to finish.
• Risk goes down: if a link doesn't work out, you remove it. There is no copy of a million rows to roll back.
• You test before you commit. You can validate whether a source adds value using the real data, not a sample.
• Governance comes first, not last: permissions and lineage are defined on the linked source from day one.

What is still work

It is worth saying, because product pitches tend to leave it out: linking is not modeling. OneLake solves access, not meaning. You still need to agree on what an active customer is, what counts as a sale and when; you still need a model people understand; and you still need to clean the data, because data quality does not improve by changing storage.

The difference is when that work is done: on data that is already visible, with the business team watching, instead of blindly during the three months the copy used to take.

Where the dashboards live

On your platform. The pipelines, the model and the dashboards are built inside your tenant, with your identity and your permissions; the information is not moved to any service of ours. And when you want to apply artificial intelligence on top of that, Azure AI Foundry works on the same platform, with your real data and not a demo dataset.

If you have information spread across an ERP, some databases at headquarters and too many Excel files, tell us which question you want to answer first. That is where you start, not with the migration.

Why does linking sources change the starting point of a data project?

For years, any data project began with a transfer stage: extracting the information from the ERP, from the databases at headquarters or from the sales team's files, and depositing it in a new repository. That stage accounted for a good part of the budget and the risk, and it happened before the business saw a single dashboard.

With OneLake, the order changes. By linking sources at their place of origin, the first dashboard does not depend on a prior migration. If a link does not deliver what you expected, you remove it without having to roll back a copy, so you can validate the value of a source with real data before committing.

The change does not eliminate the underlying work, but it does change when it happens. Definitions, the model and data cleaning are tackled on data that the business team can already see, instead of being done blindly during the time the copy used to take.

OneLake is the storage layer of Microsoft Fabric. Unlike a migration, it does not require copying the information to a new repository before you start: it links the sources where they already are, so the project can move forward from day one.

A shortcut is a link. A folder or table that lives in another storage account, account or service appears inside your data lake and is queried just like the rest. The information is not copied or duplicated: it is referenced.

No. OneLake solves access, not meaning. You still need agreement on definitions such as active customer or sale, a model the business team understands, and data cleaning, because quality does not improve by changing storage.

The pipelines, the model and the dashboards are built inside your own tenant, with your identity and your permissions. According to the published text, the information is not moved to any Arcetec service.