Git integration in Power BI service - slow sync to workspace

[Ready2excel]

Hi everyone,

We use Azure DevOps as our Git repository and have it connected to our Power BI workspace. Our typical workflow is Git-first: changes are made in DevOps and then synced to the workspace.

However, we've been running into performance issues with the Git integration in the Power BI service. Specifically:

• Syncing changes from Git to the workspace can sometimes take a very long time.

• Reverting changes in the service using the "undo" option also seems slow and unresponsive at times.
  Just to clarify: we usually don’t make any changes directly in the service. However, we occasionally see unexpected changes in the workspace — possibly due to Power BI updates or internal service behavior — which we then either undo or commit as needed.

I'm wondering if others are experiencing the same behavior.
Is this a known issue, or are there specific reasons why these operations might be slow (e.g., repo size, number of items, etc.)?

Any insights, workarounds, or advice would be greatly appreciated!

Thanks in advance.

[v-saisrao-msft · Accepted solution]

Hi @Ready2excel,

Thank you for reaching out to the Microsoft Fabric Forum Community.

The issue you are facing slow syncing in git integration is how the undo function in power bi doesn’t simply rollback change. It triggers a full workspace resync from Git, which re-applies all items and can even delete those not present in the Git repository. This can be especially time-consuming if your workspace contains many items or large semantic models. 

Try the below approach:

• Reduce Workspace Complexity: If possible, split large repositories into smaller logical workspaces. Keep only the necessary in each workspace to minimize sync surface area. 

• Use the Power BI REST API to Monitor Sync Status: status checks and logging via REST or Activity Logs can give better insights into when syncs start/finish, helping with troubleshooting. 

Please refer to the link below: 

Known issue - Git integration undo action appears after initial sync fails - Microsoft Fabric | Micr... 

If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.

Thank you.

[v-saisrao-msft · Accepted solution]

Hi @Ready2excel,

Thank you for reaching out to the Microsoft Fabric Forum Community.

The issue you are facing slow syncing in git integration is how the undo function in power bi doesn’t simply rollback change. It triggers a full workspace resync from Git, which re-applies all items and can even delete those not present in the Git repository. This can be especially time-consuming if your workspace contains many items or large semantic models. 

Try the below approach:

• Reduce Workspace Complexity: If possible, split large repositories into smaller logical workspaces. Keep only the necessary in each workspace to minimize sync surface area. 

• Use the Power BI REST API to Monitor Sync Status: status checks and logging via REST or Activity Logs can give better insights into when syncs start/finish, helping with troubleshooting. 

Please refer to the link below: 

Known issue - Git integration undo action appears after initial sync fails - Microsoft Fabric | Micr... 

If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.

Thank you.

[Ready2excel]

hi @v-saisrao-msft,

Thank you for your response and the suggestions.

Unfortunately, further reducing the size or complexity of the repository isn't feasible in our current setup. However, I will definitely look into using the Power BI REST API to monitor the sync status more effectively.

Just to clarify: does a regular Git-to-workspace sync (not triggered by an undo action) also perform a full resync from Git, or does it behave differently?

Thanks again for your support!

[v-saisrao-msft]

Hi @Ready2excel,
I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please Accept it as a solution and give it a 'Kudos' so others can find it easily.
Thank you.

[v-saisrao-msft]

Hi @Ready2excel,

A normal Git-to-workspace sync in Power BI operates differently from the "Undo" operation and normally doesn't complete a resynchronization. Rather, it only goes ahead and applies the minimal changes initiated between the workspace and the most recent Git repository commit. Due to this design, normal syncs are considerably faster and use fewer resources. By removing all the active items and reimporting everything from Git so that it is an exact replica of the repository, the Undo command, however, fully resynchronizes the workspace. This, which can be considerably slower if your workspace has a great deal of artifacts or large semantic models, could delete any items that are not in the Git repository. 

If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly. 

Thank you. 

[Ready2excel]

Hi @v-saisrao-msft 

Thank you for the explanation.

However, I’ve noticed that a normal Git-to-workspace sync can sometimes still take quite a long time in practice. Could you explain what might cause this process to be slow?

[v-saisrao-msft]

Hi @Ready2excel,

We haven’t heard back from you regarding your issue. If it has been resolved, please mark the helpful response as the solution and give a ‘Kudos’ to assist others. If you still need support, let us know.

Thank you.

[v-saisrao-msft]

Hi @Ready2excel,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[v-saisrao-msft · Accepted solution]

Hi @Ready2excel,

Sometimes, due to large semantic models or complex reports, if the workspace contains many items or artifacts, it may take longer to process. Other factors include background service queuing, dependency checks, and the size or structure of the Azure DevOps repository.  

Overview of Fabric Git integration - Microsoft Fabric | Microsoft Learn

If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.

Thank you.