> 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/2026/junho-2026.md). # June 2026 Power Monitor new features and improvements in June 2026. June was marked by a major release at the end of the month: it brought the **Billing** screen with invoices, tax invoices and fiscal data, the new **Capacity Dashboard**, monitoring of **Fabric Items** (pipelines, Copy Jobs and notebooks), the **Audit** screens for Power BI events and per-user **Notifications** settings. It also brought a redesigned Governance Dashboard, the semantic model details window and the mapping of new Fabric artifact types. ## June 30, 2026 ### Improvements * **Same artifact count on every screen**: the total number of workspaces and artifacts is now calculated using the same rule on the **Dashboard**, the **Governance Dashboard** and **Billing**. Previously, each screen could show a slightly different number. Now they all consider the same Power BI and Fabric artifact types and count only the organization's shared workspaces. Personal workspaces (*My workspace*) and admin workspaces are left out. You can compare the numbers across screens without having to reconcile differences, and the quantity used for billing is the same one shown on the dashboards. [See the documentation](/en/power-monitor/dashboards/dashboard-de-governanca.md) ## June 29, 2026 ### New features * **Trial period notice**: organizations on a free trial now see a notice at the top of the pages with the end date and how many days are left (for example, *"expires today"* or *"in 5 days"*). The notice includes a direct link to the **Fiscal Data** tab in Billing, so you can review your billing information if you want to continue after the trial, and a link to request cancellation before the end of the period and avoid the automatic charge. This way no one is caught by surprise when the trial ends. [See the documentation](/en/power-monitor/faturamento.md) * **New Governance › Development page**: the *Governance* menu gained the **Development** page, which brings together the development-support artifacts published in the tenant: **Variable Libraries** and **App Backends**. The **All**, **Variable Library** and **App Backend** tabs switch between the types, and the table shows **Type**, **Name**, **Workspace**, **Created by**, **Modified by**, **Created on** and **Modified on**, with filters by item name, workspace (name or ID) and authors. With it you can inventory these items, which previously did not appear on any screen. [See the documentation](/en/power-monitor/governanca/dados-e-engenharia/desenvolvimento.md) ### Improvements * **More Fabric artifact types mapped**: the inventory scan now identifies new Microsoft Fabric item types. In *Governance › Data Science*, in addition to ML Models, **Data Agents**, **ML Experiments**, **Ontologies** and **Graph Models** now appear. The **All**, **ML Model**, **Data Agent**, **ML Experiment**, **Ontology** and **Graph Model** tabs show each type with workspace, authors and dates. In *Governance › Data Engineering*, the **Data Build Tool Job** card (dbt jobs) was added. The **Dashboard** now displays the totals for these types and for other Fabric items that were not counted before, such as Reflex, KQL Querysets, Eventhouses, Event subscriptions, Explorations, Metric sets, Data functions, Org apps, Apache Airflow Jobs and Spark Job Definitions. The tenant inventory becomes more complete and closer to what actually exists in Fabric. [See the documentation](/en/power-monitor/governanca/dados-e-engenharia/ciencia-de-dados.md) * **Free trial emails revised**: the welcome, reminder and end-of-trial emails have new wording that clearly explains that the subscription is activated automatically at the end of the period. Each message states the exact end date and what to do to continue or to cancel. [See the documentation](/en/perguntas-frequentes/licenciamento/como-funciona-o-trial-de-30-dias.md) ## June 28, 2026 ### New features * **Billing**: the new *Settings › Billing* screen (administrators only) brings together everything related to Power Monitor billing. It has two tabs: * **Invoices**: the **Monitored artifacts** card shows the price tiers, the tier the organization is in (*"You are here"*) and the item limit included in each tier. The plan is set automatically by the number of monitored items; there is nothing to choose. Next to it are the **Current invoice** card, with the monthly amount and the billing tier, and the **Past invoices** list, with **Name**, **Amount**, **Monitored items**, **Due date** and **Status** (**Paid**, **Pending**, **Overdue**, **Awaiting payment**, **Canceled**). For each invoice, **View link** opens the boleto (Brazilian bank payment slip) or Pix (Brazilian instant payment), **View NF** downloads the tax invoice (Nota Fiscal) and **View details** shows the issue date and the installments. * **Fiscal Data**: a form with CNPJ (Brazilian company tax ID) or CPF (Brazilian individual taxpayer ID), legal name, billing email, full address (ZIP code, state, street, number, neighborhood, city and **City IBGE Code**), **Fiscal Classification** (**Opted for Simples Nacional (Brazilian simplified tax regime)**, **Individual Microentrepreneur (MEI)** or **Individual (CPF)**), **Preferred Due Date** (day 1 to 28), payment of the setup fee in up to 3 installments with the installments' due day, and **Additional Billing Notes**. When you type a CNPJ, the company data is filled in automatically based on the Receita Federal (Brazilian Federal Revenue Service) records. [See the documentation](/en/power-monitor/faturamento.md) * **Automatic billing and free trial emails**: Power Monitor now handles the billing cycle on its own. Each organization automatically starts a 14-day free trial and receives follow-up emails: a welcome email at the start, reminders 7 days and 1 day before the end, and a notice on the day the trial ends. Once the trial is over, the monthly invoice is generated on the 1st of every month, for the previous month and calculated by the tier of monitored items. In the first month after the trial, the amount is prorated to the days actually used. The setup fee installments are charged on invoices separate from the monthly fee. Everything is available in the **Invoices** tab, with boleto, Pix and tax invoice. [See the documentation](/en/power-monitor/faturamento.md) * **Capacity Dashboard**: new **Capacity Dashboard** item in the side menu, with an executive view of the consumption and health of Microsoft Fabric capacities. The page brings together: * cards with **Total consumption (CU s)**, **Success rate**, **Capacities** at risk and **Failed refreshes** in the last 24h, compared with the previous period; * the **Capacity usage** chart, which separates Background and Interactive and lets you switch the **Granularity** between **Timepoint** (last 24h), **Hour** (7 days) and **Day** (30 days). A reference line shows the 100% limit according to the capacity SKU (F and FTL SKUs); * **Executive alerts**, the **Top Workspaces**, **Top Items**, **Top Users** and **Top Operations** rankings, the **Consumption by item kind (today)** card, with the change compared with yesterday and the 30-day average, and the **Weekly consumption heatmap**, which shows on which days and at which times the capacity is under the most pressure. With this you can identify bottlenecks, peak times and the biggest consumers without leaving the portal. [See the documentation](/en/power-monitor/dashboards/dashboard-de-capacidade.md) * **Fabric Items monitoring**: the new *Monitoring › Fabric Items* page (titled **Fabric Jobs Monitoring**) tracks the health of **Data Pipelines**, **Copy Jobs** and **Notebooks** runs. The summary cards show **Total**, **Healthy**, **Degraded**, **Failed** and **Open incidents**, and the table lists each item with **Type**, **State**, **Last check**, **Incident** and **Last incident duration**. There are filter buttons by state and a search by name. To enable it, go to *Settings › Monitoring* and turn on **Automatic monitoring** in the **Fabric Jobs (DataPipeline / CopyJob / Notebook)** card. From then on, the job status is checked every 2 hours. If no items have been scanned yet, the card itself offers the **Perform initial scan** button. [See the documentation](/en/power-monitor/monitoramento/itens-do-microsoft-fabric.md) * **Per-user Notifications settings**: the new *Settings › Notifications* tab defines who receives each email alert. The alerts are organized into three groups: **Infrastructure** (**Gateway Offline** and **Capacity Offline**), **Capacity** (**Capacity Usage Limit** and **Capacity Background Usage**) and **Refreshes** (**Dataset Refresh Failed** and the new **Fabric Item Failed**, sent when a Data Pipeline, Copy Job or Notebook fails). Each card has a master switch, which turns the alert on or off for everyone, and, when expanded, lists the administrators with an individual switch. The header summarizes how many alerts are configured, how many are active and how many recipients there are. This way each administrator receives only the emails that matter to them. [See the documentation](/en/power-monitor/configuracoes/notificacoes.md) * **Power BI event audit**: the **Audit** menu is now displayed for administrators, with two pages: * **Events Overview** (*Audit Events*): cards with **Total Activities**, **Active Users**, **Audited Workspaces** and **Critical Actions**; filters by period (**Start Date** and **End Date**) and by critical actions; and a table with **Date/Time**, **User**, **Operation**, **Artifact**, **Type**, **Workspace** and **Status**, with a search in each column. Clicking an event opens the **Event Details** panel, with general information, technical metadata (client IP, User Agent, Request ID, Activity ID) and the full JSON payload. * **Reports and Models**: a simplified view focused on consumption, creation, editing and deletion events for reports and semantic models. This makes it easy to answer who accessed, created, changed or deleted an artifact and when that happened. [See the documentation](/en/power-monitor/auditoria/geral-de-eventos.md) * **Audit collection settings**: the new *Settings › Audit* tab turns the Power BI **automatic activity log collection**, which feeds the Audit screens, on and off. In **Execution Times**, the default is one collection per day at 08:00 (UTC). With **Customize Time** you can set up to 4 daily times. The **Run now** button triggers a collection immediately, and its progress can be followed in *Settings › Scan Logs*. [See the documentation](/en/power-monitor/configuracoes/auditoria.md) * **Semantic model details window**: in *Governance › Semantic Models*, clicking a table row opens a window with the model details, organized into four tabs: * **Overview**: dataset ID (with a **Copy** button), who configured it, storage mode, creation date, content provider and whether effective identity is required; * **Tables & Schema**: the tables with their columns (name, data type, visibility and DAX expression), the measures with their DAX code, and the source Power Query (M) queries; * **Parameters**: the model's expressions and parameters; * **Permissions**: users and applications with access, principal type and access level. You can understand the structure of and access to a model without having to open Power BI Desktop. [See the documentation](/en/power-monitor/governanca/modelos-semanticos.md) * **Terms of use during installation**: the installation wizard now displays the **Terms of Acceptance**, and you must check **I have read and accept the terms of use** to complete the setup. Organizations that were already installed and had not yet recorded their acceptance also see the terms on their next access. [See the documentation](/en/readme/como-instalar-o-power-monitor/instalacao-automatica.md) ### Improvements * **Redesigned Governance Dashboard**: the *Governance Dashboard* has a new layout. At the top are the **Total Workspaces** and **Total Artifacts** cards, the latter with the average number of artifacts per workspace. The new **Capacity State** and **Infrastructure Resources** cards show the environment's capacities, gateways and connections. The **Audit (last 30 days)** card shows **Events**, **Active users**, **Audited workspaces**, **Report views** and the **Activity peak**, that is, the day and time with the most events. The **Audit events** come with the trend for the last 7 days compared with the previous 7. An **Attention · governance** banner tells you how many workspaces have had no activity for more than 30 days, and the **View full list** button opens the list already filtered. In the workspace list, each row has a shortcut to that workspace's audit events. [See the documentation](/en/power-monitor/dashboards/dashboard-de-governanca.md) * **Semantic model monitoring renamed and shown as a table**: the *Monitoring › Refreshes* item has been renamed **Semantic Models**. The screen is now a table with **Name**, **Status** (**Updated**, **Failed** or **No history**), **Verified**, **Changed** and **Date/Time**, with an **Open incident** indicator, a date filter, search by name or ID and a status filter. It is easier to quickly find the models that are failing. [See the documentation](/en/power-monitor/monitoramento/modelos-semanticos.md) * **"Datasets" is now "Semantic Models" in Governance**: the *Governance › Semantic Models* page adopted Microsoft's current naming in titles and cards and gained the **Composite Mode** card, which counts the models in composite mode. The storage column was removed from the table, and the page now loads much faster, especially in environments with many models. [See the documentation](/en/power-monitor/governanca/modelos-semanticos.md) * **Operation details in Usage Metrics**: in *Monitoring › Usage Metrics*, the operations table now shows **Start**, **End**, **Status** (**Success**, **Failed**, **In progress**), **Usage Type** (**Interactive** or **Background**) and **User**, with filters by item, workspace and user. The summary cards now include the **Success Rate** and the number of failures, and they update according to the filters applied. Times are sorted by local time, from 00:00 to 23:59. With this level of detail you can analyze, throughout the day, which operations consumed capacity and who ran them. [See the documentation](/en/power-monitor/monitoramento/metricas-de-consumo.md) * **Scan Logs in a table, with filters**: *Settings › Scan Logs* now displays the records in a table with **Scan Type**, **Status** and **Date/Time**, search by ID, selection of multiple scan types (including the new **Audit**, **Item Operation** and **Fabric Job**) and the **In Progress** status. By default, the screen loads the last 7 days, which makes it open faster. [See the documentation](/en/power-monitor/mapeamento/logs-de-scans-e-re-execucoes.md) * **Alerts load faster**: *Monitoring › Alerts* now loads the alerts from the last 7 days by default and shows a loading indicator. The date filter was adjusted: if you enter only the start date, the list begins with the oldest alerts from that date onward. [See the documentation](/en/power-monitor/monitoramento/alertas.md) * **Standardized date filters on the Governance screens**: the *Governance* lists (Reports, Paginated Reports, KQL Dashboards, Apps, Semantic Models, Storage, Data Engineering, Data Science and Capacities) gained the same date range picker above the table, with the **Created on** and **Modified on** fields. The column search fields on these screens, and also on Workspaces, Dashboards, Connections, Gateways, Alerts and Scan Logs, now have an **X** button to clear the text with one click. [See the documentation](/en/power-monitor/governanca/relatorios.md) * **Service principal name in Organization**: in *Settings › Organization*, the integration section now displays the **Service Principal Name** (the name of the Service Principal used by Power Monitor), with a button to copy it, in addition to the **Copy App Secret** button. This makes it easier to find the application in Azure and Power BI when granting permissions. [See the documentation](/en/power-monitor/configuracoes/organizacao.md) * **Dates in Brasília time in emails**: alert emails now show the date and time in Brazilian format and in the Brasília time zone, avoiding confusion with UTC times. * **Logo leads to the Dashboard**: clicking the Power Monitor logo at the top of the side menu now takes you straight to the **Dashboard**. ## June 1, 2026 ### Improvements * **Admin consent validation during installation**: in the permissions step of the installation wizard, Power Monitor now checks whether Azure admin consent has been granted to the application. If it is missing, the screen shows a button to request consent again, without having to restart the installation. The organization's first user is also now created correctly during self-installation. [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/2026/junho-2026.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.