Microsoft Fabric Architecture: Four-Zone Architecture & Metadata-Driven Framework
FOUR-ZONE DATA ARCHITECTURE:
What happens when established architecture patterns meet the realities of enterprise-scale delivery?
At Eden Smith, our consultants don’t just work with established frameworks. They apply them to complex, real-world environments, identify where they can be improved and develop practical approaches that are scalable, reusable and built for what organisations need next.
This four-zone Microsoft Fabric architecture is a great example. It develops the traditional Medallion approach by separating standardisation from integration, while combining it with metadata-driven engineering to create a foundation designed for BI, Data Science, Machine Learning and AI.
The thinking is technical. But the principle behind it is simple: good architecture should solve today’s problem without creating tomorrow’s constraint.
Beyond Traditional Medallion Architecture
Traditional Medallion Architecture commonly follows: Bronze → Silver → Gold. This works well, but at enterprise scale, the Silver layer can become overloaded with cleansing, standardisation, joins, enrichment and business logic.
A four-zone architecture separates these responsibilities: RAW → BASE → ENRICHED → CURATED. The objective is not simply to add another layer. It creates clear separation between source preservation, technical standardisation, data integration and business-ready data, while providing a reusable foundation for BI, Data Science, Machine Learning and AI.
The Four Zones
1. RAW | Preserve
Stores data as received from the source with minimal modification.
Purpose: Source integrity, Traceability, History, Reprocessing
2. BASE | Standardise
Creates a clean and technically consistent representation of each source dataset while preserving its business meaning.
Purpose: Data types, Standardisation, Cleansing, Quality checks, Incremental processing
3. ENRICHED | Integrate & Enable
Combines related datasets and adds useful context without making the data report-specific.
Purpose: Joins, Cross-source integration, Reference data, Reusable business entities, Analytical preparation
Why it matters: The Enriched layer becomes a reusable Data & AI enablement layer. Data Science, ML and AI workloads can consume clean, integrated and contextualised data without rebuilding source-level engineering.
4. CURATED | Business Ready
Applies governed business rules and creates trusted data products for business consumption.
Purpose: Facts, Dimensions, KPIs, Aggregations, Reporting-ready datasets
Why Four Zones? The rationale!
Clear Separation - Each type of transformation has a defined responsibility.
Reusable Data - Integration is performed once and reused across downstream workloads.
AI & ML Ready - Enriched data can directly support Data Science, ML and AI use cases.
Maintainable & Scalable - Changes are easier to isolate, troubleshoot and extend as the platform grows.
One Foundation - Multiple Consumption Paths
Sources → RAW → BASE → ENRICHED
From ENRICHED:
→ CURATED → Power BI | Reporting | KPIs
→ Data Science | Machine Learning | AI / GenAI
The Enriched layer creates a reusable bridge between core data engineering, governed business reporting and advanced AI/ML workloads.
METADATA-DRIVEN FRAMEWORK
Reusable Data Engineering Through Configuration
As data platforms grow across multiple sources and hundreds of tables, creating and maintaining individual hard-coded pipelines for every dataset becomes difficult to scale.
A metadata-driven framework separates configuration from execution logic.
Instead of hard-coding source, target, load strategy and processing behaviour into individual pipelines, these values are stored as metadata and interpreted by reusable orchestration and processing components.

Architecture shaped by delivery, not theory
This is where Eden Smith's consulting approach is different.
Our technical consultants bring hands-on experience of complex data environments and use that experience to challenge, adapt and improve established approaches.
The goal isn’t innovation for innovation’s sake. It’s designing architecture that is easier to scale, govern and maintain while creating a stronger foundation for analytics and AI.
What Can Metadata Control?
Source: Source system, Object, Connection
Target: Lakehouse, Schema, Table, Processing zone
Load Strategy: Full load, Incremental, Watermark, Merge
Processing: Sequence, Dependencies, Processing behaviour
Operations: Schedule, Active status, Logging, Monitoring, Error handling
Flexible Ingestion - One Framework
Metadata-driven does not mean every source must use the same ingestion method. The appropriate Microsoft Fabric capability can be selected based on the source and requirement:
Pipeline → Standard data movement and orchestration
Notebook → APIs, custom ingestion and complex processing
Shortcut → Reference existing data without unnecessary duplication
Mirroring → Replicate supported operational databases
Additional ingestion methods can be introduced as requirements evolve while maintaining the same wider architecture and processing standards.
Key Benefits
Scalability - Onboard new datasets primarily through configuration.
Consistency - Apply common loading, processing, logging and monitoring standards.
Maintainability - Maintain reusable logic centrally instead of duplicating it across pipelines.
Operational Control - Understand centrally what runs, how it runs and where data is processed.
Architecture + Metadata
Four-Zone Architecture defines WHERE data belongs.
Metadata-Driven Framework defines HOW data is processed.
Together they create a platform that is:
Scalable, Reusable, Consistent, Maintainable, Governed
FROM THINKING TO APPLICATION
This isn't architecture developed in isolation.
Eden Smith consultants have applied the principles behind this approach within complex enterprise data transformation, including the modernisation of a legacy data estate onto Microsoft Fabric.
That practical delivery experience feeds back into the way we design solutions: identifying what works, where established patterns need adapting and how architecture can better support analytics, AI and future change.
At Eden Smith, our Data & AI consultants combine deep technical expertise with hands-on delivery experience. That means we're not simply implementing standard frameworks. We're continually testing, adapting and improving them against the realities of enterprise data environments.
This four-zone architecture and metadata-driven approach is one example: creating clearer separation of responsibilities, reusable integrated data and a platform capable of supporting traditional BI alongside Data Science, Machine Learning and AI.
Have a Microsoft Fabric architecture challenge of your own?
Find out more about how Eden Smith can support modernising a legacy data estate and talk to our
Data & AI Consulting team.











