Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

July 7 - July 17 | Round 2 of the Power BI Dataviz World Championships. Don't miss your chance! Learn more

Reply
CarlosPBIVision
New Member

Power BI Connection Error with BigQuery

Hi,

 

We have some reports that we expected to get refreshed on a daily basis on Power BI Service (all tables are connected to our data warehouse on BigQuery). But this morning, for some reason, we got this error for all of them:

ERROR [HY000] [Microsoft][BigQuery] (131) Unable to authenticate with Google BigQuery Storage API. Check your account permissions.

We already tried this thoroughly but it didn't work out: https://community.powerbi.com/t5/Service/BIgQuery-Account-Permissions/m-p/1390692

 

Does anybody know we could solve this? It seems it is happenning almost exclusively for the most heavy tables in terms of rows and size

 

Thanks

1 ACCEPTED SOLUTION
CarlosPBIVision
New Member

Hi Selina, we already solved the problem by contacting PBI Support directly.

 

To help future users: the solution was to go to the "Source" step of every PowerQuery table that we're ingesting from BigQuery, and substituting

Source = GoogleBigQuery.Database()

 With

Source = GoogleBigQuery.Database([BillingProject = "Insert-Your-Project-ID-Here"])

 

That's it. The catch is that it must be for ALL tables coming from BQ, not only the large, problematic ones.

 

Best,

 

View solution in original post

4 REPLIES 4
CarlosPBIVision
New Member

Hi Selina, we already solved the problem by contacting PBI Support directly.

 

To help future users: the solution was to go to the "Source" step of every PowerQuery table that we're ingesting from BigQuery, and substituting

Source = GoogleBigQuery.Database()

 With

Source = GoogleBigQuery.Database([BillingProject = "Insert-Your-Project-ID-Here"])

 

That's it. The catch is that it must be for ALL tables coming from BQ, not only the large, problematic ones.

 

Best,

 

This solution worked for me, (thanks!), however I am struggling to understand why this is suddenly neccessary on tables which worked fine previously? Do you have any insight on that?

Anonymous
Not applicable

Hi @CarlosPBIVision ,

 

I'm glad you solved the problem. You can mark the reply as a solution to better facilitate other members to find it.

 

Best regards,

Community Support Team Selina zhu

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

Anonymous
Not applicable

Hi @CarlosPBIVision ,

 

Have you had this error before? Have you tried to re-upload the report to the service for refreshing?

 

I reviewed the document you shared and indeed, there were errors consistent with yours and many members participated in it to share their views. but there is no solution to your problem, is there?

 

Best regards,

Community Support Team Selina zhu

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

Helpful resources

Announcements
FabCon and SQLCon Barcelona 2026

FabCon & SQLCon – Barcelona 2026

Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.

60 days of Data Days Carousel

Data Days 2026

Join Data Days 2026: 60 days of free live/on-demand sessions, challenges, study groups, and certification opportunities.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.