Power BI BigQuery Connector Fails for Regional Datasets (us-west2) – Works Only with US Multi-Region

[Siddharthaaman]

Hi Community,

I’m running into a region/location issue with the Power BI BigQuery connector and would appreciate guidance or confirmation if this is a known limitation.

Setup:

• Power BI connected to BigQuery using a service account

• Service account has required roles (BigQuery Data Viewer, Job User, etc.)

• Dataset locations tested:

  • us-west2 (single region)

  • US (multi-region)

    Problem:
    I was previously able to connect Power BI to a BigQuery dataset in us-west2 and view tables.

    Recently, after refreshing the connection to bring in new tables, I started getting this error:

    DataSource.Error: ADBC: Cannot execute <ExecuteQueryInternalAsync>b__1 after 5 tries. Last exception: The service bigquery has thrown an exception. No HttpStatusCode was specified. Job sfc-warehouse-optimization/US/job_310da4af_2131_4976_a14f_35e037748597 contained 2 error(s). First error message: Not found: Dataset project:dataset was not found in location US
    Details:
    DataSourceKind=GoogleBigQuery
    DataSourcePath=GoogleBigQuery
    AdbcStatus=1
    SQLState=
    NativeError=0

     

    When I test with a dataset in the US multi-region, the connector works fine and tables load.
    When I try with us-west2 (or other single-region datasets), I consistently get the “not found in location US” error.

    Questions:

    1. Does Power BI’s BigQuery connector only support US multi-region datasets?

    2. Has there been a recent change that removed support for single-region datasets like us-west2?

    3. Is there a way to configure the connector or Advanced Editor in Power BI to explicitly target the dataset’s region (e.g., us-west2) instead of defaulting to US?

       Any documentation link, workaround, or confirmation would be greatly appreciated.

       Thanks in advance!

[v-sgandrathi · Accepted solution]

Hi @Siddharthaaman,

Thank you for bringing this up—I see how the dataset region and BigQuery connector can be confusing.

This error happens because BigQuery requires queries to run in the same region as the dataset. If the connector sends a job to US but your dataset is in us-west2, BigQuery will show the message: “Dataset … was not found in location US.”

Currently, this isn’t a BigQuery limitation but a known issue with the new ADBC-based BigQuery connector implementation (Implementation="2.0" in M). There are reports that it can mistakenly default to the US multi-region, which causes issues for regional datasets like us-west2.

1. Does Power BI’s BigQuery connector only support US multi-region datasets?
No, the connector does support regional datasets like us-west2. The error you’re seeing happens because the new ADBC connector sometimes defaults to the US multi-region, even when your dataset is regional.

2.Has there been a recent change that removed support for single-region datasets like us-west2?
No change has removed support. What you’re running into is a regression with the new ADBC (Implementation=2.0) connector. Several users have reported this issue starting recently when using regional datasets.

3.Is it possible to configure the connector or use the Advanced Editor in Power BI to specify the dataset’s region? 

At the moment, there isn’t a region picker available in the UI. However, you can address this by disabling the new connector in Options → Preview features, or by removing Implementation="2.0" from your M query to revert to the stable connector that supports regional datasets. In the Advanced Editor, ensure your source includes a billing project, such as:

Source = GoogleBigQuery.Database([BillingProject="your-project"])
To ensure your SQL queries resolve correctly, always fully qualify table names using the format project.dataset.table.

https://learn.microsoft.com/en-us/power-query/connectors/google-bigquery
DirectQuery in Power BI - Power BI | Microsoft Learn

Thank you.

[Siddharthaaman]

---

Hi @v-sgandrathi,

I wanted to share a quick update — I removed Implementation="2.0" from the M Query of the existing tables, and that resolved the issue.

Additionally, I disabled the "Use new BigQuery connector implementation" option in the Preview Features. This prevents other tables from defaulting to the Implementation=2.0 connection.

Thanks again for pointing me in the right direction — your solution worked perfectly!

[v-sgandrathi]

Hi @Siddharthaaman,

Great to know the solution worked! Appreciate you sharing the extra steps you took — that’s really helpful context.

Thank you and Continue Using Microsoft Fabric Cpmmunity Forum.

[v-sgandrathi · Accepted solution]

Hi @Siddharthaaman,

Thank you for bringing this up—I see how the dataset region and BigQuery connector can be confusing.

This error happens because BigQuery requires queries to run in the same region as the dataset. If the connector sends a job to US but your dataset is in us-west2, BigQuery will show the message: “Dataset … was not found in location US.”

Currently, this isn’t a BigQuery limitation but a known issue with the new ADBC-based BigQuery connector implementation (Implementation="2.0" in M). There are reports that it can mistakenly default to the US multi-region, which causes issues for regional datasets like us-west2.

1. Does Power BI’s BigQuery connector only support US multi-region datasets?
No, the connector does support regional datasets like us-west2. The error you’re seeing happens because the new ADBC connector sometimes defaults to the US multi-region, even when your dataset is regional.

2.Has there been a recent change that removed support for single-region datasets like us-west2?
No change has removed support. What you’re running into is a regression with the new ADBC (Implementation=2.0) connector. Several users have reported this issue starting recently when using regional datasets.

3.Is it possible to configure the connector or use the Advanced Editor in Power BI to specify the dataset’s region? 

At the moment, there isn’t a region picker available in the UI. However, you can address this by disabling the new connector in Options → Preview features, or by removing Implementation="2.0" from your M query to revert to the stable connector that supports regional datasets. In the Advanced Editor, ensure your source includes a billing project, such as:

Source = GoogleBigQuery.Database([BillingProject="your-project"])
To ensure your SQL queries resolve correctly, always fully qualify table names using the format project.dataset.table.

https://learn.microsoft.com/en-us/power-query/connectors/google-bigquery
DirectQuery in Power BI - Power BI | Microsoft Learn

Thank you.

[v-sgandrathi · Accepted solution]

Hi @Siddharthaaman,

As we have not received a response from you yet, I would like to confirm whether you have successfully resolved the issue or if you require further assistance.

Thank you for your cooperation. Have a great day.