> 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/conformidade/links-publicos.md).

# Public Links

Inventory of the active "Publish to Web" links in the Power BI tenant, reports publicly exposed on the internet, with export to CSV and JSON.

The **Public Links** screen lists the active **Publish to Web** links in the Power BI tenant: reports that anyone on the internet, without sign-in, can open through a link or embed code. It is the same list the Power BI administrator sees in *Admin portal › Embed codes*, available here without requiring the Fabric administrator role.

**How to access:** menu *Governance › Compliance › Public Links*. Available to all profiles.

<figure><picture><source srcset="/files/1Z43V7QgAxAmaMyZZk9w" media="(prefers-color-scheme: dark)"><img src="https://3938213054-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH2bFRBmIfyK3kwVKbldl%2Fuploads%2Fgit-blob-57ff3475ca56172be5e00f1f1b4664aaa201f571%2Fpm-governanca-links-publicos-en.png?alt=media" alt="Public Links screen with the table of reports published to the web and the Export button"></picture><figcaption><p>Active "Publish to Web" links in the tenant</p></figcaption></figure>

{% hint style="danger" %}
**Publish to Web exposes the report data publicly, without authentication and without row-level security.** Review this list periodically: each row is a report that may be accessible to anyone on the internet. When sharing the exported file, remember that it contains employee names and emails: treat it as internal information.
{% endhint %}

## What it is for

* **Data exposure audit:** discover which reports are public and who published them.
* **Compliance (LGPD):** demonstrate, for audits, that no sensitive data is published to the web, or identify the links that need to be revoked.
* **Follow-up:** export the list for a periodic review process with the report owners.

The screen follows the [common structure of the Governance lists](/en/power-monitor/governanca/relatorios.md#common-structure-of-the-lists), but it is **read-only**: it has no details modal, actions menu, bulk selection or link to open the report.

## Features

All the features below start from the menu *Governance › Compliance › Public Links* and are available to all profiles.

### Public links table

**What it is:** the list of reports with an active Publish to Web link, with the workspace, who published it and the status of the link.

**What it is for:** have, in one place, all the reports exposed on the internet and the person responsible for each exposure.

**How to use:** read the table columns; it starts sorted by **Report name**, in alphabetical order, with 10 rows per page.

**How it works:**

| Column           | Description                                                           |
| ---------------- | --------------------------------------------------------------------- |
| **Report name**  | Report published to the web.                                          |
| **Workspace**    | Workspace of the report, when it is known to Power Monitor.           |
| **Published by** | Name and email of whoever created the link.                           |
| **Status**       | Status of the link. Currently Power BI returns only **Active** links. |

The list is read live from Power BI each time the screen is opened (see [Rules and behavior](#rules-and-behavior)).

### Filters and sorting

**What it is:** the text filter of the **Report name** column, the multiple-selection lists with search of the **Workspace** and **Published by** columns, the **Status** list and sorting by the column titles.

**What it is for:** separate the links of an area (workspace) or of a person to request the review directly from the person responsible.

<figure><picture><source srcset="/files/0IDPbBT9R4Q0E9aQYn9t" media="(prefers-color-scheme: dark)"><img src="https://3938213054-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH2bFRBmIfyK3kwVKbldl%2Fuploads%2Fgit-blob-5b49e2b1540e4c73e038c5765937669e9781030d%2Fpm-governanca-links-publicos-filtro-publicado-por-en.png?alt=media" alt="Multiple-selection list of the Published by filter open, with search and the list of who published"></picture><figcaption><p>Published by filter</p></figcaption></figure>

**How to use:**

1. Type the term in the filter box below the **Report name** column title (*Search by report name*). The table is filtered automatically.
2. In the **Workspace** (*Search workspace*) and **Published by** (*Search by who published*) columns, open the list, type to search and select one or more values. In the **Status** column, choose a value in *All statuses*.
3. Click the column title to sort. When you click another column, the first click sorts in descending order and the second reverses it.

**How it works:** the list options are built from the values present in the loaded list. The filters are combined with each other and applied to the list already loaded, without a new query to Power BI.

### Export

**What it is:** the **Export** button, at the top of the table, with the **CSV** and **JSON** options.

**What it is for:** generate a file for a review process with the owners or to document the situation in an audit.

<figure><picture><source srcset="/files/qjwAjaZ1cw66kBYdGx53" media="(prefers-color-scheme: dark)"><img src="https://3938213054-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH2bFRBmIfyK3kwVKbldl%2Fuploads%2Fgit-blob-6f243558ccab89a84ec831baa798364644abd9d8%2Fpm-governanca-links-publicos-exportar-en.png?alt=media" alt="Export menu open with the CSV and JSON options"></picture><figcaption><p>Export menu of the Public Links screen</p></figcaption></figure>

**How to use:**

1. (Optional) Apply the desired filters: the export includes **all rows visible with the filters applied**, not only the current page.
2. Click **Export**, at the top of the table, and choose **CSV** or **JSON**.
3. The file is downloaded by the browser.

**How it works:** the file contains the columns Report name, Workspace, Published by and Status.

{% hint style="warning" %}
The exported file contains employee names and emails. Treat it as internal information and be careful when sharing it or pasting it into other tools.
{% endhint %}

### Review and revoke public links

**What it is:** the recommended periodic review flow, which combines this screen's export with revocation in Power BI.

**What it is for:** keep on the internet only what can really be public.

**How to use:**

{% stepper %}
{% step %}

#### Export the list

Click **Export › CSV** to generate the current list of public links.
{% endstep %}

{% step %}

#### Validate with the owners

Use the **Published by** column to contact whoever created each link and confirm whether the publication is still needed and whether the content can be public.
{% endstep %}

{% step %}

#### Revoke in Power BI

For links that should not exist, delete the embed code in Power BI (*Admin portal › Embed codes*, or in the report settings). When you reopen this screen, the link no longer appears.
{% endstep %}
{% endstepper %}

**How it works:** revocation is not done by Power Monitor, because the Power BI API does not offer this operation.

## Rules and behavior

* **Live query:** the list is read directly from Power BI (Admin API) each time the screen is opened: it does not depend on the inventory scan. Therefore it reflects the current state of the tenant.
* **Prerequisite:** the Power Monitor Service Principal must be configured with read permission on the Power BI Admin APIs. Otherwise, the screen shows "Could not load the public links." with the **Retry** button.
* **Whole tenant:** the list covers the entire tenant, including reports in unmonitored workspaces. Name and workspace are complemented with the Power Monitor inventory; when the report is not in the inventory, the name reported by Power BI is shown and the workspace is blank.
* **Revoking a link** is not possible through Power Monitor: the Power BI API does not offer this operation. Revoke the embed code in Power BI itself (*Admin portal › Embed codes*, or in the report settings).

## Frequently asked questions

<details>

<summary>The list is empty. Does that mean there are no public links?</summary>

If there is no error message, yes: Power BI did not return any active link. If "Could not load the public links" appears, check the Service Principal configuration and the permission to use the Admin APIs in the tenant.

</details>

<details>

<summary>Why is there no button to open or copy the public link?</summary>

The Power BI API does not return the public URL of the link, only the report and who published it. To see the link, use the Power BI admin portal.

</details>

## Related pages

* [Reports](/en/power-monitor/governanca/relatorios.md)
* [Data Exposure](/en/power-monitor/qualidade-de-dados/exposicao-de-dados.md)
* [Permissions Audit](/en/power-monitor/auditoria/auditoria-de-permissoes.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/governanca/conformidade/links-publicos.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.