Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
Hi Joseph French_846,
Thank you for reaching out to the Microsoft Community. I appreciate your thoughtful questions. They’re important for understanding how the BigQuery connector works across Power BI and the Power Platform.
Below is a detailed breakdown based on current documentation and implementation:
1. Is it ODBC based?
No, the connector is not ODBC-based. Since the June 2021 update, Power BI Desktop and Power Platform Dataflows use a native connector (GoogleBigQuery.Database) that does not require third-party ODBC drivers.
In May 2025, Microsoft introduced a preview feature using Arrow Database Connectivity (ADBC) via Implementation="2.0", which improves performance for large-scale queries.
2. Is it encrypted?
Yes, encryption is enforced at multiple levels:
- In transit: All communication between Power BI/Power Platform and BigQuery uses HTTPS with TLS 1.2 or higher.
- At rest: BigQuery encrypts data using AES-256 by default. For advanced control, organizations can use Customer-Managed Encryption Keys (CMEK) via Google Cloud KMS
3. How are credentials stored?
- Power BI Desktop: OAuth tokens (for organizational accounts) or JSON keys (for service accounts) are stored encrypted in Windows Credential Manager under Microsoft.PowerBI.Desktop_store.
- Power BI Service (Microsoft 365 Cloud):
- Cloud-to-cloud: Credentials are stored in the Power BI Service Credential Store.
- On-premises gateway: Credentials are encrypted using Windows Data Protection API and stored within the gateway cluster.
4. How does this vary between Power BI Desktop and Microsoft 365 Cloud?
- Connection: Power BI Desktop uses the built-in native connector. No additional drivers are needed.
- Deployment: Desktop allows direct import. For cloud use, datasets must be published to Power BI Service.
- Refresh: Desktop supports manual refresh or automation via scripts. Power BI Service supports scheduled refresh and requires a gateway for on-premises sources.
- Advanced options: Desktop supports parameters like BillingProject, UseStorageApi, CommandTimeout. These are limited or require API configuration in Power BI Service.
- ADBC support: Currently available only in Power BI Desktop (Preview mode).
5. How does this vary with the Power Apps/Platform connector?
Both Power BI and Power Platform use the same native M-connector for BigQuery.
- Authentication: Supports both organizational accounts and service accounts.
- Data handling:
- Power BI supports Import and DirectQuery.
- Power Apps/Dataflows support Import only — data is stored in Dataverse or Dataflow storage, not queried live.
- Refresh:
- Power BI allows scheduled refresh or live queries.
- Power Platform refreshes data only when the Dataflow is manually or automatically triggered.
- Advanced options: Power BI offers more flexibility; Dataflows are more limited.
If this information helped clarify your current situation, please consider marking this reply as an answer. Doing so helps others facing similar questions find accurate guidance more easily.
For reference:
Google BigQuery connector - Power Query | Microsoft Learn
Encryption at rest | BigQuery | Google Cloud
If this information helped clarify your current situation, please consider marking this reply as an answer. Doing so helps others facing similar questions find accurate guidance more easily.
Thanks for your precious time. Have a nice day.
Best regards,
Rin-L MSFT | Microsoft Community Support Specialist