> 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/capacidades.md).
# Capacities
Follow and trigger the collection of the inventory of the tenant's Fabric, Power BI Premium and Embedded capacities.
The **Capacities** collection brings the inventory of the tenant's capacities into Power Monitor (Fabric F, Power BI Premium, Embedded and Premium Per User): name, SKU, region, state, administrators and access right. It is the basis of the capacity screens in Governance, Monitoring and Dashboards and of the pause, resume and change size (SKU) automations.
**How to access:** *Mapping › Inventory › Capacities* (page title: **Capacity Dashboard**). The same screen also appears in the *Capacities* domain, under the **Capacity Scan** item. Only **Administrators** can access the screen and see the action buttons.
In the capacity list at *Governance › Infrastructure › Capacities*, administrators have the **View/manage collection →** button, which leads straight to this screen. Collection is controlled only here: the capacity list has no collection button of its own.
Capacities
## What it is for
* Confirm whether the capacity inventory is up to date and whether the last collection finished well.
* Force synchronization after creating, deleting or changing the SKU of a capacity in Azure.
* See, per run, which capacities were created, updated or removed.
{% hint style="info" %}
This screen deals with the capacity **inventory**. The **consumption** of Capacity Units (CU) is collected by another routine, every 5 minutes, for capacities with monitoring enabled. See [Enable Capacity Monitoring](/en/power-monitor/monitoramento/capacidades/ativar-monitoramento-de-capacidade.md).
{% endhint %}
## Features
The screen has five features: the **Start Scan** button, the **Active Scans** button, the totals cards, the **Scan History** table and the **View changes** modal.
### Start Scan (manual collection)
**What it is:** a button that immediately triggers a collection of the capacity inventory, without waiting for the automatic daily run.
**What it is for:** reflect in Power Monitor, without waiting for the next day, a capacity you have just created, deleted, renamed or changed the SKU of in Azure.
Screen action buttons
**How to use:**
{% stepper %}
{% step %}
### Open the screen
Go to *Mapping › Inventory › Capacities* with an **Administrator** user.
{% endstep %}
{% step %}
### Trigger the scan
Click **Start Scan**. There is no confirmation modal: the request is sent immediately, the button shows **Starting scan...** while sending, and the message **Capacity scan started successfully.** confirms the request.
{% endstep %}
{% step %}
### Follow the run
Click **Active Scans** to see the progress, or wait for the new row in the **Scan History** to go from **Running** to **Completed**. The screen reloads the data while there is an active scan.
{% endstep %}
{% step %}
### Check the result
See the updated cards and the badges in the **Changes** column; for the details, click **View changes**.
{% endstep %}
{% endstepper %}
**How it works / rules:**
* The action buttons appear only for **Administrators**.
* Manual triggering works even with the automatic run turned off in *Settings › Monitoring › Scans and Collections*.
* There is only one capacity run at a time per organization. If one is already in progress, no new row appears until it finishes.
* If the request fails, the message **Failed to start capacity scan.** appears.
### Active Scans (real-time tracking)
**What it is:** a button that opens the **Scan Tracking** modal. The number on the button's red badge indicates how many scans are running, and the thin bar below it shows the average progress.
**What it is for:** follow, without leaving the screen, the scan you have just triggered: status, how long ago it started, current step and progress bar.
Scan Tracking modal
**How to use:**
1. Click **Active Scans**.
2. Check each listed scan: type, status, time since start (**Started ...**), current step and percentage. When the total number of items is not yet known, the bar is full and animated, without a number.
3. Click **Close**.
**How it works / rules:**
* The modal shows the capacity scans **triggered by you in this browser session**. Automatic runs and scans triggered by other administrators do not appear there; follow them through the **Scan History** or in [Scan Logs](/en/power-monitor/mapeamento/logs-de-scans-e-re-execucoes.md).
* With no scans in progress, the modal shows **No active scans at the moment**.
### Totals cards
**What it is:** four cards with the count of the capacities currently inventoried (excluding deleted ones).
**What it is for:** get a quick view of the capacity estate and notice, for example, suspended or paused capacities that should be active.
Inventory totals cards
| Card | Meaning |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| **Total Capacities** | All inventoried capacities |
| **Active Capacities** | Capacities in the active state |
| **Paused** | Capacities in the "not activated" state reported by Microsoft |
| **Suspended** | Suspended capacities. **A Fabric capacity paused in Azure is reported by Microsoft as suspended and is counted in this card.** |
**How to use:** the cards are informational only (they are not clickable). To see the list of capacities behind the numbers, use [Governance › Infrastructure › Capacities](/en/power-monitor/governanca/infraestrutura/capacidades.md).
**How it works / rules:** the sum of the last three cards may be lower than the total, because capacities in transitional states (provisioning, changing SKU, unknown etc.) are only counted in the total. The numbers reflect the current inventory, that is, the result of the last completed scan.
### Scan History
**What it is:** a table with the capacity scan runs, from most recent to oldest, paginated 10 at a time.
**What it is for:** confirm whether the daily collection ran, how long it took, how many capacities Microsoft returned and whether there was a failure.
Scan History
| Column | Content |
| ----------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| **Trigger** | **Scheduled** or **Manual** (for manual runs, hover over the person icon to see who triggered it) |
| **Started** / **Finished** / **Duration** | Run times and duration |
| **Status** | **Pending** (gray), **Running** (blue, with an animated progress bar), **Completed** (green), **Failed** (red) |
| **Capacities** | Number of capacities returned by Microsoft |
| **Changes** | **Created: n** (green), **Updated: n** (blue) and **Removed: n** (red) badges |
**How to use:**
1. Locate the run by the **Started** column.
2. If the status is **Failed**, hover over the ⓘ icon next to the badge to read the error message (see [Common errors and how to resolve them](#common-errors-and-how-to-resolve-them)).
3. Use **Previous**, **Next** or the page numbers below the table to navigate through older runs, and **Items per page** to show more rows at once.
**How it works / rules:** with no run recorded, the table shows **No scan recorded yet**.
### View changes (run changes modal)
**What it is:** a link next to the status of each finished run that opens the **Scan changes from {date}** modal, with the **Created**, **Updated** and **Removed** sections.
**What it is for:** find out exactly **which** capacities came in, changed or left in a run, for example to confirm that the SKU change made in Azure was picked up.
Changes detected in a run
**How to use:**
1. In the **Scan History**, locate the run and click **View changes**.
2. Check the **Created**, **Updated** and **Removed** sections, with the name and identifier of each capacity.
3. Click **Close**.
**How it works / rules:**
* The link does not appear on **Running** runs (there is no final count yet).
* Each section lists up to 200 capacities; the rest appears as **and n more not listed**.
* **No changes detected in this run.** indicates that the inventory was already up to date; **No detail available for this run.** appears when the run did not store the details.
* **Created:** a capacity that did not yet exist in Power Monitor. **Updated:** a change in name, SKU, state, region, access right or list of administrators. **Removed:** a capacity that no longer came in the listing.
## Rules and behavior
* **Where the data comes from:** Power BI Admin API (list of the tenant's capacities), authenticated with the organization's Service Principal.
* **Automatic frequency:** by default, once a day, at **00:00** (Brasília time, UTC-3). Under *Settings › Monitoring › Scans and Collections*, the **Capacity Inventory** card lets you turn off automatic collection and choose the **Frequency**: **Daily**, **Weekly** or **Monthly**. With weekly and monthly, the run happens on a day distributed per organization, and the card shows **Next expected run** and **Last run**. The **Start Scan** button is not affected: it works with automatic collection turned off and at any frequency.
* **Protection against loss of access:** capacities are only marked as removed when the listing comes back complete and with at least one item. An empty response (for example, due to loss of permission) never erases the inventory.
* **Location in Azure:** at each scan, Power Monitor tries to automatically discover the subscription and resource group of each capacity (when the Service Principal has read access in Azure). This enables pause/resume without manual configuration; without this access, the step is skipped without error.
* **Overage:** at the end of each scan, Power Monitor reads through the Fabric API the overage configuration of each **F** capacity with provisioned CUs (excluding F0, trial, PPU, A, EM and P): state, limit in CU-hours and check date. The result appears, for reference only, in the [Overage](/en/power-monitor/governanca/infraestrutura/capacidades.md#overage) section of the capacity details. A capacity without access shows the permission message; a read failure keeps the last value read and never brings the scan down; if Fabric throttles the calls, the read stops for that round and continues in the next scan.
* **Premium Per User (PPU):** it is inventoried and counted normally, but does not take part in the automations and Azure costs.
* **Retries and timeout:** each run has a 30-minute timeout and is retried up to 3 times in case of failure. There is only one capacity run at a time per organization.
### Required permissions
* Tenant setting **Service principals can access read-only admin APIs**, enabled for a security group that contains the Service Principal.
* Optional: Service Principal as **capacity administrator** (in the Fabric admin portal), to read the overage configuration of F capacities.
* Optional: read role (Reader) for the Service Principal on the capacities' subscriptions/resource groups, for the automatic discovery of the location in Azure. To pause, resume and change size (SKU), see [Configuring permissions in Azure](/en/readme/como-instalar-o-power-monitor/configuracao-de-permissoes-no-azure-para-o-power-monitor.md).
## Common errors and how to resolve them
| Message / symptom | Probable cause | How to resolve |
| -------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------- |
| **403 Forbidden - Verifique permissões de admin.** (shown in Portuguese: "check admin permissions") | The Admin API refused the Service Principal | Enable **Service principals can access read-only admin APIs** for the Service Principal's security group and wait for propagation. |
| **Service Principal sem credenciais configuradas** (Service Principal without configured credentials) / **Failed to obtain API token** | Missing or invalid credentials, or expired secret | Review the Service Principal's App ID and secret. |
| A paused capacity appears in **Suspended** | This is how Microsoft reports a paused Fabric capacity | Expected behavior. |
| I clicked **Start Scan** and no new row appeared | A run was already in progress | Wait for the current run to finish. |
## Frequently asked questions
I changed the capacity's SKU in Azure. When does Power Monitor start considering the new SKU?
On the next run of the scan (by default daily at 00:00; see the **Frequency** configured in *Settings › Monitoring*). To apply it right away, click **Start Scan** and check the capacity under **Updated** in the **View changes** modal.
Does this screen list the capacities?
No. It shows only the totals and the collection history. The detailed list is in [Governance › Infrastructure › Capacities](/en/power-monitor/governanca/infraestrutura/capacidades.md).
## Related pages
* [Governance › Infrastructure › Capacities](/en/power-monitor/governanca/infraestrutura/capacidades.md)
* [Monitoring › Capacities](/en/power-monitor/monitoramento/capacidades.md)
* [Capacity Dashboard](/en/power-monitor/dashboards/dashboard-de-capacidade.md)
* [Capacity Cost](/en/power-monitor/mapeamento/custo-de-capacidade.md)
* [Settings › Monitoring](/en/power-monitor/configuracoes/monitoramento.md)
* [Scan Logs](/en/power-monitor/mapeamento/logs-de-scans-e-re-execucoes.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/capacidades.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.
