> 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/power-monitor/governanca/infraestrutura.md).

# Infrastructure

Governance menu group that brings together what supports the execution of the environment: capacities, gateways, connections and Capacity Unit quotas in Azure.

The **Infrastructure** group brings together, in the Governance menu, the screens for the resources that support the execution of the artifacts: the Fabric and Power BI Embedded **capacities** where the items run, the **gateways** and **connections** that lead to the data, and the **Capacity Unit quotas** of each Azure subscription and region.

Use the group to survey the tenant's infrastructure: how many capacities exist, the cost and SKU of each one, which gateways are outdated, which connections use a password or have no privacy level, and how much of the Azure quota is still free before you create or resize a capacity. Reading the screens is open to all profiles; write actions (for example, pausing or changing the size (SKU) of a capacity, **Run now** and **Pause** in the Azure Quotas collection) are exclusive to **Administrators**.

## How to open

1. In the side menu, click **Governance**.
2. Click **Infrastructure** to expand the group and choose the screen, for example *Governance › Infrastructure › Capacities*.

The group is collapsible: clicking its name only expands or collapses the list, without changing the screen. When the open screen belongs to it, the group is already expanded. On the [Home](/en/power-monitor/pagina-inicial.md) page, each screen in the group has its own shortcut in the Governance section.

## Screens in the group

| Screen                                                                      | What it shows                                                                                                                                                                             |
| --------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Capacities](/en/power-monitor/governanca/infraestrutura/capacidades.md)    | Capacity inventory, cost, pause/resume/change size (SKU) via Azure, schedules, autoscaling and time-based alerts. The same screen is also available at *Capacities › Capacity Governance* |
| [Gateways](/en/power-monitor/governanca/infraestrutura/gateways.md)         | Data gateways, version status, permissions and reverse lineage                                                                                                                            |
| [Connections](/en/power-monitor/governanca/infraestrutura/conexoes.md)      | Single inventory of connections and data sources, privacy, credentials, permissions and lineage                                                                                           |
| [Azure Quotas](/en/power-monitor/governanca/infraestrutura/azure-quotas.md) | Limit and current usage of Fabric Capacity Units by Azure subscription and region                                                                                                         |

## Related pages

* [Governance](/en/power-monitor/governanca.md): overview of the module and of the menu groups
* [Capacities (domain)](/en/power-monitor/capacidades.md): the capacity screens gathered in one place
* [Operations](/en/power-monitor/governanca/operacao.md): refresh and job schedules that run on the capacities


---

# 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/power-monitor/governanca/infraestrutura.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.