👤 Who is this for?

Data Architect Business Decision Maker Platform Owner — This section explains the Data Mesh paradigm in Fabric: how domains own and publish data products, federated governance, and an interactive visualization of domain-to-domain data flows.

Section 13

Data Mesh Architecture

Domain-oriented data ownership — how business domains produce and consume data products in Microsoft Fabric.

What is Data Mesh?

Data Mesh is a decentralized approach to data architecture where domain teams own and publish their data as products. In Microsoft Fabric, this translates to domains owning their workspaces, lakehouses, and pipelines while exposing curated datasets for other teams to consume through OneLake's unified namespace.

Fabric & Data Mesh

Microsoft Fabric's Domains and OneLake shortcuts are the foundational building blocks for implementing a Data Mesh. Each domain maps to a business unit with its own workspaces, while shortcuts enable zero-copy data sharing across domain boundaries.

Interactive Domain Map

Click on any domain node to highlight its data products and connections. Each animated line represents data flowing between domains.

Fabric Data Mesh — Domain Architecture
Producer flow Consumer flow Bidirectional
📊 Sales 3 data products 📣 Marketing 2 data products 👥 Customer 2 data products 💰 Finance 3 data products ⚙️ Operations 2 data products OneLake

Core Principles

Domain Ownership

Each business domain (Sales, Finance, etc.) owns its data end-to-end — ingestion, transformation, storage, and quality — within its own Fabric workspace.

Data as a Product

Domains publish discoverable, trustworthy datasets with SLAs, documentation, and quality guarantees — consumed via OneLake shortcuts and semantic models.

Federated Governance

A central platform team defines global policies (security, compliance, naming) while domains retain autonomy over their data engineering practices.

Self-Serve Platform

Fabric provides the self-serve infrastructure — OneLake, Data Factory pipelines, Spark notebooks, and Power BI — so domains can build without platform bottlenecks.

Best Practice

Start your Data Mesh journey by identifying 2-3 high-value domains. Create a Fabric domain for each, set up dedicated workspaces (Dev/Test/Prod), and define a clear data product contract (schema, refresh cadence, SLA) before scaling to more domains.