Forum Discussion

EynnerLH12's avatar
EynnerLH12
Copper Contributor
Mar 10, 2026

Connection Failed Issue scanning Google BigQuery from Microsoft Purview Azure environment

Hi everyone, I am currently setting up a laboratory environment in Microsoft Purview to catalog data from Google BigQuery, but I am encountering a connection error during the testing phase. 

I have verified that the Service Account has the required permissions in GCP (BigQuery Metadata Viewer and BigQuery Data Viewer) and the JSON key is correctly stored in Azure Key Vault. Has anyone faced a similar issue when connecting BigQuery to Purview recently? I want to rule out if this is a networking issue or a specific configuration requirement for the BigQuery connector that I might be missing. Thanks in advance for your help!

BIGQUERY
purview

2 Replies

  • AS1522's avatar
    AS1522
    Icon for Microsoft rankMicrosoft
    Mar 11, 2026

    Hi ,

     

    Please check this : 

     

    1. Dataset location
      Microsoft Purview currently supports scanning BigQuery datasets only in the US multi‑regional location. Datasets in EU or regional locations (e.g., europe-west1, us-east1) will cause connection or scan issues.
    2. Required IAM roles
      In addition to BigQuery Metadata Viewer and BigQuery Data Viewer, the service account must also have BigQuery Job User.
    3. Azure Key Vault permissions
      Ensure the Microsoft Purview Managed Identity has Secrets → Get permission on the Key Vault storing the JSON key.
    4. SHIR / Java (if applicable)
      If using Self‑Hosted Integration Runtime, verify Java 11 and a supported Simba BigQuery JDBC driver are installed.

    In most cases, validating the dataset region and Key Vault access resolves the issue. Try and share of this solves the problem.

    • EynnerLH12's avatar
      EynnerLH12
      Copper Contributor
      Mar 16, 2026

      Thanks for the detailed reply! I’ve gone through the checklist and confirmed the following:

      • Dataset Location:Verified, it's in US multi-regional.
      • IAM Roles:The Service Account has BigQuery Metadata Viewer, Data Viewer, and Job User roles assigned.
      • Azure Key Vault:The Purview Managed Identity has Secrets → Get permissions correctly set up.
      • Java: Java 11 is already installed and configured on the SHIR server.

      The only thing still tripping me up is point #4 (Simba JDBC). I’ve downloaded the Simba ZIP, but I'm unsure about the exact folder structure for the extracted files.

       

      I've placed the .jar files in a flat directory (e.g., C:\Drivers\BigQueryJDBC) and pointed to it in the Purview scan settings, but I'm not sure if the SHIR is actually picking up that path to use the drivers.

      Is there a specific way to verify if the runtime is correctly 'seeing' the drivers, or is there a mandatory folder hierarchy I should be following? I suspect this path recognition might be the root cause of the connection error