> For the complete documentation index, see [llms.txt](https://docs.powermonitor.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.powermonitor.com.br/en/power-monitor/mapeamento/licencas-power-bi.md).
# Power BI Licenses
Follow, trigger and pause the daily collection of Power BI licenses (Free, Pro and Premium Per User) read from Microsoft Graph and crossed with usage.
The **Power BI Licenses** collection reads, through **Microsoft Graph**, the tenant's Power BI license subscriptions (Free, Pro and Premium Per User) and each account's license, and crosses that data with the usage recorded in the activity log. The cards, the list of users and the savings opportunities are in Governance; this screen shows the collection history and lets you trigger or pause it.
**How to access:** *Mapping › Audit and compliance › Power BI Licenses*. Only **Administrators** can access the screen and the actions. On the data screen, all profiles see the **Collection** line with the date of the last run; the **View/manage collection →** link, which leads here, appears only for administrators.
Power BI Licenses
## What it is for
* Keep up to date the picture in [Governance › Tenant › Power BI Licenses](/en/power-monitor/governanca/tenant/licencas-power-bi.md): who has each license, where it comes from, how much it was used and which ones can be released.
* Refresh the numbers right away, for example just after removing licenses in the Microsoft 365 admin center.
* Confirm that the collection is running and investigate failures, such as a missing Microsoft Graph permission.
## Screen components
The screen has a header (*Mapping* and the collection subtitle) and two cards.
### What is collected card
Describes the source and the cadence (*Source, cadence and where the data shows up*) and has, at the bottom, the **View collected data in Power BI Licenses →** link, which leads to the data screen.
### Collection runs card
The **Collection runs** card (*Daily collection of licenses from Microsoft Graph*) holds the buttons and the history.
License collection runs
| Element | What it is for |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Run now** / **Resume** | Triggers a manual collection. When there is a **Paused** run, the button is renamed **Resume**. It works even with the automatic collection turned off. |
| **Pause** | Appears only during a run in progress. The pause is cooperative: the notice **Pause requested: the run stops after the next processed item** appears. |
| State badges | **Run in progress (n)** (with a progress bar), **Run paused** and, if automatic tracking ends, **Automatic refresh stopped. Reload the page to see the current status.** |
| Runs table | History from the most recent to the oldest, with an items-per-page selector and pagination. |
| **View failures** | Link in the **Failures** column that opens the **Failures for the {date} run** modal, with **Item**, **Reason** and **Detail**. |
Table columns:
| Column | Content |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------- |
| **Trigger** | **Scheduled** or **Manual** (for manual runs, hover over the person icon to see who triggered it) |
| **Started** / **Finished** / **Duration** | Run times (no end and duration while it is active) |
| **Status** | **Running**, **Paused**, **Completed**, **Failed** or **Stuck** |
| **Items processed** | Number of users with a Power BI license saved in the collection |
| **Failures** | Failure counter; **View failures** link when there is detail |
| **Error** | Icon with the run's general error message (hover over it) |
## Rules and behavior
* **Where the data comes from:** Microsoft Graph (license subscriptions and the licenses assigned to each user), crossed with the Power BI and Fabric activity log already collected by Power Monitor (see [Audit](/en/power-monitor/mapeamento/auditorias.md)). Only subscriptions that include some Power BI plan are included; capacities (Fabric F, Embedded A and Premium P) are not per-user licenses and are left out.
* **Required permission:** the Microsoft Graph application permissions `LicenseAssignment.Read.All` and `User.Read.All` (or `Directory.Read.All`, which also covers the read) for the Service Principal. They only read; they never change assignments. Organizations created by the automatic installation usually already have the permission. To grant it, see [Additional Permissions › Power BI licenses](/en/power-monitor/configuracoes/permissoes-adicionais.md#power-bi-licenses). Without permission, the run ends as **Failed** with a message asking for that grant.
* **Snapshot replaced on every collection:** each completed collection replaces the previous one entirely and records a daily point for the evolution chart. If a collection fails, the data screen keeps showing the last successful collection.
* **Frequency:** daily, at **09:45** (Brasília time, UTC-3), after the morning activity log ingestion, for organizations with a Service Principal configured. In [Settings › Monitoring](/en/power-monitor/configuracoes/monitoramento.md#scans-and-collections), **Scans and Collections** section, **Others** group, the **Power BI licenses** switch turns the automatic collection on or off (it is on by default) and the **Frequency** selector allows **Daily**, **Weekly** or **Monthly**. With the weekly and monthly options, the run happens on a day distributed per organization, and the item shows **Next expected run** and **Last run**. **Run now** is never affected: it works with the switch turned off and at any frequency.
* **Stuck:** a run with no progress for **10 minutes** is closed as **Stuck**.
* **Concurrency:** there is only one active run (in progress or paused) per organization. When you try to trigger another one, *A run is already in progress for this organization.* appears.
* **Screen refresh:** while there is an active run, the table refreshes by itself every 20 seconds, for up to 30 minutes.
## Step by step
{% stepper %}
{% step %}
### Open the collection screen
Go to *Mapping › Audit and compliance › Power BI Licenses* with an administrator account.
{% endstep %}
{% step %}
### Trigger the collection
In the **Collection runs** card, click **Run now**. There is no confirmation; the button shows **Running…** and the message *Run queued. The history updates when it starts.* appears. While the collection service has not picked up the run, the button shows **Queued** and the card says *Run queued, waiting to start…*; then the button changes to **In progress** and the bar shows the processed items (for example, *12 of 40*) and the estimated time left (*\~3 min left*). The screen tracks the run until it finishes, without reloading.
{% endstep %}
{% step %}
### Follow it
Watch the **Run in progress** badge and the new row in the history. If you need to stop it, click **Pause**; later use **Resume** to continue.
{% endstep %}
{% step %}
### Confirm the result
When the run shows as **Completed**, open [Governance › Tenant › Power BI Licenses](/en/power-monitor/governanca/tenant/licencas-power-bi.md) through the link in the **What is collected** card and reload. If the run failed, hover over the icon in the **Error** column to read the reason.
{% endstep %}
{% endstepper %}
## Frequently asked questions
The data screen shows "No collection has finished yet".
The first collection has not finished yet. Check the history here: if there is no run, click **Run now**; if there is one with **Failed**, read the message in the **Error** column.
The run failed with a message asking for LicenseAssignment.Read.All and User.Read.All.
Microsoft Graph refused the read. Grant the permissions in [Additional Permissions › Power BI licenses](/en/power-monitor/configuracoes/permissoes-adicionais.md#power-bi-licenses) and click **Run now** again.
I removed licenses and the numbers did not change.
The collection is daily. Click **Run now** and, with the run **Completed**, reload the data screen.
## Related pages
* [Governance › Tenant › Power BI Licenses](/en/power-monitor/governanca/tenant/licencas-power-bi.md)
* [Additional Permissions › Power BI licenses](/en/power-monitor/configuracoes/permissoes-adicionais.md#power-bi-licenses)
* [Audit](/en/power-monitor/mapeamento/auditorias.md)
* [Settings › Monitoring](/en/power-monitor/configuracoes/monitoramento.md)
* [Mapping](/en/power-monitor/mapeamento.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://docs.powermonitor.com.br/en/power-monitor/mapeamento/licencas-power-bi.md?ask=&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.
