> 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/readme/primeiro-acesso.md).

# First access

What to check and configure right after installing Power Monitor to start monitoring your Microsoft Fabric and Power BI environment.

After completing the installation, you enter Power Monitor through the [Home](/en/power-monitor/pagina-inicial.md) page. This page gathers the recommended settings for the first days, in the order in which they make the most difference.

{% hint style="info" %}
Most of the settings below are in **Settings** and are exclusive to **Administrators**. The person who installed Power Monitor is already an administrator of the organization.
{% endhint %}

Always access it at [app.powermonitor.com.br](https://app.powermonitor.com.br/), signing in with your Microsoft account from the monitored tenant.

***

## First-days checklist

{% stepper %}
{% step %}

### Check whether the first scans have finished

The first scans (inventory, capacities, gateways, connections, and apps) start at the end of the installation and take from minutes to a few hours, depending on the size of the tenant. Track them in **Mapping › Scan Logs** (administrators). Afterwards, the inventory scans repeat **automatically every day**.

As soon as the first full inventory finishes, the monitoring routines (semantic model refreshes, gateway status, job runs and Fabric schedules) start running, including the first collection of Fabric schedules and job runs. Right after the installation, collections also wait up to 15 minutes for Microsoft to accept the new Service Principal secret, instead of failing.

Check the result on the **Dashboard** (monitored inventory card) and on the **Governance** screens (Workspaces, Reports, Semantic Models, etc.).

If the inventory is empty or incomplete, the most common causes are **Fabric tenant settings** not enabled for the Power Monitor application or workspaces outside monitoring. See [Prerequisites](/en/technical-documentation/instalacao/pre-requisitos.md).
{% endstep %}

{% step %}

### Review which workspaces are monitored

Only items from **monitored** workspaces appear on the screens, generate alerts, and are included in billing. Review the selection made during installation in *Governance ›* [*Workspaces*](/en/power-monitor/governanca/workspaces.md) and add or remove workspaces as needed. Remember that the number of monitored items determines the billing tier (see [Billing](/en/power-monitor/faturamento.md#how-billing-works)).
{% endstep %}

{% step %}

### Grant the pending additional permissions

In **Settings › Additional Permissions**, check the **Basic Fabric permissions** and grant whatever is still pending: gateways and connections, Entra ID read access (secret expiration and user import), the Microsoft Teams bot, and the Azure permissions for capacities and costs. Each card shows the status and the role required of the person who will grant it.

The fastest way is the **Grant all needed permissions** button at the top of the page: click **Run all** and complete the Microsoft consent windows. Then, use **Add Service Principal** on the **Add Service Principal to Workspaces** card. Full step-by-step in [Additional Permissions › How to use](/en/power-monitor/configuracoes/permissoes-adicionais.md#how-to-use).
{% endstep %}

{% step %}

### Enable monitoring

In **Settings › Monitoring**, confirm:

* **Capacity Metrics Source:** the workspace and the semantic model of the **Fabric Capacity Metrics** app, where capacity consumption (Capacity Units) comes from. See [Enable Capacity Monitoring](/en/power-monitor/monitoramento/capacidades/ativar-monitoramento-de-capacidade.md).
* **Gateway Monitoring:** periodic check of the status of the gateways on which the Power Monitor application is an administrator. See [Enable Gateway Monitoring](/en/power-monitor/monitoramento/gateways/ativar-monitoramento-de-gateways.md).
* **Semantic model monitoring:** detection of refresh failures of models on capacity.

For each item, see the step-by-step in [Settings › Monitoring › How to use](/en/power-monitor/configuracoes/monitoramento.md#features).

In **Settings › Audit**, enable **automatic activity log collection** to feed the **Audit** screens (tenant events and report views) and the **Report Access Dashboard**. Collection runs three times a day. To turn it on: enable **Enable automatic activity log collection** and click **Save Configuration** (see [Audit › How to use](/en/power-monitor/configuracoes/auditoria.md#how-to-use)).
{% endstep %}

{% step %}

### Configure alerts and notification channels

* In **Settings › Notifications**, choose which alert types each recipient receives (gateway offline, semantic model refresh failure, Fabric item failure, capacity usage limit, consumption anomalies, daily and hourly checklists, among others) and use **Test** to validate.
* In **Settings › Alerts**, configure the channels: email (including with an SMTP account from your company, if you want), **Microsoft Teams**, **Slack**, and **Telegram**.

Step-by-step: [Notifications › How to use](/en/power-monitor/configuracoes/notificacoes.md#features) and [Alerts (channels) › How to use](/en/power-monitor/configuracoes/alertas.md#how-to-use). To follow the generated alerts, see [Monitoring › Alerts](/en/power-monitor/monitoramento/alertas.md).
{% endstep %}

{% step %}

### Invite your team

In [Users](/en/power-monitor/usuarios.md), register the people who will use Power Monitor (individually, through **Import from Entra ID**, which also accepts groups, or through a CSV file), define who is an **Administrator**, apply **profiles**, and, if necessary, restrict each user to **certain workspaces** or block specific pages. Only registered people can enter Power Monitor: a tenant account without registration sees the message "User not found". Step-by-step in [Users › How to use](/en/power-monitor/usuarios.md#features).

Users from outside your tenant must first be invited as guests (B2B) in your Entra ID. See [How do I monitor more than one tenant?](/en/perguntas-frequentes/duvidas-gerais/como-monitorar-mais-de-um-tenant.md)
{% endstep %}

{% step %}

### Explore the dashboards

With the data collected, explore the [Dashboards](/en/power-monitor/dashboards.md): the main **Dashboard**, the Governance, Capacity, Efficiency, and Permissions dashboards, and the **Monitoring Dashboard**, designed to stay open on a team TV.
{% endstep %}
{% endstepper %}

***

## How to use

### How to sign in to Power Monitor

1. Open [app.powermonitor.com.br](https://app.powermonitor.com.br/) in your browser.
2. Sign in with your Microsoft account from the monitored tenant (the same one registered in **Users**).
3. You are taken to the [Home](/en/power-monitor/pagina-inicial.md) page. If the **User not found** screen appears, the account used is not registered: click **Sign out and sign in again** and use the correct account, or ask an administrator to register it.

### How to change the interface language

1. At the top of the screen, click the language selector.
2. Choose **Português**, **English**, **Español**, **Italiano**, or **日本語**. The interface changes immediately.

### How to switch between light and dark theme

1. At the top of the screen, click the moon icon (or the sun icon, in the dark theme).
2. Alternatively, open the user menu, at the bottom of the side menu, and click **Change Theme**.

## Tips

* **Mobile:** Power Monitor works in the phone's browser and can be **installed on the home screen** of your smartphone or tablet. See [Does Power Monitor work on mobile devices?](/en/perguntas-frequentes/duvidas-gerais/funciona-em-dispositivos-moveis.md)
* **Power BI consent:** some actions ask, once per user, for authorization of your Power BI access in a Microsoft window. Allow pop-ups for Power Monitor.
* **Trial period:** a notice at the top of the screens shows how many days are left. Check the information in **Billing** before the end of the trial. See [How does the 30-day trial work?](/en/perguntas-frequentes/licenciamento/como-funciona-o-trial-de-30-dias.md)

## Related pages

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Portal Overview</strong></td><td>All areas of Power Monitor</td><td><a href="/en/power-monitor/visao-geral.md">Overview</a></td></tr><tr><td><strong>Alerts</strong></td><td>Alert types and channels</td><td><a href="/en/power-monitor/monitoramento/alertas.md">Alerts</a></td></tr><tr><td><strong>Capacities</strong></td><td>Capacity consumption in Capacity Units</td><td><a href="/en/power-monitor/monitoramento/capacidades.md">Capacities</a></td></tr><tr><td><strong>Gateways</strong></td><td>Data gateway status</td><td><a href="/en/power-monitor/monitoramento/gateways.md">Gateways</a></td></tr><tr><td><strong>Frequently asked questions</strong></td><td>Questions and answers</td><td><a href="/en/perguntas-frequentes.md">Frequently asked questions</a></td></tr><tr><td><strong>Chat on WhatsApp</strong></td><td>Need help?</td><td><a href="https://powermonitor.com.br/whatsapp">https://powermonitor.com.br/whatsapp</a></td></tr></tbody></table>


---

# 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/readme/primeiro-acesso.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.