Git Integration Best Practise

[hlbchant]

Hi everyone,

I'm looking for some advice on how to handle workspace Git integration in Microsoft Fabric for our development process. Our architecture includes one main data engineering workspace (with dev/test/prod environments) and separate workspaces for each business domain (e.g., HR, IT) for their reporting needs. These business domain workspaces will contain only semantic models and reports, which will reference lakehouses in the data engineering workspace. Access to these workspaces will be restricted to prevent untrained developers from creating semantic models.

How would you manage Git integration in this setup and use the inbuilt deployment pipelines? In the past, I've used VS Code outside of Power BI Service to create branches for new reports and deployed them using Python scripts. However, this approach doesn't work for all Fabric items, such as notebooks and pipelines, which need to be built directly in the service.

Any insights or experiences you can share would be greatly appreciated!

Thanks!

[v-prasare]

Hi @hlbchant, as we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?

Thanks,

Prashanth Are

MS Fabric community support

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query

[v-prasare]

Hi @hlbchant, as we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?

Thanks,

Prashanth Are

MS Fabric community support

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query

[suparnababu8 · Accepted solution]

Hi @hlbchant 

You may follow the some of best practises as outlined below.

• Create seperate workspace for different teams. Such as create data engineering workspaces for  your dev/test/prod environments and connect with each environment to sepearate Github branch to manage the version controlling.
• As per business specific requiremet (HR,Admin) create sepearte workspaces and in this workspace, connect with data engineering workspace having only sematic model and Power BI reports.
• syncrnize the fabirc items b/w workspace and git brach regularly.
• Restrict the access by using RLS in business workspaces for preventing untrained developers.
• Cming to deployement pipelines, create deployement pipelines and assign dideicated wokrspace each three stages and deploy the content from one stage to another stage. 

If you need additional info, pls go thorugh below documentation. It might helps you.

The Microsoft Fabric deployment pipelines process - Microsoft Fabric | Microsoft Learn

Best practices for lifecycle management in Fabric - Microsoft Fabric | Microsoft Learn

Git integration workspaces - Microsoft Fabric | Microsoft Learn

Overview of Fabric Git integration - Microsoft Fabric | Microsoft Learn

Thank you!!!