Usage Metrics and the activity log answer different questions.
Use Usage Metrics when report and page behavior matters. Use the activity log when you need tenant-wide events and audit-oriented activity. Preserve either source externally before its native history ages out.
Choose the source from the decision.
| Question | Usage Metrics | Activity log |
|---|---|---|
| Primary purpose | Understand report consumption, viewers, page views, and opening performance. | Track user and administrator activities across Fabric and Power BI. |
| Scope | Workspace/report-oriented; the model can cover reports in its workspace. | Tenant activity available to authorized administrators. |
| Report page views | Yes, subject to client telemetry reaching Power BI. | No equivalent report-page-view detail in the Power BI audit log. |
| Report opens | Yes, as report views/opens. | ViewReport events can support activity analysis. |
| Other operations | Focused on usage and performance. | Broad event set, including creation, sharing, refresh, administrative, and viewing activities. |
| Native lookback | The current improved semantic model contains the last 30 days. | Power BI activity events can be retrieved for up to the previous 28 days. |
| Access | Applicable license, edit-capable workspace role, and tenant setting. | Fabric administrator access or an approved administrative collection identity. |
| Best long-term pattern | Scheduled extraction into a governed external store. | Daily export into a governed external store. |
Do not silently blend sources and call every event a “view.” Define the event, source, grain, time zone, exclusions, and known collection limitations in the report.
Use Usage Metrics for the consumption experience
The improved Usage Metrics report records report opens separately from report page views. That distinction matters: changing a page is not another report open, and page-view telemetry depends on information from the user’s device reaching Power BI. Microsoft also documents that the current model retains 30 days and can take up to 24 hours to show new activity.
This source is useful when the decision sounds like: “Which pages are people actually reaching?”, “Is opening performance changing?”, or “How is this report consumed?” It is not a perfect behavioral record, and the limitations should stay visible.
Use the activity log for tenant activity and audit questions
The activity log provides Power BI and Fabric operations as event records. It is a better foundation for questions such as who shared an item, who created or deleted content, and which report-view events occurred across the tenant. Microsoft’s guidance recommends exporting and retaining activity data because retrieval is limited to 28 days.
The log does not replace Usage Metrics for page-level consumption. Microsoft specifically notes that report page views are not part of the audit logs.
Use inventory APIs for the current estate
Neither activity events nor usage history should be treated as the complete current inventory. Reports can be deleted, renamed, or moved. Microsoft’s metadata scanning APIs return current workspaces and items, which can be joined carefully to event history when tenant-level permissions are available.
A practical architecture
- Collect the source needed for the question on a reliable schedule.
- Store raw, time-stamped data before the native window expires.
- Maintain stable item and workspace identity across name changes.
- Document missing client events, exclusions, privacy choices, and time zones.
- Model usage evidence separately from business criticality and ownership.
Which should you choose?
If you need a broad audit and adoption platform and have tenant-admin sponsorship, the activity log is usually the stronger backbone. If you specifically need page behavior and the experience available in Usage Metrics, preserve that source. Some mature implementations use both, but the added operational and identity-matching work should be intentional.
Primary Microsoft references
See whether UsageVault fits the narrower problem.
UsageVault is a focused, maintained path for selected-workspace Usage Metrics history. It is not positioned as a replacement for a tenant-wide audit platform.
Bring your workspace scope and source constraints.
Request a fit check