Every data strategy conversation eventually reaches the same fork in the road. Centralize everything under one team, and you get consistency, but decisions slow down and business units lose the context they need to move fast. Hand data ownership to every department, and speed returns, but so do duplicate reports, conflicting numbers, and a governance function that spends more time firefighting than protecting the business.
Most organizations have experienced one extreme or the other, and few emerge convinced that either approach works at scale. Microsoft Fabric offers a structural answer to this tension. Domains own the data, Workspaces contain the work, and a technology called Shortcuts lets every team build from the same source without copying it. This is not a policy teams agree to follow. It is the architecture that makes the right behavior the default.
Domains and Workspaces: Ownership without chaos
Federated governance sounds appealing in a slide deck but is difficult to enforce in practice, mainly because most platforms offer teams no structural way to divide ownership without duplicating infrastructure. Microsoft Fabric solves this with two connected concepts.
A Domain groups data assets around a business unit or ownership boundary, such as Finance, Marketing, or Supply Chain. Within each Domain, Workspaces host the pipelines, reports, and notebooks that teams build and maintain day-to-day. The Domain sets the rules. The Workspace does the work.
This two-level structure lets a data mesh take shape in practice rather than remaining only in a strategy document that nobody operationalizes.
- Domain owners can certify trustworthy datasets and publish them to the OneLake catalog, so other teams can find and use them without having to request a copy.
- A Domain owner in Finance can assign and track compute capacity at the Domain level, giving the business unit real visibility into what its data costs to run.
- Access and sharing controls are in place at the platform level, so cross-domain collaboration occurs through governed channels rather than via email attachments or spreadsheets that no one can track.
- Domains tend to map naturally to how a business is already organized, which removes much of the friction around who owns a given table.
DBAs will recognize the pattern from a shared database instance. A Domain behaves like a database within that instance: it establishes a security and administrative boundary around a defined set of objects, and an admin can assign it its own compute capacity, the way a database in a shared environment has its own resource allocation. A Workspace behaves like a schema within that database: it holds the tables, procedures, reports, pipelines, and notebooks a team actively builds and modifies, and it inherits the Domain’s security model without redefining it. The Fabric tenant serves as the instance itself, enforcing baseline governance, auditing, and platform-wide policies across every Domain and Workspace, regardless of which team owns the workload.
Shortcuts: One version of the truth, wherever it lives
Data duplication rarely begins as a bad decision. A team needs a dataset for a new report, so someone copies it. Six months later, that copy has drifted from the source, and two dashboards display different numbers for the same metric. Multiply that pattern across a large organization, and inconsistency becomes the default state of the data estate.
Shortcuts remove the incentive to copy data in the first place. A Shortcut is a virtual reference to data stored in Azure Data Lake Storage, Amazon S3, Google Cloud Storage, or another OneLake location. It appears in Fabric as a native item without physically moving the underlying data. Finance can reference the customer dataset in the Marketing Domain, and both teams see identical numbers because there is only one dataset.
- Because the data never leaves its source, every consumer automatically works from the latest version, with no stale exports and no overnight sync jobs to maintain.
- Shortcuts work across cloud providers, so an organization running workloads on AWS, Azure, and Google Cloud can build a unified view in Fabric without migrating any files.
- Access policies configured at the source apply to every Shortcut built on top of it, so teams do not need to recreate permissions each time another group references the same dataset.
- Because nothing is duplicated, storage costs remain lower even as more teams build on the same datasets.
Consider a global retailer with sales data in AWS S3, customer data in Azure Data Lake, and supplier data in Google Cloud Storage. Its analytics team uses Shortcuts to build a unified reporting layer across all three sources, with full lineage tracked and no data physically moved.
Seeing where data comes from and where it goes
Ownership and zero-copy access solve two problems, but teams still need to trust what they see. Microsoft Fabric addresses this through automatic lineage tracking and a searchable catalog built into OneLake.
Fabric automatically tracks every pipeline, dataflow, and notebook run as data moves through it, so a business user can trace any number in a report back to the table it came from. That same lineage view enables impact analysis before a change goes live. If a schema update affects dozens of downstream reports, teams learn about it in advance rather than through a support ticket. The OneLake catalog surfaces every certified, governed dataset across every Domain, giving teams a way to find trustworthy data on their own instead of building another shadow spreadsheet. Fabric captures lineage automatically rather than requiring manual documentation after the fact, so audit and compliance reviews become considerably easier.
Domains, Workspaces, and Shortcuts provide organizations with the building blocks for federated data management, but structure alone does not guarantee good outcomes. Someone still has to define Domain boundaries that align with how the business is organized on the ground, decide which datasets to certify, size capacity correctly, and set governance policies that hold up as the platform grows. Get these decisions wrong early, and Fabric becomes just another tool that adds confusion instead of removing it.
This is where a Fabric implementation partner earns its place. LevelShift is a Microsoft Fabric Featured Partner with more than 50 Fabric-certified experts and over 30 completed Fabric implementations across industries. Our team has helped organizations establish this kind of federated architecture into practice, including a leading US convenience retailer that consolidated data from multiple business lines into a governed Fabric foundation. That work cut the time to access business insights by 60 percent and reduced manual reporting effort by 40 percent. We bring a proven approach to domain design, capacity governance, and Shortcut architecture, so your team does not have to learn these lessons through trial and error.
Ready to bring Domains, Workspaces, and Shortcuts together in your Fabric environment? Connect with LevelShift’s Microsoft Fabric experts to receive a clear roadmap for your rollout.
