How to Connect BigQuery to Power BI

Power BI has a native Google BigQuery connector that supports both Import and DirectQuery, so connecting them is straightforward; the decisions that matter are which storage mode to use, how to authenticate, and how to stop BigQuery query costs from creeping up. BigQuery bills largely by the data each query scans, so a careless DirectQuery report can quietly run up a bill. Import gives fast, stable reports refreshed on a schedule. DirectQuery gives live data and handles very large datasets, but sends a query to BigQuery on every interaction. This guide covers both, plus the GA4 export angle and the cost controls that keep a deployment healthy.

Import versus DirectQuery

Import mode loads a copy of the data into Power BI's in-memory engine. Visuals are fast, calculations are unconstrained, and BigQuery is only queried at refresh time. This is the default recommendation for most reports. The limits are dataset size and freshness, since users see data as of the last refresh.

DirectQuery leaves data in BigQuery and sends a query for each visual interaction. You get near-live data and can report over datasets too large to import, but visuals are slower, some calculations are restricted, and every slice and filter can scan data and cost money. Composite models let you mix the two, importing small lookup tables while keeping a huge fact table in DirectQuery.

For most organisations, Import with a sensible refresh schedule is cheaper and faster. Reserve DirectQuery for genuine real-time needs or volumes that cannot be imported.

Authentication and the gateway

Power BI connects to BigQuery with OAuth for individual users or a service account for shared, automated refresh. For production, a service account with least-privilege access is usually the cleanest, since it does not depend on one person's login. Because BigQuery is a cloud service, scheduled cloud-to-cloud refresh often works without an on-premises gateway, though you should confirm your path is supported. Manage credentials centrally and rotate them rather than embedding personal logins in shared datasets. Our guide on data refresh and gateway setup covers the wider picture.

The GA4 export angle

A common reason to connect BigQuery to Power BI is GA4. Google Analytics 4 can export raw event data to BigQuery, which gives you far more control than the standard GA4 reports, including custom attribution and unsampled data. The catch is volume: raw GA4 event tables grow fast and are expensive to scan in full. The fix is to transform and pre-aggregate the events in BigQuery into tidy daily tables, then have Power BI read those. This keeps cost down and reports fast. If you only need standard metrics, our guide on connecting GA4 to Power BI covers the lighter-weight route without BigQuery.

Controlling BigQuery costs

BigQuery bills largely for the data each query scans, so a careless Power BI deployment can run up spend, especially with DirectQuery. Practical controls:

• Prefer Import unless freshness genuinely requires DirectQuery. A scheduled refresh costs far less than thousands of interactive queries.
• Pre-aggregate in BigQuery. Build summary tables or materialised views so Power BI reads small, tidy data instead of scanning raw tables.
• Partition and cluster tables so queries scan only the partitions they need, especially for date-based GA4 data.
• Limit refresh frequency to what the business actually needs; hourly refresh on data reviewed once a day is waste.
• Consider flat-rate or capacity pricing if query volume is high and predictable (as of 2026, confirm current pricing options).
• Monitor query cost in BigQuery to find expensive, frequently run report queries and optimise them.

These steps routinely cut BI-driven BigQuery spend without users noticing any loss of capability.

Getting it done well

A well-architected BigQuery-to-Power BI deployment balances speed, freshness and cost rather than defaulting to one mode for everything. As a rough guide for UK delivery, a focused dashboard build starts from £6,000 with typical projects at £8,000–£14,000, and senior Power BI day rates run roughly £400–£850 a day (as of 2026, confirm current pricing). When the BigQuery feed needs governed pipelines into your reporting, that is our data integration and warehousing work. If your data lives in the wider Microsoft stack, see our Power BI and Microsoft Fabric work, and for a broader view of cloud data stores our guide on connecting Snowflake to Power BI covers the same trade-offs.

A Trusted Numbers Review checks your BigQuery setup, agrees the storage mode and recommends the controls that keep query spend predictable. Book one to connect BigQuery to Power BI in a way that stays fast and stays affordable.