Moving Artifacts from Dev to Prod

[Ananth_Bhirappa]

I have three development workspaces (A,B,C) in microsoft fabric, need to deploy to production workspaces.

Workspace A have Lakehouses,Pipelines,Notebooks.

Workspace B have Lakehouses.

Workspace C have Lakehouses,Warehouses,Pipelines,PBI Reports.

I've three options 

Option 1 : Deploying all the artifacts which are present in Dev to Prod

Option 2 : ETL artifacts in separate workspace in Dev and Prod and remaining deploy as it is.

Option 3: Create separate production workspaces for data lakehouses, pipelines, notebooks, reports etc.,

What is the best approach to create prod environment??

[v-prasare]

Hi @Ananth_Bhirappa,
Hope your doing well.

@uselessai_in, @suparnababu8  thanks for your promt response.

As we haven’t heard back from you, we wanted to check in to see if the resolution provided by our Supers User and community members worked for you?

If you’re still facing any issues or have additional questions, please don’t hesitate to let us know.

We’re here to help and would be happy to assist further if needed. Looking forward to your feedback!

Thanks,

Prashanth Are

MS Fabric community support.

Did we answer your question? Mark post as a solution, this will help others!

If our response(s) assisted you in any way, don't forget to drop me a "Kudos"

[v-prasare]

Hi @Ananth_Bhirappa,

Hope your doing well.

if your query got resolved please mark post as a solution,this will help other community members find answers quickly.

Thanks,

Prashanth Are

MS Fabric community support.

[v-prasare]

@Ananth_Bhirappa, Thanks for actively participating MS Fabric community Support

As we haven’t heard back from you, we wanted to check in to see if the resolution provided by our Supers User and community members worked for you?

If you’re still facing any issues or have additional questions, please don’t hesitate to let us know.

We’re here to help and would be happy to assist further if needed. Looking forward to your feedback!

Thanks,

Prashanth Are

MS Fabric community support.

Did we answer your question? Mark post as a solution, this will help others!

If our response(s) assisted you in any way, don't forget to drop me a "Kudos"

[uselessai_in]

Hi, thanks for the question. Find all deployment related issues with their creative solutions here. I tested and implemented all of them. Hope it helps.

link - https://uselessai.in/dont-use-set-variable-activity-in-data-factory-pipeline-microsoft-fabric-bf74fa...

2. https://uselessai.in/microsoft-fabric-interesting-and-hidden-deployment-observations-important-bug-f...

3. https://uselessai.in/microsoft-fabric-stored-procedure-not-reflecting-warehouse-connection-change-in...

4. https://uselessai.in/microsoft-fabric-warehouse-deployment-issue-s-and-potential-solution-s-9ad36041...

[suparnababu8 · Accepted solution]

Hi @Ananth_Bhirappa 

If creating a production environment requires very careful consideration of organization, scalability, and maintainability. 

From your options, I will choose option 3. Becuase, it is best approach for creating a production environment. It offers the most organized and scalable solution, allowing you to manage each type of artifact independently. This separation can lead to better performance, easier troubleshooting, and more straightforward scaling. 

But, let's think your self take decessions as per you/your organisation needs.

Thanks you!