Forum Discussion
Unable to connect to Google Bigquery data source (October 2025) due to ADBC US location error.
- 11 months ago
Hi Lawliim,
Thank you for reaching out to the Microsoft Fabric Community Forum and yes, you are right that this seems to have started after the recent Power BI October 2025 update. Also, thanks to grazitti_sapna, for his inputs on this thread.Based on the error message (Dataset ... was not found in location US), it looks like Power BI’s Google Big Query connector (ADBC-based) is defaulting to the US region, even when your dataset is stored in a regional location (such as europe-north1).
This behaviour has been reported by other users as well and appears to be a known issue with the latest connector build. You can try the following steps while Microsoft and Google work on a fix:
Switch back to the legacy connector: Go to File > Options and settings > Options > Preview features, uncheck “Use ADBC-based Big Query connector”, Restart Power BI Desktop and reconnect to your dataset.
If the issue persists, you can temporarily connect using the ODBC driver (Simba Big Query) as a workaround. Check your dataset’s region in the Google Cloud Console to confirm the exact location Power BI currently needs the connector to match that region correctly.
You can refer this solved thread: https://community.fabric.microsoft.com/t5/Power-Query/Power-BI-BigQuery-Connector-Fails-for-Regional-Datasets-us-west2/m-p/4830273For connector reference, refer this official Microsoft link: https://learn.microsoft.com/en-us/power-query/connectors/google-bigquery
Hope this helps clarify the situation and gives you a working path until an update is released.
Thank you for using the Microsoft Fabric Community Forum.
There is an error due to location mismatch—your BigQuery project is in europe-north1, but the connector or query is looking in the US location. You need to explicitly specify the correct project and location in your connection string or settings to avoid this issue. Check your Adbc/BigQuery connector configuration and verify your dataset and location parameters
Yes I am using PowerBI desktop,
There is a mismatch but I cannot specify location in the integration --> a bug since it defaults to fixed US. It has now been confirmed and escalated to product team by MSFT support that i showed. Since it is related to the 2025-09-16 Fix for bigquery under known issues. I reverted to August 2025 build and it worked without a hitch.
Additionally the answer/solution also works by opting out in file options.
- Shubham_rai95511 months ago
Super User
.
- Lawliim11 months ago
Advocate I
But you have not provided a solution, since there is no explicit way to set location in connection string nor configuration. If you read the msft-employees answer you should've seen it is a known bug. They also had the correct temporary solution of checking it off in file/options.
What are you thinking really?