> 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/configuracoes-do-tenant.md).
# Tenant Settings
Follow, trigger and pause the daily collection of the Power BI and Fabric tenant settings, which feeds the change history and the desired state.
The **Tenant Settings** collection reads the Power BI and Microsoft Fabric tenant settings through the administration API and keeps their history: the first collection records the state of all settings and the following ones record only what changed. The data screen shows the current state, what changed and the desired state; this screen shows the collection history and lets you trigger or pause it.
**How to access:** *Mapping › Audit and compliance › Tenant Settings*. 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.
Tenant Settings
## What it is for
* Keep up to date the picture in [Governance › Tenant › Tenant Settings](/en/power-monitor/governanca/tenant/configuracoes-do-tenant.md): current state of the highest-risk settings, change history and comparison with the desired state.
* Read the settings right away, after changing one of them in the Fabric admin portal.
* Confirm that the collection is running and investigate failures, such as a missing Service Principal 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 Tenant Settings →** link, which leads to the data screen.
### Collection runs card
The **Collection runs** card (*Automatic daily collection, every day at noon Brasília time. Trigger manually if you do not want to wait.*) holds the buttons and the history.
Tenant settings 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. Since this collection makes a single read per organization, it usually finishes in a few seconds and there is rarely time to pause. |
| 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** | Run counter (the collection makes one read per organization) |
| **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 Fabric administration API (tenant settings), read by the organization's Service Principal. The collection is **read-only**: Power Monitor never changes tenant settings.
* **What is saved:** the first collection records the state of all settings; the following ones record **only the settings that changed**. A **Completed** run that found no changes does not create a new reading, which is why the **Last reading** date on the data screen is that of the last collection in which something changed.
* **Drift alert:** at the end of each collection, if the drift alert is turned on in [Settings › Monitoring](/en/power-monitor/configuracoes/monitoramento.md#scans-and-collections) (**Audit, security and compliance** section, **Tenant settings drift alert**), Power Monitor compares the state read with the desired state and opens an alert when a setting moves away from it.
* **Required permission:** the tenant setting **Service principals can access read-only admin APIs**, enabled for the security group that contains the Service Principal. Power Monitor never changes this setting; a Fabric administrator must enable it. See the step by step in [How to enable the domain collection permission](/en/power-monitor/mapeamento/dominios.md#how-to-enable-the-domain-collection-permission). Without it, the run ends as **Failed**.
* **Frequency:** daily, at **12:00** (Brasília time, UTC-3), 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 **Tenant settings** 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 › Tenant Settings* 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. The run usually finishes in a few seconds.
{% endstep %}
{% step %}
### Confirm the result
When the run shows as **Completed**, open [Governance › Tenant › Tenant Settings](/en/power-monitor/governanca/tenant/configuracoes-do-tenant.md) through the link in the **What is collected** card. If the run failed, hover over the icon in the **Error** column to read the reason.
{% endstep %}
{% endstepper %}
## Frequently asked questions
The run finished as Completed, but the data screen did not change.
This is expected when nothing changed in the tenant: the collection only saves a new reading when some setting differs from the previous one.
The run failed with a message saying the admin tenant settings read failed.
Fabric refused the read (the message is shown in Portuguese). Enable the tenant setting for the Service Principal's group, wait a few minutes for propagation and click **Run now** again.
Does Power Monitor change any setting in my tenant?
No. The collection is read-only.
## Related pages
* [Governance › Tenant › Tenant Settings](/en/power-monitor/governanca/tenant/configuracoes-do-tenant.md)
* [Settings › Monitoring](/en/power-monitor/configuracoes/monitoramento.md)
* [Additional Permissions](/en/power-monitor/configuracoes/permissoes-adicionais.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/configuracoes-do-tenant.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.
