Forum Discussion
Severe GitHub Integration Issues with Power BI Projects - Almost Completely Unusable
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.
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": "[email protected]",
"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?
Solution SageThanks 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.
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.
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.