> 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-gerais/como-monitorar-mais-de-um-tenant.md).

# How do I monitor more than one tenant?

How Power Monitor handles multiple tenants and how a user from another tenant (consultant, partner, headquarters) accesses the organization.

In Power Monitor, **each Microsoft Entra ID tenant corresponds to one organization**. The data of one organization is isolated from the others: no one in one organization sees data from another.

Therefore, to monitor **multiple tenants** (for example, companies of the same group or clients of a consulting firm):

1. **Install Power Monitor in each tenant.** Each installation creates its own organization, with its inventory, alerts, users, and billing. See [How do I install Power Monitor?](/en/readme/como-instalar-o-power-monitor.md)
2. **Give access to the people who will follow each tenant.** Anyone who does not belong to the tenant must be invited as an **external user (B2B guest)** in that tenant's Entra ID and registered in **Users** in the Power Monitor of the corresponding organization.
3. **Switch organizations by switching accounts or tenants at sign-in.** Use **Switch Account** in the user menu and sign in to the desired organization.

{% hint style="info" %}
Access to Power Monitor is always done with a Microsoft account. There is no Power Monitor-specific username and password.
{% endhint %}

***

## Invite an external user to your tenant

A user from another tenant registered in Power Monitor may not be able to sign in until they are registered in **your** tenant. To fix this, an administrator of your Entra ID sends an invitation:

**1. Open the Azure portal**

Open the list of users in your tenant: [Microsoft Entra ID › Users](https://portal.azure.com/#view/Microsoft_AAD_UsersAndTenants/UserManagementMenuBlade/~/AllUsers).

**2. Invite the external user**

Click **+ New user** and select **Invite external user**.

<figure><img src="https://3938213054-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH2bFRBmIfyK3kwVKbldl%2Fuploads%2Fgit-blob-a4b846c6706b408ae0b122abfe92ef18078de894%2Fimage%20(2)%20(1).png?alt=media" alt="Invite external user option in the Azure portal"><figcaption></figcaption></figure>

**3. Fill in the details**

Enter the external user's email and name and click **Review + invite**.

<figure><img src="https://3938213054-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH2bFRBmIfyK3kwVKbldl%2Fuploads%2Fgit-blob-fb3a575e35b7a774e66b52a40f977c70ade7d8b9%2Fimage%20(3)%20(1).png?alt=media" alt="External user invitation form"><figcaption></figcaption></figure>

**4. The user accepts the invitation**

The user receives an email from Microsoft and clicks **Accept invitation** to be linked to your tenant.

**5. Register the user in Power Monitor**

In [Users](/en/power-monitor/usuarios.md), a Power Monitor administrator registers the user and defines the profile, the workspace scope, and the allowed pages.

***

## Sign in to Power Monitor with an external user

**1. Open the Power Monitor portal**

Open <https://app.powermonitor.com.br/>.

**2. Choose "Sign in to an organization"**

On the Microsoft sign-in screen, click **Sign-in options** and select **Sign in to an organization**.

<figure><img src="https://3938213054-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH2bFRBmIfyK3kwVKbldl%2Fuploads%2Fgit-blob-d6b17f80dfa33913ff3658d295300837330aaa2d%2Fimage%20(5).png?alt=media" alt="Sign-in options on the Microsoft sign-in screen"><figcaption></figcaption></figure>

<figure><img src="https://3938213054-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH2bFRBmIfyK3kwVKbldl%2Fuploads%2Fgit-blob-538e52102aaccecda67eeb1c809a7629b5b8d051%2Fimage%20(6).png?alt=media" alt="Sign in to an organization option"><figcaption></figcaption></figure>

**3. Enter the tenant domain**

Type the domain of the tenant you want to access. Example: `minhaempresa.com.br`.

<figure><img src="https://3938213054-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH2bFRBmIfyK3kwVKbldl%2Fuploads%2Fgit-blob-21bc210cb4b7cbf74078184644474e662ede8f4c%2Fimage%20(7).png?alt=media" alt="Organization domain field"><figcaption></figcaption></figure>

**4. Enter your account email**

Type the email of the invited account.

**5. Access granted**

After validation, you are redirected to the Power Monitor of that tenant's organization.

<figure><img src="https://3938213054-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH2bFRBmIfyK3kwVKbldl%2Fuploads%2Fgit-blob-745ea9e17071f1cb0eda6b8259d4d6ffdc7349e1%2Fimage%20(9).png?alt=media" alt="Power Monitor after sign-in"><figcaption></figcaption></figure>

***

## Frequently asked questions

<details>

<summary>Can I see multiple tenants in a single consolidated panel?</summary>

No. Each tenant is an isolated organization, with its own data and dashboards. To switch, sign in to the desired organization with **Switch Account**.

</details>

<details>

<summary>Is each tenant billed separately?</summary>

Yes. Each organization has its own trial period and its own monthly fee tier, calculated from the items monitored in that tenant.

</details>


---

# 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-gerais/como-monitorar-mais-de-um-tenant.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.
