Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
I am trying to figure out how to collaboratively work on Power BI reports using the Power BI workspace Git integration feature. I know how to enable Git feature in my workspace as well as know how to connect my workspace to an Azure Repo, but I don't fully understand the role of Power BI Service here. My question is, if me and another person were to work on the same reporting (same version) at the same time on Power BI Desktop and we both publish the report to Service let's say 1min apart to commit our changes to Azure Repos, I assume that whoever publishes last to Service workspace replaces all the work the other person been doing, with their own work - is this correct? If so, then what is the point of the Git feature? How does one 'lock' the files when someone is working on them to avoid two different copies being created at the same time?
I'm sure I am missing a step/idea about this - help?
Solved! Go to Solution.
Hi @klaudias18
My understanding is that you save your changes into git, which then goes into azure Dev ops. Once it is in Azure Devops, it will then send those changes through to the Power BI service. You no longer interact directly with the power of the art servers when you are working with git integration.
Hi @klaudias18
My understanding is that you save your changes into git, which then goes into azure Dev ops. Once it is in Azure Devops, it will then send those changes through to the Power BI service. You no longer interact directly with the power of the art servers when you are working with git integration.