> 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/changelog/changelog/2025/agosto-2025.md). # August 2025 Power Monitor new features and improvements in August 2025. In August, the *Settings › Organization* screen arrived, with the company data and the automatic installation that connects Power Monitor to Power BI in just a few clicks. The menus and settings screens also became translated. ## August 20, 2025 ### Improvements * **Translated Settings tabs**: the **Organization** and **Users** tabs of the *Settings* screen and the user menu items now follow the language chosen in the language selector (Portuguese, English, or Spanish). Previously, part of these texts always appeared in Portuguese. [See the documentation](/en/power-monitor/interface-e-navegacao.md#language) ## August 19, 2025 ### Improvements * **Automatic installation also configures Power BI**: in addition to creating the app registration, the installation now creates a security group in Microsoft Entra ID and adds the Power Monitor Service Principal to it. The **Install** button in the **Self Install - Power BI** section now automatically adjusts the Power BI/Fabric tenant settings that Power Monitor needs. Among them are the settings that allow the Service Principal to use the admin APIs (read and write), receive detailed metadata and expressions from semantic models, and access the global and permissions APIs. To do this, the portal asks for consent from a Power BI administrator during installation. This way, you do not need to go into the admin portal to enable each option manually, and configuration errors become less likely. [See the documentation](/en/readme/como-instalar-o-power-monitor/instalacao-automatica.md) * **More complete, translated organization screen**: the *Settings › Organization* tab now shows the organization's actual **Total users**, and all the texts on the screen (**Organization Details**, **Additional Information**, the **Configured**/**Not configured** status, and the installation confirmation window) follow the chosen language. The **Settings** option in the user menu now opens the **Organization** tab directly. [See the documentation](/en/power-monitor/configuracoes/organizacao.md) ## August 12, 2025 ### New features * **Organization settings and automatic installation (Self Install)**: the *Settings* screen gained the **Organization** tab, next to **Users**. The **Organization Details** card shows **Organization Name**, **CNPJ** (Brazilian company tax ID), and **Legal Organization Name**, and the **Additional Information** card shows the organization's **Creation Date**. On the same screen, the **Self Install - Power BI** section shows whether the Power BI integration is already configured. The **Install** button opens a confirmation window that lists what will be done (**Access permissions to Power BI workspaces** and **Security and policy configuration**). After you sign in with a Microsoft administrator account, Power Monitor automatically creates in your tenant the app registration and the Service Principal used to read the environment, and shows the progress in **Configuring resources, please wait...**. With this, you no longer need to do the manual configuration in the Azure portal. [See the documentation](/en/readme/como-instalar-o-power-monitor/instalacao-automatica.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/changelog/changelog/2025/agosto-2025.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.