Forum Discussion

EynnerLH12's avatar
EynnerLH12
Occasional Reader
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!

1 Reply

  • 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.