Severe GitHub Integration Issues with Power BI Projects - Almost Completely Unusable

[mramirez1]

Hi Fabric Community,

I'm experiencing critical problems with the GitHub integration in Fabric that make it practically unusable for our team. This is particularly concerning since GitHub integration is mandatory for Power BI Projects and DirectLake.

The issue manifests in two main ways:

First, when trying to view files for commit/update, the Source Control functionality fails approximately 14 out of 15 attempts. When clicking on Source Control, I either get unhelpful error messages like "Unable To Sync Changes" or "Something went wrong" with no additional information or context about what's causing the problem.

Second, even on the rare occasions when I can see the files, the actual commit/update process itself fails roughly 14 out of 15 times as well. This means the complete workflow (viewing files AND successfully committing them) only works after dozens of attempts.

Our team is based in Santiago (GMT-4/GMT-3), and we're using Fabric for our data projects with DirectLake. This GitHub integration issue is severely impacting our ability to collaborate and maintain version control.

Has anyone else encountered similar problems? Are there any known workarounds or fixes? Any guidance from the Fabric team would be greatly appreciated, as this makes the mandatory GitHub integration essentially non-functional for actual production use.

Thank you for any help you can provide!

[v-ssriganesh]

Hi @mramirez1,

Thank you for reaching out to the Microsoft Fabric Community Forum. I also appreciate @pborah for sharing his valuable input.

We apologize for the inconvenience caused. As @pborah suggested, please consider raising a Microsoft support ticket. You can create one using the link below:

https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket

If this helps, please Accept it as a solution and give a "Kudos" so other members can find it more easily.

Thank you.

[v-ssriganesh]

Hi @mramirez1
Could you please confirm if the issue has been resolved after raising a support case? If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.

Thank you for your understanding and assistance.

[pborah]

If you're a Fabric administrator you can try accessing the activity log for the specific workspace to see what's going on in greater detail.

[mramirez1]

Hello pborah,

Thanks for your suggestion. As a Fabric administrator, I reviewed the documentation and pulled all logs for the past 24 hours in my workspace. Unfortunately, the logs only show information for the following operations:

ViewReport, GenerateEmbedToken, RunArtifact, RequestDataflowRefresh, ExportReport, GetTaskFlow, RefreshDataset, GetPowerBIDataModel, ViewWarehouse, GetPowerBIDataModelDiagramLayouts, Import, UpdateWarehouse, UpdateWarehouseMetadata, EditDataset, ReadArtifact, CreateReport

None of these operations relate to git/github integration. Even more concerning, the operations that fail don't provide any useful diagnostic information. Here's an example of a failed operation log:

{
"Id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"RecordType": 20,
"CreationTime": "2025-03-04T14:14:42Z",
"Operation": "GetPowerBIDataModel",
"OrganizationId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"UserType": 0,
"UserKey": "xxxxxxxxxxxxxxxxx",
"Workload": "PowerBI",
"ResultStatus": "Failed",
"UserId": "user@example.com",
"ClientIP": "xxx.xxx.xxx.xxx",
"UserAgent": "",
"Activity": "GetPowerBIDataModel",
"WorkSpaceName": "ExampleWorkspace",
"WorkspaceId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"ObjectId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"RequestId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"ObjectType": "Model",
"ObjectDisplayName": "example_model",
"Experience": "PowerBI",
"RefreshEnforcementPolicy": 0,
"BillingType": 0
}

Do you have any other suggestions for diagnosing these GitHub integration issues?

[pborah]

Thanks for checking @mramirez1 , the other set of logs I'd check would be in Github. Followed by a browser trace when you try to sync your workspace with Git. If you cannot find any clues there, you may need to raise a support ticket with Microsoft. This could be a severity 1 ticket if it is directly impacting your business right now to the point of end user activities coming to a halt. Otherwise a severity 2.

[mramirez1]

Thanks for the update, pborah. I've managed to capture the specific error during my testing:

{"code":"HttpRequestException","message":"Error while copying content to a stream."}

This clearly points to a connection/transfer issue with the GitHub integration. Since I've exhausted troubleshooting options through logs, I'll create a support ticket with Microsoft.

Could you direct me to the proper channel for submitting a support ticket for this issue? Based on your suggestion, I'll mark it as severity 2 since it's severely limiting our development workflow, though not completely halting all end-user activities.

[pborah]

@mramirez1 that's awesome you were able to capture the point of failure in your testing. Since you are a fabric admin, you should be able to get "help+support" in your admin portal wherein you should see the option to create a new support request.

[mramirezsal · Accepted solution]

We finally moved our repository from GitHub to Azure DevOps repos and we haven't had any problems, we stopped having errors and everything works perfectly.

[pborah]

That's great to hear @mramirezsal . We also use devops over github and we've never encountered any issues.

[v-ssriganesh]

Hi @mramirezsal,

We appreciate your efforts and are pleased to hear that your issue was resolved. Please mark the helpful response as "Accept as solution". This will assist other community members in resolving similar issues more efficiently.

Thank you.