> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/powerbi/understand-power-bi-license-requirements.md).

# Understand Power BI license requirements

Check which package, permissions, and external access you need for Power BI.

Power BI use depends on both OutSmart access and Microsoft access.

Check both before you start the setup.

### What you need

* an active Power BI Power-Up in OutSmart
* access to **Settings → Data Sync**
* access to Microsoft Power BI for reporting

### What to verify

Check these points in your account:

* the Power BI Power-Up is active
* the right user can manage the setup
* the Data Sync settings are available

{% hint style="info" %}
Package and license availability can differ per account.
{% endhint %}

### Frequently asked questions

<details>

<summary>Where do I check whether the license is active?</summary>

Check the **License Manager** in the BackOffice.

</details>

<details>

<summary>Do I also need Microsoft access?</summary>

Yes.

You need Power BI access on the Microsoft side.

</details>

<details>

<summary>What if the settings are missing?</summary>

First check the license status and your permissions.

</details>

### Related topics

* [**PowerBI**](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/powerbi.md)
* [**OutSmart packages**](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/marketplace/outsmart-packages.md)
* [**Power-Ups**](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups.md)


---

# 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://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/powerbi/understand-power-bi-license-requirements.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.
