> 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/apps.md).

# Apps

Follow and trigger the daily collection of the Power BI Apps published in the tenant, which feeds the Apps inventory in Governance.

The Mapping **Apps** screen controls the collection of the **Power BI Apps** published in your tenant: name, description, who published it and the date of the last update. The list of Apps is in Governance; this screen shows when the collection last ran, whether it finished well and lets you trigger a new collection right away.

**How to access:** *Mapping › Inventory › Apps*. Only **Administrators** can access the screen and the **Run now** action. On the Apps screen in Governance, the other profiles see only the **Collection** status line (without the link to this screen).

<figure><picture><source srcset="/files/DKBy0ccfCqNcii9KS1qi" media="(prefers-color-scheme: dark)"><img src="https://3938213054-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH2bFRBmIfyK3kwVKbldl%2Fuploads%2Fgit-blob-ed661334d6c912883576bd4a9c02c839d5ede883%2Fpm-mapeamento-apps-en.png?alt=media" alt="Mapping Apps screen with the What is collected card and the Scans in this collection card with the last run and the Run now button"></picture><figcaption><p>Apps</p></figcaption></figure>

## What it is for

* Keep the Apps inventory used in [Governance › Reports › Apps](/en/power-monitor/governanca/relatorios/apps.md) up to date.
* See a newly published or updated App without waiting for the daily collection.
* Confirm whether the last collection finished well and, if it failed, go to the history in **Scan Logs**.

## Screen components

The screen has two cards: **What is collected** and **Scans in this collection**.

### What is collected

**What it is:** a card with the description of the collection ("Lists the Power BI Apps published in the tenant through the Admin API. Runs automatically once a day.") and, in the footer, the link **View collected data in Apps →**, which leads to the list in Governance.

### Scans in this collection

**What it is:** a table with one scan per row (here, **App**) and the columns **Scan**, **Last run**, **Status** and the action button.

<figure><picture><source srcset="/files/dw1a7A65ETQqnwppWqs3" media="(prefers-color-scheme: dark)"><img src="https://3938213054-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH2bFRBmIfyK3kwVKbldl%2Fuploads%2Fgit-blob-b8bafb0b57310399080c6d7d9b4bd7f8a5c808fd%2Fpm-mapeamento-apps-scans-en.png?alt=media" alt="Scans in this collection card with the App row, the date of the last run, the Completed status and the Run now button"></picture><figcaption><p>Scans in this collection card</p></figcaption></figure>

| Column / element | Content                                                                                                        |
| ---------------- | -------------------------------------------------------------------------------------------------------------- |
| **Scan**         | Name of the scan (**App**)                                                                                     |
| **Last run**     | Date and time of the most recent run, or a dash if it never ran                                                |
| **Status**       | **Running** (blue, with a spinning indicator), **Completed** (green), **Failed** (red) or **Never run** (gray) |
| **Run now**      | Triggers the collection right away                                                                             |

**How to use Run now:**

1. Click **Run now**. There is no confirmation modal.
2. The message **Scan queued. The status updates by itself when it finishes.** appears and the button shows **Running…** (disabled).
3. When the collection finishes, Power Monitor notifies you with **Scan completed.** or, if it failed, **The scan finished with a failure. See the details in Scan Logs.**, and the row updates by itself.
4. Check the Apps in [Governance › Reports › Apps](/en/power-monitor/governanca/relatorios/apps.md).

**Full history:** the **View full history in Scan Logs →** link, in the footer of the card, opens [Scan Logs](/en/power-monitor/mapeamento/logs-de-scans-e-re-execucoes.md) already filtered by the **App** type, with all runs, including the error message of those that failed.

### Run history

**What it is:** the **Run history** table, below the scans, with the runs of this screen's scans from the most recent to the oldest, with an items-per-page selector and pagination.

| Column                                    | Content                                                                                           |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------- |
| **Trigger**                               | **Scheduled** or **Manual** (for manual runs, hover over the person icon to see who triggered it) |
| **Scan**                                  | Which of this screen's scans ran                                                                  |
| **Started** / **Finished** / **Duration** | Run times; while the run is in progress, **Duration** shows the elapsed time live                 |
| **Status**                                | Run status                                                                                        |
| **Items processed**                       | Number of items handled by the run                                                                |
| **Error**                                 | Icon with the run's error message (hover over it)                                                 |

**What it is for:** checking the latest runs and the error of a failure without leaving the screen.

## Rules and behavior

* **Where the data comes from:** Power BI Admin API (Apps published in the tenant), with the organization's Service Principal.
* **Automatic frequency:** once a day, at **00:00** (Brasília time). In *Settings › Monitoring › Scans and Collections*, **Inventory** group, the scan appears as **App Inventory**: there you can turn it off and choose the **Frequency** (**Daily**, **Weekly** or **Monthly**). The screen shows the **Next expected run** and the **Last run**. See [Settings › Monitoring](/en/power-monitor/configuracoes/monitoramento.md).
* **Run now** works even with the automatic run turned off or with a weekly or monthly frequency, and does not change the configured frequency.
* **Prerequisite:** the tenant setting **Service principals can access read-only admin APIs**, enabled for a security group that contains the Service Principal. See the summary in [Mapping](/en/power-monitor/mapeamento.md#service-principal-permission-requirements-summary).
* **Only one run at a time:** there is never more than one Apps collection at the same time for the organization.
* **Last run:** comes from the same record shown on the Home page, not from the window of days of Scan Logs.

## Step by step

{% stepper %}
{% step %}

### Open the screen

In *Mapping › Inventory › Apps* (or through the **View/manage collection →** link on the Apps screen in Governance, if you are an Administrator).
{% endstep %}

{% step %}

### Trigger the collection

In the **App** row, click **Run now** and wait for the status to change from **Running** to **Completed**.
{% endstep %}

{% step %}

### Check the data

Click **View collected data in Apps →** and look for the App in the list.
{% endstep %}
{% endstepper %}

## Frequently asked questions

<details>

<summary>I just published an App and it does not appear in the list. What should I do?</summary>

Click **Run now**. The automatic collection runs once a day (or weekly/monthly, if you changed the **Frequency**).

</details>

<details>

<summary>The status is Failed. Where do I see the reason?</summary>

Click **View full history in Scan Logs →**. The error message of each run appears there. Also check that the tenant setting for admin APIs is enabled for the Service Principal.

</details>

<details>

<summary>Are workspace apps also collected here?</summary>

This screen only controls the collection of Power BI Apps. The list in Governance also brings together workspace apps, which have a separate source; see [Apps](/en/power-monitor/governanca/relatorios/apps.md).

</details>

## Related pages

* [Governance › Reports › Apps](/en/power-monitor/governanca/relatorios/apps.md)
* [Scan Logs](/en/power-monitor/mapeamento/logs-de-scans-e-re-execucoes.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/apps.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.