> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.1/connectors/connector-repositories/reporting-tool/power-bi/power-bi-cloud/power-bi-usage-metrics-reports.md).

# Power BI Usage Metrics Reports

This article outlines how Power BI generates, manages, and stores Usage Metrics reports, including their visibility, workspace behavior, report-level behavior, and dependency on system-generated semantic models. It also explains the differences between Power BI-managed usage metrics datasets and user-created semantic models.

Usage Metrics reports help monitor report and dashboard activity within Power BI. These reports are system-generated and behave differently from standard user-created PBIX reports.

## Usage Metrics Reports

### Usage Metrics Report Visibility

Usage Metrics reports are not displayed in the workspace Reports list by default because the reports are system-generated artifacts managed by the Power BI Service.

Unlike standard PBIX reports, Usage Metrics reports are accessible only through the **Usage Metrics** option available from the ellipsis (...) menu of a report or dashboard.

### Key Details

<table><thead><tr><th width="186">Item</th><th>Description</th></tr></thead><tbody><tr><td>Report creation</td><td>Power BI automatically generates Usage Metrics reports when usage metrics are accessed for a report or dashboard.</td></tr><tr><td>Workspace visibility</td><td>Usage Metrics reports do not appear in the workspace Reports list unless a manual copy of the report is saved.</td></tr><tr><td>Access method</td><td>Usage Metrics reports are accessible from the Usage Metrics option available in the ellipsis (...) menu of reports and dashboards.</td></tr><tr><td>Standard report conversion</td><td>Selecting Save a copy converts the system-generated Usage Metrics report into a standard report visible within the workspace.</td></tr></tbody></table>

<div align="left"><img src="/files/aC1r0N0P4AoKoyVgp8Qf" alt="" height="215" width="624"></div>

{% hint style="warning" %}

* Usage Metrics reports are not treated as standard user-created reports.
* The reports become visible in the workspace only after selecting Save a copy.
* Saving a copy converts the system-generated report into a standard PBIX report.
  {% endhint %}

## Workspace-Level Functionality

Power BI does not automatically generate a single Usage Metrics report for an entire workspace.

Usage metrics remain associated with individual reports and dashboards instead of the complete workspace.

### Key Details

<table><thead><tr><th width="221">Workspace Functionality</th><th>Description</th></tr></thead><tbody><tr><td>Default workspace summary report</td><td>Power BI does not create a built-in Usage Metrics report that summarizes activity across all reports and dashboards within a workspace.</td></tr><tr><td>Metrics scope</td><td>Usage metrics are tracked separately for each report and dashboard available in the workspace.</td></tr><tr><td>Workspace-wide monitoring</td><td>A consolidated workspace-level monitoring solution requires manual implementation using exported activity or telemetry data.</td></tr></tbody></table>

{% hint style="info" %}
Workspace-wide usage analytics requires custom implementation using Power BI Activity Logs, Admin APIs, or exported telemetry data.
{% endhint %}

## Report and Dashboard-Level Functionality

Each report and dashboard within a workspace can have an independent Usage Metrics report.

The Usage Metrics report is generated only after the Usage Metrics option is accessed for the first time.

Although telemetry collection occurs automatically in the background, the visual Usage Metrics report appears only after the request is initiated.

### Key Details

<table><thead><tr><th width="222">Item</th><th>Description</th></tr></thead><tbody><tr><td>Metrics availability</td><td>Each report and dashboard can maintain a separate Usage Metrics report containing individual activity and usage details.</td></tr><tr><td>Initial report generation</td><td>Power BI generates the Usage Metrics report only when the Usage Metrics option is opened for the first time.</td></tr><tr><td>Background telemetry collection</td><td>Power BI continuously collects usage and activity data in the background, even before the Usage Metrics report is opened.</td></tr><tr><td>Saved copy support</td><td>Usage Metrics reports can be saved as standard reports within the workspace using the Save a Copy option.</td></tr></tbody></table>

<div align="left"><img src="/files/DZkLcglnkRBTJ1jW4kJ5" alt="" height="275" width="624"></div>

{% hint style="info" %}

* Usage Metrics reports are created independently for each report and dashboard.
* Saved copies operate like standard reports within the workspace.
* Saving a copy does not create a separate telemetry dataset.
  {% endhint %}

## Semantic Model (Dataset) Functionality

When Usage Metrics is opened for the first time within a workspace, Power BI automatically creates a hidden semantic model that stores telemetry and usage data for that workspace.

This semantic model is managed internally by the Power BI Service and supports both the system-generated Usage Metrics reports and saved report copies.

### Key Details

<table><thead><tr><th width="219">Dataset Functionality</th><th>Description</th></tr></thead><tbody><tr><td>Dataset creation</td><td>Power BI automatically creates a hidden Usage Metrics dataset when usage metrics are accessed for the first time within a workspace.</td></tr><tr><td>Dataset visibility</td><td>The Usage Metrics dataset remains hidden from the standard workspace view and is not treated as a regular semantic model.</td></tr><tr><td>Dataset management</td><td>The dataset is fully managed internally by the Power BI Service without manual administrative control.</td></tr><tr><td>Dataset usage</td><td>The same hidden dataset supports system-generated Usage Metrics reports and all saved report copies within the workspace.</td></tr><tr><td>Refresh management</td><td>Power BI controls dataset refresh operations internally without allowing manual or scheduled refresh configuration.</td></tr></tbody></table>

{% hint style="warning" %}

* A single hidden Usage Metrics dataset is created per workspace.
* Saved copies of Usage Metrics reports continue to reference the same hidden dataset.
* The dataset cannot be manually refreshed, modified, or scheduled for refresh.
  {% endhint %}

{% hint style="info" %}
The hidden Usage Metrics dataset remains read-only and cannot be directly edited or customized.
{% endhint %}

## Usage Metrics Datasets Vs User-Created Semantic Models&#x20;

Power BI-managed Usage Metrics datasets differ significantly from user-created semantic models.

User-created semantic models provide full administrative control over refresh schedules, updates, APIs, and modifications, whereas Usage Metrics datasets remain read-only and service-managed.

### Comparison

<table><thead><tr><th width="205">Feature</th><th>Usage Metrics Dataset</th><th>User-Created Semantic Model</th></tr></thead><tbody><tr><td>Dataset ownership</td><td>Managed internally by the Power BI Service.</td><td>Managed by the report or semantic model owner.</td></tr><tr><td>Refresh control</td><td>Refresh operations are controlled automatically by Power BI.</td><td>Manual and scheduled refresh operations are supported.</td></tr><tr><td>Scheduled refresh support</td><td>Scheduled refresh configuration is not available.</td><td>Scheduled refresh configuration is supported.</td></tr><tr><td>Manual refresh support</td><td>Manual refresh execution is not supported.</td><td>Manual refresh execution is supported.</td></tr><tr><td>API-based updates</td><td>Dataset updates through APIs are not supported.</td><td>API-based updates and management operations are supported.</td></tr><tr><td>Dataset modification</td><td>Direct modification or customization is not supported.</td><td>Dataset structure and logic can be modified as required.</td></tr><tr><td>Intended usage</td><td>Used internally for storing and displaying usage telemetry data.</td><td>Used for custom reporting, analytics, and business intelligence implementations.</td></tr></tbody></table>

{% hint style="warning" %}
Custom refreshable usage analytics solutions require the extraction of usage data through Power BI Activity Logs or Admin APIs, followed by the creation of an independent semantic model and reporting solution.
{% endhint %}

## Implementation Considerations&#x20;

The following approaches are commonly used for implementing Usage Metrics monitoring solutions in Power BI.

<table><thead><tr><th width="255">Requirement</th><th>Recommended Approach</th></tr></thead><tbody><tr><td>Standard usage monitoring</td><td>Use the built-in Usage Metrics reports available within Power BI reports and dashboards.</td></tr><tr><td>Workspace-wide analytics</td><td>Create custom reporting solutions using Power BI Activity Logs or Admin APIs.</td></tr><tr><td>Refreshable analytics solution</td><td>Build a separate semantic model using exported telemetry or activity log data.</td></tr><tr><td>Centralized monitoring</td><td>Use tenant-level usage datasets available for Power BI administrators to monitor activity across multiple workspaces.</td></tr></tbody></table>

{% hint style="info" %}
Tenant-level usage monitoring provides centralized visibility across multiple workspaces and supports governance, auditing, and usage analysis requirements.
{% endhint %}

## Summary&#x20;

<table><thead><tr><th width="233">Summary Point</th><th>Description</th></tr></thead><tbody><tr><td>Visibility</td><td>Usage Metrics reports are not automatically visible in workspace report lists and require manual saving to appear as standard reports.</td></tr><tr><td>Report generation</td><td>Usage Metrics reports are created separately for each report and dashboard within a workspace.</td></tr><tr><td>Workspace-level report availability</td><td>Power BI does not automatically generate a consolidated workspace-wide Usage Metrics report.</td></tr><tr><td>Saved copy functionality</td><td>Saved copies appear as standard reports within the workspace while continuing to use the same hidden dataset.</td></tr><tr><td>Dataset architecture</td><td>Power BI creates one hidden Usage Metrics dataset for each workspace.</td></tr><tr><td>Dataset refresh management</td><td>Dataset refresh operations are fully controlled by the Power BI Service.</td></tr><tr><td>Saved report copy dependency</td><td>Saved Usage Metrics report copies continue to depend on the original hidden dataset.</td></tr><tr><td>Custom analytics implementation</td><td>Advanced analytics solutions require Activity Logs or Admin APIs combined with independently created semantic models and reports.</td></tr></tbody></table>

{% hint style="warning" %}
Advanced and refreshable usage analytics implementations require custom semantic models created using exported activity logs or Power BI Admin API data.
{% endhint %}

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ovaledge.com/release8.1/connectors/connector-repositories/reporting-tool/power-bi/power-bi-cloud/power-bi-usage-metrics-reports.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.