Erwin | Data & Intelligence

FMD Framework for Microsoft Fabric Explained: A Video Guide by Matthias Falland

Fabric Metadata‑Driven Framework (FMD)
Fabric Metadata‑Driven Framework (FMD)

FMD Framework for Microsoft Fabric Explained: A Video Guide by Matthias Falland

by Erwin | Nov 19, 2026

Table of Contents

"From the architecture to your first table — and when a different approach may be the better fit."

A practical introduction to FMD, from someone else’s perspective

Explaining a framework you build yourself is one thing. Seeing someone else unpack the ideas, follow the data and ask where it fits is something different. Matthias Falland has created a video series about my Fabric Metadata-Driven Framework (FMD), covering the architecture, the loading process, onboarding a table and the decision between FMD and Fabric Copy job.

A big thank-you to Matthias for putting this material together. If you have been curious about FMD but would rather start with a guided explanation than dive straight into the repository, these videos give you a useful route into the framework.

 

Start here: what is FMD?

The starting point is a familiar data engineering problem: loading another table should not mean creating and maintaining another near-identical pipeline. FMD takes a metadata-driven approach. You describe what needs to be loaded in a configuration database, and reusable pipelines and notebooks carry out the work.

The first video introduces that idea through the core loading journey: source data arrives as files in the Landing Zone, Bronze represents the current state, and Silver maintains history. It also draws an important boundary: the ingestion journey covered here ends at Silver. Your business-specific Gold models, metrics and reporting logic remain yours to design.

That distinction matters. A reusable loading framework should give you a consistent foundation without pretending it knows how your organisation defines revenue, customers or business performance.

 

Follow one table from Landing to Silver

Architecture becomes easier to understand when you follow a concrete example. In the second video, Matthias follows an Orders table through the layers, showing how the orchestrator runs Landing, Bronze and Silver in sequence.

The useful detail is not just where the data ends up, but how the work is coordinated. Views turn configuration into the queries needed for execution, while queues connect the processing stages. The video also highlights the ordering of the queue step and watermark update: the watermark is stored after the queue step.

For anyone assessing the framework, this is the video to watch when you want to move beyond the architecture diagram and understand the mechanics of a load.

 

Add a table through configuration, not another pipeline

The third video brings the metadata-driven approach into focus. Rather than editing a pipeline for each new source table, you register the table in the configuration database. The example covers a connection, a data source and the entity registrations for Landing, Bronze and Silver.

Matthias explains the separation between the database schemas: integration holds the definitions you configure; execution determines the work to perform; logging records what happened. Credentials stay in Fabric rather than becoming part of those configuration rows.

The practical takeaway is simple: onboarding becomes configuration work. That does not make configuration unimportant. Treat it with the same care as code, because those rows determine what the framework will execute.

FMD or Fabric Copy job? Start with the requirement

I am glad this series also includes a discussion about when not to use FMD. Choosing an approach should start with your requirements, not with a preference for a particular framework.

In the final video, Matthias makes the case for considering Fabric Copy job first where its supported sources and change-handling capabilities meet your needs. He positions FMD as an alternative when you want a configuration-based table registry and history-building patterns without relying on source CDC.

The limitations deserve equal attention. The incremental loading approach discussed cannot detect source deletes simply from a watermark, and FMD is a framework you deploy and operate yourself. History in Silver should not be mistaken for a guarantee that every source-side change has been captured.

Check the behaviour you need for your actual source, especially deletes and historical accuracy. That is a more useful starting point than asking which option wins in every situation.

 

Thank you, Matthias — and over to you

Open source is not only about publishing code. Clear explanations help people understand the design, challenge assumptions and decide whether a project fits their own platform. Thank you, Matthias, for making FMD more approachable through this series.

If you are new to FMD, start with the overview, follow the Orders example, and then look at table onboarding. Finish with the Copy job comparison before deciding what belongs in your own architecture.

FMD is available as an open-source project under the MIT licence. Explore the repository, try it against your own requirements, and share your questions, issues and contributions. What would you like to see explained next?

New to the Microsoft Fabric Metadata Driven Framework?

Learn more about the framework architecture, deployment model, and features here:

The Microsoft Fabric Metadata Driven Framework continues to help organizations standardize data platform delivery, automate Microsoft Fabric deployments, improve governance, and accelerate AI-ready architectures. With every release, the framework becomes more reliable, secure, and easier to adopt for enterprise-scale Microsoft Fabric implementations.

GitHub Repository
FMD_FRAMEWORK

Hit Subscribe to get future release notes delivered straight to your inbox!

Feel free to leave a comment

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Exit mobile version