> 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/perguntas-frequentes/duvidas-tecnicas/como-o-power-monitor-funciona-internamente.md). # How does Power Monitor work internally? How Power Monitor connects to your tenant, which APIs it uses, how often it collects data, and where the data is stored. Power Monitor is a SaaS application hosted by Power Tuning on **Microsoft Azure**. It connects to your tenant through the **official Microsoft APIs**, using an **application (Service Principal) registered in your Microsoft Entra ID**, without installing anything in your environment. ### Architecture summary ``` Your Microsoft tenant (Power BI / Microsoft Fabric / Entra ID / Azure) │ │ Official Microsoft APIs │ (authenticated with the Power Monitor application in your Entra ID) ▼ Power Monitor SaaS (Microsoft Azure, operated by Power Tuning) • inventory and metadata scans • continuous health and consumption checks • database isolated per organization │ │ alerts and summaries ▼ Your channels: email, Microsoft Teams, Slack, Telegram ``` ### Which APIs does Power Monitor use? | API | Purpose | | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | | **Power BI / Fabric admin APIs** (Scanner API) | Inventory of workspaces and items, semantic model metadata, lineage, data sources, users with access, capacities, gateways, connections, and apps | | **Power BI REST APIs** | Semantic model refresh history, gateway status, schedules | | **Microsoft Fabric REST APIs** | Runs of pipelines, notebooks, Copy jobs, and Dataflows Gen2, Fabric Mirroring, domains | | **Microsoft Fabric Capacity Metrics app** (query to its semantic model) | Capacity consumption in Capacity Units | | **Power BI Activity Events** (when enabled) | Activity events and report views | | **Microsoft Graph** | During automatic installation; and, when granted, reading users, groups, and members, and the client secret expiration | | **Azure Resource Manager and Cost Management** (when granted) | Pausing, resuming, and changing the size (SKU) of capacities and reading their cost | ### How often does Power Monitor check the environment? | What | Frequency | | --------------------------------------------------------------------------- | --------------------------------------------------------------------------------- | | Full inventory (workspaces, items, capacities, gateways, connections, apps) | At installation and then **daily**, in addition to on-demand scans in **Mapping** | | Capacity consumption | Every **5 minutes** | | Gateway status | Every **5 minutes** | | Semantic model refresh failures | Every **15 minutes** | | Fabric item runs | Every **2 hours** | | Data freshness and Fabric Mirroring | Every **10 minutes** | | Activity events (Activity Events) | **Three times a day** | | Number of items for billing | **Once a day** | ### Is access read-only? **Collection** is read-only: Power Monitor reads metadata and status. Some actions, however, **change your environment**, always explicitly and initiated by an administrator: * in the **automatic installation**, creating the application and the security group in Entra ID and applying the Fabric tenant settings; * granting the application administrator access to workspaces, gateways, and capacities (in **Additional Permissions**); * **pausing, resuming, and scaling** capacities (schedules, Auto-Scale, and manual scaling); * **reprocessing failed refreshes** of semantic models and changing refresh schedules, when an administrator requests it. ### Where is the data stored? The collected metadata (inventory, history, alerts, consumption, settings) is stored on Power Tuning infrastructure in **Microsoft Azure**, in a database with **isolation per organization**. The application credentials are **encrypted** with keys managed in **Azure Key Vault**. The **business data** of your reports and models is not copied. See [Data security and privacy](/en/perguntas-frequentes/duvidas-tecnicas/seguranca-e-privacidade.md). ### Can I revoke access at any time? Yes. Remove or disable the Power Monitor application in **Microsoft Entra ID › Enterprise applications** (and, if you want, delete the App Registration and the security group). From then on, Power Monitor can no longer collect data from your tenant. For architecture details, see the [Technical Documentation](/en/technical-documentation/documentacao-tecnica.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/perguntas-frequentes/duvidas-tecnicas/como-o-power-monitor-funciona-internamente.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.