Forum Discussion
Power BI Service not syncing - problem with git integration (Azure Devops) and Dpeloyment Pipeline
It seems the issue is solved now. I think MS has solved the bug, nothing was made from my side.
Hi Beu777 ,
I understand that you are facing persistent issues with Power BI Service Git integration and Deployment Pipelines since July 22, 2025, a structured diagnostic and remediation approach is necessary. First, review the Azure DevOps and Power BI Service activity logs to identify any failed or partial sync attempts that could indicate whether the Git sync process is being interrupted at the service or capacity level. Next, temporarily disconnect and relink the Git repository in your Power BI workspace, using a clean test branch. This helps rule out corruption or misconfiguration in the current linkage. Since a blank report successfully synced, test with incrementally more complex PBIP projects to determine whether semantic model complexity, folder structure, or features like incremental refresh are contributing to the failure. It's also advisable to align your project with the latest PBIP folder structure standards, as recent changes in Power BI such as Fabric folder support may conflict with legacy structures.
On the deployment side, the consistent failure to promote content from Development to Production is likely linked to Premium capacity connection health issues, as indicated by the backend error messages and correlation IDs. You should monitor your Premium capacity metrics in the Power BI Admin Portal for any signs of memory or CPU throttling. If capacity limitations are identified, consider temporarily moving the affected workspace to another capacity to isolate whether the issue is environment-specific. Additionally, split your deployment to isolate whether the problem lies within the report or semantic model. If the Power BI UI continues to fail, test deployments via the Power BI REST API or PowerShell, which may bypass UI-related issues and reveal more precise error behavior.
Finally, considering this issue began around the same time as other user reported cases, it may be tied to a service regression. Check the Microsoft Service Health Dashboard for your region especially wabi-us-east2 and review recent Power BI release notes for any related breaking changes. If the issue persists, escalate by opening a Microsoft support ticket, providing them with detailed logs, correlation and operation IDs, and clear steps to reproduce the error.
To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn.
Hope this helps.
Warm Regards,
Chaithra E.
Thanks fo the response Chaithra!
I'll split my answer in a few steps according to your suggestions:
1. Azure DevOps and Power BI activity logs:
Unfortunately I don't have access and couldn't reach the Power BI admin to get those logs yet.
2. Disconnect and relink Git Repo in Power BI Workspace
I've done that a thousand times, even created test workspaces to run multiple tests over new branches and new git repositories.
3. Test with more complex files (since a blank file works to sync)
Yes, I was gradually increasing the model complexity but the issue started to happen very soon with few tables in the model already.
4. Align your Project with latest PBIP folder structure standards
Can you tell me more about that? Not sure if this is related because the issue started to happen suddenly.
5. Monitor Fabric capacity
We monitor capacity all the time, and btw the fabric capacity broke many times due to unsuccessful deployment/git syncs.
6. Move workspace to another capacity
Check, also done that. We have two capacities to move workspaces between those.
7. Deploy via REST API
Done that too. Thought the same thing about UI issues, but the operation fails just as bad.
We raised a ticket to microsoft and they're still working to find out a cause.