> 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/mapeamento/assinaturas-de-email.md).
# E-mail Subscriptions
Follow, trigger and pause the daily collection of Power BI e-mail subscriptions (how many subscribers and how many are from an external domain).
The **E-mail Subscriptions** collection checks, for each Power BI report and dashboard that had an e-mail subscription created or changed, **how many subscribers** exist and **how many are from an external domain**. The list of artifacts and the indicators are in Audit; this screen shows the collection history and lets you trigger or pause it. The data screen shows only counts, never a subscriber's name or e-mail.
**How to access:** *Mapping › Audit and compliance › E-mail Subscriptions*. Only **Administrators** can access the screen and the actions. On the data screen, all profiles see the **Collection** line with the date of the last run; the **View/manage collection →** link, which leads here, appears only for administrators.
E-mail Subscriptions
## What it is for
* Keep up to date the audit in [Audit › E-mail Subscriptions](/en/power-monitor/auditoria/assinaturas-de-e-mail.md), which helps you find deliveries to external recipients or to people who have already changed areas.
* Check the subscriptions right away, just after creating or changing a subscription in Power BI.
* Confirm that the collection is running and investigate artifacts that could not be checked.
## Screen components
The screen has a header (*Mapping* and the collection subtitle) and two cards.
### What is collected card
Describes the source and the cadence (*Source, cadence and where the data shows up*) and has, at the bottom, the **View collected data in E-mail Subscriptions →** link, which leads to the data screen.
### Collection runs card
The **Collection runs** card (*Automatic daily collection, every day at 10am Brasília time. Trigger manually if you do not want to wait.*) holds the buttons and the history.
E-mail subscription collection runs
| Element | What it is for |
| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Run now** / **Resume** | Triggers a manual collection. When there is a **Paused** run, the button is renamed **Resume** and continues from the artifact where it stopped. It works even with the automatic collection turned off. |
| **Pause** | Appears only during a run in progress. The pause is cooperative: the notice **Pause requested: the run stops after the next processed item** appears and the run becomes **Paused** when it finishes the current artifact. |
| State badges | **Run in progress (n)** (with a progress bar), **Run paused** and, if automatic tracking ends, **Automatic refresh stopped. Reload the page to see the current status.** |
| Runs table | History from the most recent to the oldest, with an items-per-page selector and pagination. |
| **View failures** | Link in the **Failures** column that opens the **Failures for the {date} run** modal, with **Item**, **Reason** and **Detail**. |
Table columns:
| Column | Content |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------- |
| **Trigger** | **Scheduled** or **Manual** (for manual runs, hover over the person icon to see who triggered it) |
| **Started** / **Finished** / **Duration** | Run times (no end and duration while it is active) |
| **Status** | **Running**, **Paused**, **Completed**, **Failed** or **Stuck** |
| **Items processed** | Reports and dashboards already checked by the run (including those that failed) |
| **Failures** | Artifacts whose check was not confirmed; **View failures** link |
| **Error** | Icon with the run's general error message (hover over it) |
## Rules and behavior
* **Where the data comes from:** Power BI administration API, which reports the e-mail subscriptions and recipients of each report and dashboard, queried with the organization's Service Principal.
* **How artifacts are chosen:** the collection looks, in the activity log already collected by Power Monitor, for subscription **creation** and **change** events from the **last 30 days**. Each report or dashboard with those events is checked. Artifacts whose most recent event is the **deletion** of the subscription are no longer checked. For this reason, the collection depends on the activity log (see [Audit](/en/power-monitor/mapeamento/auditorias.md)).
* **Call pace:** queries to the administration API are spaced out to respect the Power BI request limit; with many artifacts, the run can take longer.
* **Required permission:** the same read-only administration API permission used by the scans (the tenant setting **Service principals can access read-only admin APIs**, enabled for the security group that contains the Service Principal). See [How to enable the domain collection permission](/en/power-monitor/mapeamento/dominios.md#how-to-enable-the-domain-collection-permission) and [Additional Permissions](/en/power-monitor/configuracoes/permissoes-adicionais.md). Without it, artifacts appear as **No permission to check** on the data screen and count in **Failures** here.
* **Frequency:** daily, at **10:00** (Brasília time, UTC-3), for organizations with a Service Principal configured. In [Settings › Monitoring](/en/power-monitor/configuracoes/monitoramento.md#scans-and-collections), **Scans and Collections** section, **Others** group, the **Power BI e-mail subscriptions** switch turns the automatic collection on or off (it is on by default) and the **Frequency** selector allows **Daily**, **Weekly** or **Monthly**. With the weekly and monthly options, the run happens on a day distributed per organization, and the item shows **Next expected run** and **Last run**. **Run now** is never affected: it works with the switch turned off and at any frequency.
* **A failure on one artifact does not bring the collection down:** the artifact that failed is counted in **Failures** (reasons such as no permission, request limit or check failure) and the run continues.
* **Stuck:** a run with no progress for **10 minutes** is closed as **Stuck**.
* **Concurrency:** there is only one active run (in progress or paused) per organization. When you try to trigger another one, *A run is already in progress for this organization.* appears.
* **Screen refresh:** while there is an active run, the table refreshes by itself every 20 seconds, for up to 30 minutes.
{% hint style="info" %}
The list is a survey based on recent activity, not a complete inventory of all subscriptions in the tenant: a subscription created before the 30 days checked and never changed only appears if it was already checked before.
{% endhint %}
## Step by step
{% stepper %}
{% step %}
### Open the collection screen
Go to *Mapping › Audit and compliance › E-mail Subscriptions* with an administrator account.
{% endstep %}
{% step %}
### Trigger the collection
In the **Collection runs** card, click **Run now**. There is no confirmation; the button shows **Running…** and the message *Run queued. The history updates when it starts.* appears. If the subscription has just been created, first wait for the activity log collection, which is where the artifacts are discovered from. While the collection service has not picked up the run, the button shows **Queued** and the card says *Run queued, waiting to start…*; then the button changes to **In progress** and the bar shows the processed items (for example, *12 of 40*) and the estimated time left (*\~3 min left*). The screen tracks the run until it finishes, without reloading.
{% endstep %}
{% step %}
### Follow it
Watch the **Run in progress** badge and the new row in the history. If you need to stop it, click **Pause**; later use **Resume** to continue.
{% endstep %}
{% step %}
### Confirm the result
When the run shows as **Completed**, open [Audit › E-mail Subscriptions](/en/power-monitor/auditoria/assinaturas-de-e-mail.md) through the link in the **What is collected** card and check the artifacts. If there are failures, click **View failures**.
{% endstep %}
{% endstepper %}
## Frequently asked questions
I created a subscription and it does not appear on the data screen.
The subscription is discovered through the creation event in the activity log. Wait for the activity event collection and then for the daily check (10:00, Brasília time), or click **Run now** here after the event has already been collected.
Several artifacts appear in Failures with "No permission".
The Service Principal cannot use the administration API. Enable the tenant setting for the group that contains the Service Principal (see **Required permission**) and click **Run now**.
Does the collection show subscribers' names or e-mails?
No. The data screen stores and shows only counts of subscribers and of external subscribers.
## Related pages
* [Audit › E-mail Subscriptions](/en/power-monitor/auditoria/assinaturas-de-e-mail.md)
* [Audit](/en/power-monitor/mapeamento/auditorias.md)
* [Settings › Monitoring](/en/power-monitor/configuracoes/monitoramento.md)
* [Additional Permissions](/en/power-monitor/configuracoes/permissoes-adicionais.md)
* [Mapping](/en/power-monitor/mapeamento.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/power-monitor/mapeamento/assinaturas-de-email.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.
