Forum Discussion
Best practices to implement and deploy a general Fabric solution for many customers
- 3 months ago
HI pmscorca,
For most enterprise multi-customer Fabric implementations, it is generally recommended to use a standardized Fabric architecture with the Medallion design, Deployment Pipelines, Git Integration, and CI/CD. Custom workloads are better suited for ISV or platform-style scenarios that require advanced Fabric extensibility, custom user experiences, or marketplace-oriented product packaging, but these usually involve much higher engineering effort and operational complexity.
Implement Medallion Lakehouse Architecture in Fabric - Microsoft Fabric | Microsoft Learn
Overview of Fabric deployment pipelines - Microsoft Fabric | Microsoft Learn
The Microsoft Fabric deployment pipelines process - Microsoft Fabric | Microsoft LearnOverview of Fabric Git integration - Microsoft Fabric | Microsoft Learn
Get started with Git integration - Microsoft Fabric | Microsoft Learn
Thank you.
Hi, thanks for your reply, but you have suggested two alternatives.
Which is the best one in terms of architecture, development and deployment?
HI pmscorca,
For most enterprise multi-customer Fabric implementations, it is generally recommended to use a standardized Fabric architecture with the Medallion design, Deployment Pipelines, Git Integration, and CI/CD. Custom workloads are better suited for ISV or platform-style scenarios that require advanced Fabric extensibility, custom user experiences, or marketplace-oriented product packaging, but these usually involve much higher engineering effort and operational complexity.
Implement Medallion Lakehouse Architecture in Fabric - Microsoft Fabric | Microsoft Learn
Overview of Fabric deployment pipelines - Microsoft Fabric | Microsoft Learn
The Microsoft Fabric deployment pipelines process - Microsoft Fabric | Microsoft Learn
Overview of Fabric Git integration - Microsoft Fabric | Microsoft Learn
Get started with Git integration - Microsoft Fabric | Microsoft Learn
Thank you.