Microsoft Fabric Architecture: A Deep Dive Into the Unified Analytics Platform

What Makes Fabric Different

Microsoft Fabric is not simply a rebrand of existing Azure data services. It represents a fundamental architectural shift: a unified analytics platform built on a single data lake (OneLake) with integrated compute engines for every analytics workload — data engineering, data warehousing, real-time intelligence, data science, databases, and business intelligence.

Before Fabric, building an enterprise analytics platform on Azure meant provisioning and integrating separate services: Azure Data Factory for pipelines, Azure Synapse for warehousing, Azure Databricks for data science, Azure Data Lake Storage for storage, and Power BI for visualization. Each service had its own security model, storage format, metadata catalog, and billing structure.

Fabric collapses this complexity into a single SaaS platform with shared governance, a single security model, and one copy of the data. In 2025–2026, Fabric expanded its workload lineup significantly — adding Fabric Databases (GA), Fabric Mirroring (GA), Fabric Activator (GA), and renaming Real-Time Analytics to Real-Time Intelligence. Organizations planning this transition benefit from structured microsoft fabric consulting to accelerate architecture design and governance setup.

OneLake: The Foundation

What Is OneLake?

OneLake is Fabric’s built-in data lake, analogous to OneDrive for data. Key characteristics:

• One lake per tenant — every Fabric capacity in your organization shares a single OneLake instance
• Built on Azure Data Lake Storage Gen2 — full ADLS Gen2 compatibility with hierarchical namespace
• Open format — data is stored in Delta Lake (Parquet + transaction log), an open standard accessible by any tool
• Automatic provisioning — no storage accounts to create, manage, or secure separately
• Multi-cloud shortcuts — create references to data in AWS S3 or Google Cloud Storage without copying it
• OneLake File Explorer — a Windows desktop application that mounts your OneLake as a local file system for drag-and-drop file operations without the Fabric portal

OneLake Hierarchy

OneLake organizes data in a familiar hierarchy:

OneLake (Tenant)
├── Workspace: Sales Analytics
│   ├── Lakehouse: SalesLakehouse
│   │   ├── Tables/
│   │   │   ├── customers (Delta table)
│   │   │   ├── orders (Delta table)
│   │   │   └── products (Delta table)
│   │   └── Files/
│   │       ├── raw_data/
│   │       └── staging/
│   ├── Warehouse: SalesWarehouse
│   ├── SQL Database: SalesOperational
│   ├── Semantic Model: SalesModel
│   └── Report: SalesReport
├── Workspace: HR Analytics
│   └── …
└── Workspace: Finance
└── …

Shortcuts: Zero-Copy Data Access

Shortcuts are one of OneLake’s most powerful features. A shortcut is a reference to data stored elsewhere — another OneLake location, an ADLS Gen2 account, an S3 bucket, or a GCS bucket. The data is not copied; the shortcut provides a transparent access layer.

Use cases for shortcuts:

• Cross-workspace data sharing — the Finance workspace creates a shortcut to the Sales lakehouse’s customer table without duplicating data
• Hybrid cloud — reference data in AWS S3 alongside data in OneLake without ETL
• Legacy migration — create shortcuts to existing ADLS Gen2 storage while gradually migrating to Fabric-native items
• Data mesh — each domain owns its data in its workspace and publishes shortcuts for cross-domain access

Compute Engines

Data Engineering (Apache Spark)

Fabric provides a fully managed Apache Spark environment for large-scale data processing:

• Spark pools — auto-scaling Spark clusters with Starter pools (instant start) and custom pools
• Notebooks — interactive development with Python, Scala, R, and SparkSQL, with Copilot assistance
• Spark job definitions — scheduled batch jobs for production pipelines
• VS Code integration — develop locally and deploy to Fabric
• Libraries — install custom Python and R packages per workspace or session
• Lakehouse integration — Spark reads and writes directly to OneLake Delta tables

Key architectural detail: Fabric Spark uses a shared metadata layer. When Spark writes a Delta table to a lakehouse, that table is immediately visible in the SQL endpoint and Power BI — no ETL, no sync, no delay.

Data Warehouse

Fabric’s data warehouse provides a full T-SQL experience:

• T-SQL compatibility — familiar SQL Server syntax for queries, views, stored procedures, and functions
• Distributed query engine — columnar storage with distributed processing for fast analytical queries
• Cross-database queries — query across warehouses and lakehouses within the same workspace
• Clone tables — zero-copy table clones for development and testing
• Time travel — query data as it existed at a previous point in time

Warehouse vs. Lakehouse SQL Endpoint:

Fabric Databases — SQL Database in Fabric (GA)

Fabric Databases is a generally available workload that brings a fully managed operational SQL database into the Fabric platform. Unlike the Data Warehouse (analytics-optimized), Fabric Databases supports transactional OLTP workloads:

• Full SQL Server compatibility — T-SQL, transactions, foreign keys, triggers
• Autonomous — automatic backups, high availability, and patching managed by Microsoft
• OneLake integration — database tables are automatically mirrored into OneLake as Delta Parquet, making operational data immediately available to analytics workloads without ETL
• GraphQL API — a built-in Fabric API for GraphQL exposes database data to applications
• Best for — application backends, operational databases, LOB apps that need to coexist with analytics in the same Fabric tenant

Real-Time Intelligence (Renamed from Real-Time Analytics)

Microsoft renamed the Real-Time Analytics workload to Real-Time Intelligence in 2024, reflecting its expanded scope:

• Eventstreams — ingest data from Azure Event Hubs, Kafka, IoT Hub, custom apps, change data capture from databases, and more
• KQL Database — store and query streaming and time-series data with Kusto Query Language
• Real-Time Dashboards — live visualizations that update as data arrives, with sub-second latency
• Activator (GA) — event-driven triggers that fire automated actions (Teams alerts, Power Automate flows, webhooks) based on conditions in streaming or lakehouse data

Architecture pattern for IoT monitoring: IoT Devices → Event Hubs → Eventstream → KQL Database → Real-Time Dashboard ↓ Activator (alert when threshold exceeded) ↓ Teams notification / Power Automate flow

Fabric Mirroring (GA)

Fabric Mirroring replicates data from external operational databases into OneLake continuously:

• Supported sources — Azure SQL Database, Azure SQL Managed Instance, Azure Cosmos DB, Snowflake, and more
• Near-real-time — changes in source systems appear in OneLake within seconds to minutes
• No pipeline required — configured declaratively; no Spark jobs or Data Factory pipelines needed
• Replicated as Delta Parquet — mirrored data is immediately available to all Fabric workloads
• Best for — analytics on operational data without impacting source systems, replacing traditional CDC-based ETL patterns

Data Science

Fabric integrates data science capabilities:

• Notebooks with MLflow tracking for experiment management and Copilot assistance for code generation
• Models registered in the Fabric model registry
• PREDICT function for scoring models directly in T-SQL or Spark
• Semantic link for accessing Power BI semantic models from notebooks

Data Factory

Fabric Data Factory handles data movement and orchestration:

• Dataflows Gen2 — Power Query-based transformations (low-code ETL)
• Data pipelines — orchestration workflows compatible with Azure Data Factory
• Copy activity — move data from 100+ source connectors into OneLake
• Scheduling — cron-based and event-based pipeline triggers

The Medallion Architecture in Fabric

The medallion architecture (Bronze → Silver → Gold) is the recommended pattern for organizing data in Fabric:

Bronze Layer (Raw)

• Raw data ingested from source systems without transformation
• Stored in the lakehouse Files section or as Delta tables
• Full fidelity — preserves the exact data as received from the source
• Serves as the system of record for auditability

Silver Layer (Curated)

• Cleaned, validated, and standardized data
• Data type enforcement, null handling, deduplication
• Conformed dimensions (consistent customer IDs, product codes)
• Stored as Delta tables in the lakehouse Tables section

Gold Layer (Business-Ready)

• Aggregated, enriched data optimized for specific business use cases
• Star schema models for reporting (fact and dimension tables)
• Pre-computed metrics and KPIs
• Consumed by Power BI semantic models and operational applications Sources → Bronze (raw) → Silver (curated) → Gold (business-ready) → Power BI ↑ ↑ ↑ ↑ Pipelines/ Mirroring Spark/SQL Semantic Dataflows Notebooks Models

Security Architecture

Workspace-Level Security

• Roles: Admin, Member, Contributor, Viewer
• Microsoft Entra ID integration — assign roles to users, groups, and service principals
• Workspace identity — managed identity for accessing external resources

Item-Level Security

• OneLake data access roles — control who can read specific folders and tables within a lakehouse
• Row-level security (RLS) — filter data rows based on user identity in warehouses and semantic models
• Column-level security (CLS) — restrict access to sensitive columns in warehouses
• Object-level security (OLS) — hide tables and columns from users in semantic models
• Dynamic data masking — mask sensitive data (SSN, email) in query results

Network Security

• Private endpoints — access Fabric from within your VNet
• Managed private endpoints — connect Fabric to data sources via private network
• Trusted workspace access — allow specific workspaces to access secured storage accounts

Capacity and Licensing

Fabric uses capacity-based licensing measured in Capacity Units (CUs):

All workloads — Spark, SQL, Real-Time Intelligence, pipelines, Power BI, Databases — share the same capacity pool. Fabric uses bursting and smoothing so you do not need to provision for peak demand. Capacities can be paused when not in use. Note: Fabric SQL Databases introduced separate storage billing from OneLake in 2025 — refer to the current Microsoft pricing page for latest rates.

Design Patterns

Pattern 1: Centralized Data Platform

One team manages a central Fabric capacity with shared lakehouses. Simple governance but potential bottleneck on the central team.

Pattern 2: Data Mesh

Each domain (Sales, Finance, HR) owns data in dedicated workspaces and publishes curated datasets via OneLake shortcuts. More autonomous but requires a mature data culture.

Pattern 3: Hub and Spoke

Central hub workspace manages shared reference data and enterprise-wide transformations. Domain-specific spoke workspaces connect via shortcuts for team-level analytics.

Pattern 4: Operational + Analytics (New in 2026)

Enabled by Fabric Databases and Fabric Mirroring — Fabric SQL Database hosts transactional application data, automatic mirroring continuously replicates it into OneLake, and all analytics workloads access the same data with no ETL pipeline. Single Fabric tenant hosts both operational and analytical workloads under unified governance.

Migration Path

For organizations running Azure Synapse, Azure Data Factory, or Databricks:

1. Assessment — inventory existing pipelines, datasets, and consumers
2. OneLake shortcuts — create shortcuts to existing ADLS Gen2 storage for immediate access in Fabric
3. Fabric Mirroring — evaluate whether operational source databases can be mirrored instead of ETL’d
4. Migrate pipelines — convert ADF pipelines to Fabric Data Factory pipelines (high compatibility)
5. Migrate notebooks — port Databricks or Synapse Spark notebooks to Fabric (Spark API compatible)
6. Migrate Power BI — existing Power BI workspaces can be assigned to Fabric capacities
7. Decommission — retire legacy services once Fabric workloads are validated

Next Steps

Microsoft Fabric’s unified architecture reduces the complexity and cost of enterprise analytics, but realizing its benefits requires thoughtful design — from OneLake organization and security to capacity planning and workload optimization. If you need implementation support, our microsoft fabric consulting team can help design the right operating model.

Al Rafay Consulting helps organizations design, migrate to, and optimize Microsoft Fabric deployments. Whether you are evaluating Fabric for a new project or planning a migration from existing Azure data services, our team brings hands-on experience across every Fabric workload.

Contact us to plan your Fabric architecture