Power BI Metadata Connector – Privacy Policy

Last updated: 2025-11-17

This Privacy Policy describes how the Power BI Metadata Community Connector for Looker Studio (the “Connector”) processes information when you use it in your Looker Studio reports.

The Connector is implemented as a Google Apps Script Community Connector and executes within the Google Apps Script and Looker Studio runtime environment.

Summary: - The Connector retrieves Power BI metadata (not report data values) from your Power BI tenant using the Power BI Admin API. - The Connector does not store your credentials or metadata on any external server controlled by the connector author. - All processing occurs within Google infrastructure as part of Looker Studio and Apps Script.

1. Information we access

When you configure and use this Connector, it may access the following categories of information:

1.1 Configuration parameters

You provide the following configuration parameters when creating a data source:

• Azure AD Tenant ID
• Azure AD Client ID
• Azure AD Client Secret
• Power BI Workspace IDs (one or more GUIDs)
• Output Table selection (Measures or Measure-Column Associations)

These values are used by the Connector at runtime to:

• Perform a client-credentials OAuth2 flow against Azure AD.
• Obtain an access token for the Power BI Admin API.
• Call the Power BI Admin API to retrieve metadata about workspaces, datasets, tables, and measures.

The configuration values are stored by Looker Studio as part of your data source definition. They are not collected or stored by the connector author outside of Google systems.

1.2 Power BI metadata

Using the access token, the Connector calls the Power BI Admin API to retrieve metadata including, but not limited to:

• Workspace names
• Dataset names
• Table names
• Measure names
• DAX measure expressions
• Measure descriptions (if provided)

The Connector also parses DAX expressions locally (within Apps Script) to compute:

• Lists of referenced columns (e.g. Table[Column])
• Lists of referenced measures (e.g. [Measure])
• Lists of associated tables
• Per-measure, per-column association rows

The Connector does not access or process:

• Row-level data from fact tables
• Visualization-level user interactions beyond what Looker Studio itself provides to connectors (e.g. filters and requested fields)

2. How information is processed

All processing performed by the Connector happens within:

• The Looker Studio runtime, and
• The Google Apps Script execution environment associated with your script project.

The Connector:

1. Uses the configuration values you provide to request an access token from Azure AD.
2. Uses the access token to call the Power BI Admin API.
3. Receives a JSON response containing Power BI workspace and dataset metadata.
4. Parses that response and builds tabular data (measures and measure-column associations) for Looker Studio.
5. Returns only the requested fields to Looker Studio in the format required by the Community Connector API.

The Connector does not send your configuration parameters or Power BI metadata to any external servers controlled by the connector author.

3. Data storage and retention

• The Connector does not implement any external storage of credentials or metadata.
• Azure AD Tenant ID, Client ID, Client Secret, workspace IDs, and connector configuration values are stored by Looker Studio as part of the data source definition.
• Power BI metadata is held in memory only for the duration of the Apps Script execution and Looker Studio request.
• No long-term external database or file storage is used by the Connector.

However, logs may be written by Apps Script (e.g. via console.log / Logger.log), which are stored by Google as part of the Apps Script project logs. These logs are intended for debugging and typically do not contain sensitive data, but may occasionally include identifiers (e.g. workspace IDs) for troubleshooting purposes.

4. Access to your data

The Connector runs under:

• Your Google account (for Apps Script / Looker Studio), and
• The Azure AD application identity (service principal) used to obtain tokens for the Power BI Admin API.

The Connector can only access Power BI metadata that:

• Is available to the service principal according to your Azure AD and Power BI configuration, and
• Is permitted by the scopes/permissions you granted to the application.

The connector author does not have direct access to your Power BI environment or your Looker Studio account.

5. Sharing and disclosure

The connector author does not receive or share your data with third parties. Any sharing of reports or data within Looker Studio is controlled by you through Looker Studio’s sharing and permissions settings.

You are responsible for ensuring that sharing of reports and data sources complies with your organization’s policies.

6. Security

While the Connector itself does not store your data externally, the overall security of your data depends on:

• Your Google account security (e.g., strong passwords, 2-step verification).
• Your Azure AD and Power BI security configuration.
• Proper management of the Azure AD Client Secret (treat it as a sensitive credential).

If you suspect that your Azure AD credentials have been compromised, you should revoke or rotate the secret and update the connector configuration accordingly.

7. Your responsibilities

By using this Connector, you acknowledge that:

• You have the right to access the Power BI metadata being retrieved.
• You will configure and use the Connector in compliance with your organization’s security, privacy, and compliance policies.
• You are responsible for any data exposed through Looker Studio reports that use this Connector.

8. Changes to this Privacy Policy

This Privacy Policy may be updated from time to time to reflect changes in functionality, security practices, or applicable laws. The “Last updated” date at the top of this document will be revised when changes are made.

9. Contact

For questions about this Connector or this Privacy Policy, please use the support form.