> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/2025.1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.immuta.com/2025.1/configuration/application-settings/how-to-guides/bi-tools/power-bi.md).

# Power BI Configuration Example

## Specify authentication method

When creating a data source in Power BI, specify **Microsoft Account** as the authentication method, if available. This setting allows you to use your enterprise SSO to connect to your compute platform.

## Set up DirectQuery

After connecting to the compute platform and the tables to use for your data source, select **DirectQuery** to connect to the data source. This setting is required for Immuta to enforce policies.

## Publish data

After you publish the datasets to the Power BI service, force users to use their personal credentials to connect to the compute platform by following the steps below.

1. Enable SSO in the tenant admin portal under **Settings -> Admin portal -> Integration settings**.
2. Find the option to manage **Data source credentials** under **Settings -> Datasets**.
3. For most connectors you can enable **OAuth2** as the authentication method to the compute platform.
4. Enable the option **Report viewers can only access this data source with their own Power BI identities using DirectQuery**. This forces end-users to use their personal credentials.

## Resources

* Snowflake guides:
  * <https://www.snowflake.com/blog/using-sso-between-power-bi-and-snowflake>
  * <https://docs.snowflake.com/en/user-guide/oauth-powerbi>
* Databricks guide: <https://learn.microsoft.com/en-us/azure/databricks/partners/bi/power-bi#access-azure-databricks-data-source-using-the-power-bi-service>
* Redshift guide: <https://aws.amazon.com/blogs/big-data/integrate-amazon-redshift-native-idp-federation-with-microsoft-azure-ad-and-power-bi>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.immuta.com/2025.1/configuration/application-settings/how-to-guides/bi-tools/power-bi.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.