> 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/technical-documentation/instalacao/passo-a-passo.md). # Step-by-step installation Technical summary of what happens at each step of the Power Monitor installation. This page summarizes, from a technical point of view, what happens at each step of the installation wizard. The guide with screenshots is in [How do I install Power Monitor?](/en/readme/como-instalar-o-power-monitor.md) ## Steps | # | Step | What happens | | -- | ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | 1 | **Sign-in** | The user signs in with the tenant's Microsoft account (OpenID Connect). Without an organization, the wizard opens automatically | | 2 | **Region and language** | Sets the wizard language and, in Brazil, the country and currency (BRL) | | 3 | **Organization** | Creates the organization in the **Incomplete** state, with the registration data and the notification **time zone** (default set by the country). The user who installs becomes the first **Administrator** | | 4 | **Billing** | Stores the tax and billing information and the **consent to automatic billing** at the end of the trial, with date/time and text version | | 5 | **Installation Type** | Automatic or manual | | 6a | **Permissions** (automatic) | Delegated admin consents for Microsoft Graph and the Power BI Service | | 7a | **Automatic** | Creates the App Registration, the Service Principal, the client secret, and the security group; adds the application to the group; applies the Fabric tenant settings; stores the encrypted credentials; revokes the temporary permissions | | 6b | **Credentials** (manual) | Tests the Client ID and Client Secret in Entra ID and stores the encrypted credentials | | 8 | **Terms of Acceptance** | Acceptance of the Terms of Use, which **activates the organization** (status **Active**) and starts the 30-day trial | | 9 | **Additional Permissions** (automatic, optional) | Optional grants: gateways, Graph, Teams, Azure | | 10 | **Metrics Source** (automatic, optional) | Choice of the Fabric Capacity Metrics model, Administrator access to its workspace, and activation of consumption monitoring for all capacities | | 11 | **Workspaces** | Defines the monitored workspace selection, grants the application Administrator access to the chosen workspaces, and schedules the initial and daily scans | | 12 | **Done** | **Preparing the environment** screen, with the real progress of each initial scan, and access to the portal | {% hint style="info" %} * The **Automatic** step separates the required tenant settings from the optional ones. If the required ones cannot be applied (for example, the account is not a Fabric administrator), the installation is completed **with a pending item**: the credentials are stored, but collection only works after a Fabric administrator enables the settings. * An organization in the **Incomplete** state with no activity for more than 24 hours is removed automatically. Before the terms are accepted, leaving the wizard with **Cancel Installation** removes the data entered. {% endhint %} ## First scans When the workspace selection is completed, the scans of capacities, full inventory, gateways, connections, apps, and model × connection relationships are queued, and they then repeat **daily**. The time of the first scan depends on the number of workspaces and items in the tenant. See [Scan Flow](/en/technical-documentation/documentacao-tecnica/fluxo-de-scans.md). * **No wait between scans:** the installation scans do not wait for the 5-minute cycle of the collection service. Capacities, full inventory, apps and gateways start right away and run in parallel; connections wait for the gateway scan, and model × connection relationships wait for the inventory and the connections. Each dependent scan starts as soon as its prerequisite finishes. * **Real progress:** the preparation screen lists the **Initial scans** with the phase of each one (**Queued**, **Running** or **Retrying**), the processed items and the summary *4 of 6 finished*. The overall bar never goes backwards. * **Outcome:** when all of them finish, *All set, shall we start?* is displayed (or *Environment configured, but some scans failed.*, with the scans that failed, which run again in the daily collection). If the screen closes earlier, due to time or because tracking dropped, *Environment configured. The initial collection continues in the background.* or *Environment configured. Progress could not be tracked.* is displayed: the scans keep running and the data shows up as each one finishes. ## After installation 1. Check the inventory and the [Scan Logs](/en/power-monitor/mapeamento/logs-de-scans-e-re-execucoes.md). 2. Enable monitoring in **Settings › Monitoring** and configure alerts in **Settings › Notifications** and **Settings › Alerts**. 3. Follow [First access](/en/readme/primeiro-acesso.md). ## Problems with the installation? * Check the [Prerequisites](/en/technical-documentation/instalacao/pre-requisitos.md). * Open a ticket in **Support**, inside Power Monitor, or [talk to our team on WhatsApp](https://powermonitor.com.br/whatsapp). * [Schedule an assisted installation](https://powermonitor.com.br/instalacao). --- # 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/technical-documentation/instalacao/passo-a-passo.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.