Forum Discussion
Post ProdigyBest practices to implement and deploy a general Fabric solution for many customers
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.
Super UserHi pmscorca
For best practices on Fabric, I recommend referring to the Reference Architectures available on Microsoft documentation. There are multiple reference architectures for different industries, and here is a link related to Customer Churn:
Customer Churn Architecture with Fabric Real-Time Intelligence - Microsoft Fabric | Microsoft Learn
You can explore this link and review other reference architectures as well.
Regarding deployment methods in Fabric, there are useful learning materials that cover best practices, Git integration, deployment pipelines, and the use of reusable variables for stage-based configuration. Here are a couple of learning material and a blog:
Best practices for lifecycle management in Fabric - Microsoft Fabric | Microsoft Learn
Application lifecycle management tutorial - Microsoft Fabric | Microsoft Learn
Optimizing for CI/CD in Microsoft Fabric - Microsoft Fabric Community
Post ProdigyHi,
I was hoping to have some guidelines to follow for implementing and distributing a standard solution that could be useful to many customers, while protecting intellectual property. For example, would building a workload be the best choice? How should it be organized?
Thanks
KevinChantIf IP is really a big thing then a custom workload might be a good option depending on your skillsets. Alternatively, look to develop and test a standardized solution locally and then deploy to client tenants through a service such as Azure Pipelines.
- pmscorca
Hi, thanks for your reply, but you have suggested two alternatives.
Which is the best one in terms of architecture, development and deployment?
- v-saisrao-msft
Community Support
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.