How to Structure a Project in Microsoft Fabric Using the Medallion Model (Bronze, Silver, Gold)

[nel_hmous69216]

Following the implementation of Microsoft Fabric in the medallion model, I would like to know how to structure the project in terms of file architecture across the different layers (Bronze, Silver, Gold), and how to structure the Data Products to make them available to end-users who will build their BI reports.

[v-sathmakuri · Accepted solution]

Hi @nel_hmous69216 ,

Thank you for reaching out to Microsoft Fabric Community.

The Medallion Architecture (Bronze, Silver, Gold) is a best-practice layered approach to managing data transformations in a lakehouse environment. Microsoft Fabric fully supports this model through OneLake, Lakehouses, and Notebooks/Spark, enabling scalable data engineering and analytics workflows.

Folder Structure in OneLake (File Architecture)

     Organize your Lakehouse as follows:

• Bronze Layer: Raw, ingested data. Little to no transformation. Use shortcuts to source files if possible.
• Silver Layer: Cleaned and enriched data, with deduplication and type standardization.
• Gold Layer: Business-level curated data products (e.g., dimensional models) ready for BI consumption.

Data Products & Access for BI Users

     Use Gold Layer Tables as the foundation for your Data Products:

• Model data in semantic models (previously Power BI datasets) built directly on top of the Gold Lakehouse tables.
• Publish Gold tables to Fabric Data Warehouses for access via Power BI reports.
• Create Data Products in Fabric by promoting curated gold-level data as certified or endorsed datasets.

Recommended Practices

• Use pipelines or notebooks to orchestrate ETL across bronze → silver → gold layers.
• Define Delta Lake format for tables to support ACID transactions.
• Use Dataflow Gen2 for ingestion and transformation of structured data.
• Secure datasets using sensitivity labels, row-level security, and workspace roles.

Please refer to below documentation for more insights:

https://learn.microsoft.com/en-us/fabric/onelake/onelake-medallion-lakehouse-architecture 

https://learn.microsoft.com/en-us/training/paths/implement-lakehouse-microsoft-fabric/ 

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! 

Thank you!!

[v-sathmakuri]

Hi @nel_hmous69216 ,

I hope the information provided is helpful. Feel free to reach out if you have any further questions or would like to discuss this in more detail. If responses provided answers your question, please accept it as a solution so other community members with similar problems can find a solution faster.

Thank you!!

[v-sathmakuri]

Hi @nel_hmous69216 ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If the responses has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you!!

[v-sathmakuri · Accepted solution]

Hi @nel_hmous69216 ,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you!!

[v-sathmakuri · Accepted solution]

Hi @nel_hmous69216 ,

Thank you for reaching out to Microsoft Fabric Community.

The Medallion Architecture (Bronze, Silver, Gold) is a best-practice layered approach to managing data transformations in a lakehouse environment. Microsoft Fabric fully supports this model through OneLake, Lakehouses, and Notebooks/Spark, enabling scalable data engineering and analytics workflows.

Folder Structure in OneLake (File Architecture)

     Organize your Lakehouse as follows:

• Bronze Layer: Raw, ingested data. Little to no transformation. Use shortcuts to source files if possible.
• Silver Layer: Cleaned and enriched data, with deduplication and type standardization.
• Gold Layer: Business-level curated data products (e.g., dimensional models) ready for BI consumption.

Data Products & Access for BI Users

     Use Gold Layer Tables as the foundation for your Data Products:

• Model data in semantic models (previously Power BI datasets) built directly on top of the Gold Lakehouse tables.
• Publish Gold tables to Fabric Data Warehouses for access via Power BI reports.
• Create Data Products in Fabric by promoting curated gold-level data as certified or endorsed datasets.

Recommended Practices

• Use pipelines or notebooks to orchestrate ETL across bronze → silver → gold layers.
• Define Delta Lake format for tables to support ACID transactions.
• Use Dataflow Gen2 for ingestion and transformation of structured data.
• Secure datasets using sensitivity labels, row-level security, and workspace roles.

Please refer to below documentation for more insights:

https://learn.microsoft.com/en-us/fabric/onelake/onelake-medallion-lakehouse-architecture 

https://learn.microsoft.com/en-us/training/paths/implement-lakehouse-microsoft-fabric/ 

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! 

Thank you!!

[nel_hmous69216]

Hi,

We are using Microsoft Fabric from few months, and we are facing now an issue on our workspace in which the "Starter pool" of Spark no longer exists,

we have a message "Admin has disabled the customized pool" and now we cannot execute notebooks

Is there someone who had already faced that, or can you advice us how to workaround this ?

Thank you in advance.