Skip to content

Azure · Editable reference architecture

Microsoft Fabric architecture

An editable microsoft fabric architecture reference showing Sources → Data Factory pipelines → OneLake and downstream dependencies. Define ownership across shared analytical assets.

Open & Edit in DrawArc (Free, No Login Required)

Your changes stay in a separate draft on this browser. Download an editable project to keep a portable copy.

LinkedInTelegramReddit

Microsoft Fabric architecture diagram: Sources, Data Factory pipelines, OneLake, Lakehouse and their connections
Microsoft Fabric architecture — follow the component relationships, then open the editor to adapt the design. View diagram image.

7 components · 6 connections · Open the editor to zoom, move nodes and edit source.

Architectural overview

Microsoft Fabric architecture addresses the responsibilities and boundaries shown in this reference rather than prescribing an entire production deployment. The primary flow starts at Sources and reaches Power BI through Data Factory pipelines, OneLake, Lakehouse, Semantic model. Use this view to explain which component initiates work, which component owns a decision, and where a dependency can affect the caller. Define ownership across shared analytical assets.

The diagram contains 7 distinct components and 6 directed relationships. A separate path connects Governance catalog → OneLake. These arrows describe logical interactions; they do not establish authentication, network access, atomic transactions or delivery guarantees. Label the actual protocol, payload contract and owner when adapting the drawing to your system. Keep synchronous and asynchronous boundaries explicit so that a reviewer can identify where a request ends and a later operation begins.

Before implementing this architecture, define expected load, data classification, latency budgets and recovery objectives. Give Semantic model a bounded dependency timeout and a documented failure response. For OneLake, Lakehouse, specify ownership, retention, access control and a tested recovery procedure. Validate the decision above against your workload instead of treating the presence of a component as proof of reliability. Open the editable canvas, replace generic labels with real deployment units, and document the decisions that differ from this reference.

The real-world problem

Design or explain microsoft fabric architecture with explicit ownership and dependency paths. Define ownership across shared analytical assets.

Data flow

Connections from this diagram. Branches and control signals are not a single chronological sequence.

  • Sources → Data Factory pipelines. Define the interaction contract and trace the resulting response or state change.
  • Data Factory pipelines → OneLake. Define the interaction contract and trace the resulting response or state change.
  • OneLake → Lakehouse. Define the interaction contract and trace the resulting response or state change.
  • Lakehouse → Semantic model. Define the interaction contract and trace the resulting response or state change.
  • Semantic model → Power BI. Define the interaction contract and trace the resulting response or state change.
  • Governance catalog → OneLake. Define the interaction contract and trace the resulting response or state change.

Security boundaries

  • Authenticate callers at the boundary before Data Factory pipelines accepts protected work; authorize the specific operation rather than trusting network placement.
  • Use separate service identities and least-privilege permissions for Data Factory pipelines, OneLake, Lakehouse. Encrypt sensitive traffic, protect credentials and avoid placing confidential payloads in logs.
  • Restrict and audit access to OneLake, Lakehouse; define retention and deletion requirements for the actual data.

Failure handling

Semantic model is unavailable or slow

Response: Apply bounded timeouts and controlled backoff only where retrying is safe. Return an explicit failure or durable acceptance; do not report success before required work is committed.

Verify: Interrupt Semantic model in an isolated test and measure errors, recovery and any repeated side effects.

OneLake loses or returns stale state

Response: Use workload-specific durability, reconciliation and tested recovery. Specify how stale reads or a failed write affect callers.

Verify: Exercise the failure path with representative records and verify both the visible response and the resulting state.

An invalid or incompatible input reaches Data Factory pipelines

Response: Validate the input contract before effects are committed. Preserve rejected input identifiers without exposing secrets, and document a safe replay or correction procedure.

Verify: Send malformed and older-version inputs through Sources and verify rejection, observability and unchanged valid state.

Trade-offs and alternatives

Define ownership across shared analytical assets.

Benefit
Makes the ownership and interaction boundaries visible for a focused design review.
Cost
The 7 illustrated components still require contracts, monitoring and operational ownership; extra boundaries can add latency and failure modes.
Alternative
Use a simpler deployment when it meets the same requirements, or split a boundary only after measuring a specific need.

Logical boundaries versus deployment units in Microsoft Fabric architecture

Benefit
Keeps the responsibilities of Sources, Data Factory pipelines, OneLake visible without requiring a separate server for each box.
Cost
A logical view does not establish isolation, independent scaling or high availability; those require a separate deployment design and operational tests.
Alternative
Co-locate components in a simpler deployment first when ownership and workload requirements permit it.

When to use this architecture

  • Explain microsoft fabric architecture to engineers or stakeholders using a concrete visual flow.
  • Review this decision before deployment: Define ownership across shared analytical assets.
  • Adapt a starting diagram for your own requirements, then record and validate every changed boundary.

Key components

Sources
Sources participates in microsoft fabric architecture. Sources → Data Factory pipelines. Define its contract, owner and access permissions in your implementation.
Data Factory pipelines
Data Factory pipelines participates in microsoft fabric architecture. Sources → Data Factory pipelines; Data Factory pipelines → OneLake. Define its contract, owner and access permissions in your implementation.
OneLake
OneLake participates in microsoft fabric architecture. Data Factory pipelines → OneLake; OneLake → Lakehouse; Governance catalog → OneLake. Define its contract, owner and access permissions in your implementation.
Lakehouse
Lakehouse participates in microsoft fabric architecture. OneLake → Lakehouse; Lakehouse → Semantic model. Define its contract, owner and access permissions in your implementation.
Semantic model
Semantic model participates in microsoft fabric architecture. Lakehouse → Semantic model; Semantic model → Power BI. Define its contract, owner and access permissions in your implementation.
Power BI
Power BI participates in microsoft fabric architecture. Semantic model → Power BI. Define its contract, owner and access permissions in your implementation.
Governance catalog
Governance catalog participates in microsoft fabric architecture. Governance catalog → OneLake. Define its contract, owner and access permissions in your implementation.

Questions about this template

What does this microsoft fabric architecture diagram show?

It shows 7 components with the core flow Sources → Data Factory pipelines → OneLake → Lakehouse → Semantic model → Power BI. Define ownership across shared analytical assets.

Can I edit this diagram without signing in?

Yes. Open the template in the browser-local canvas to change nodes, connections and source. AI generation and cloud account storage require sign-in.

Is this a complete production implementation?

No. It is an editable reference. Validate the security controls, dependency behavior, capacity and recovery plan against your own requirements before implementation.

Validate your implementation

Use the relevant platform documentation to verify service limits, supported features and configuration. This diagram is an original reference rather than a reproduction of a provider deployment.