
Reporting Operations
Part of BI system performance and cost control
Monitoring unused BI licences and scheduled jobs
Compare BI entitlements and scheduled jobs with actual tasks, telemetry coverage and dependencies before changing access or schedules.
Review assigned BI licences and scheduled jobs whenever a reporting need changes. Compare entitlements and recurring work with observed use, then confirm each apparent gap with the owner before changing access or schedules. A usage chart alone cannot prove that a person or job is unnecessary.
Build two inventories
For licences, record the person or service identity, product, licence type, role, granting route and approved task. For Microsoft licences, start in the Microsoft 365 admin centre: the licences page under Billing lists assignments by product, and the Active users page under Users shows each person's licences.
For jobs, record the scheduled action, owner, frequency, source, output, recipients or dependent reports, last successful run and required data cut-off. Include refreshes, extracts and deliveries outside the interactive BI interface, such as Power BI email subscriptions, which send a snapshot, link or attachment on a set schedule.
For a bulk inventory of Fabric and Power BI items, the scanner APIs, a set of Admin REST APIs, extract each item's name, owner, sensitivity label, applied tags and endorsement status. Use that list to find content with no named owner.
Match each job to its consumers. A model refresh may serve several reports; a scheduled file may reach someone who never opens the interactive report. A person with a paid authoring licence may now only view content, but the review must establish what they actually do and which permissions that task requires.
Interpret activity carefully
Power BI usage metrics help show how dashboards and reports are used, including who uses them and for what purpose. They track SharePoint Online embedded views but omit some other embedding routes, including the documented user-owns-credentials and app-owns-credentials flows. Usage metrics therefore do not show every route of use.
For a tenant-wide view of who did what, use the Power BI activity log. The ActivityEvents REST API downloads up to one day of activities per request and can optionally filter by activity type or user ID. The Get-PowerBIActivityEvent cmdlet downloads activity events for one day at a time. The audit log in the Microsoft Purview portal searches the same activity by date range, defaulting to the past seven days.
A report used on an annual cycle may not appear active in the period you review. Check the normal cycle and delivery routes before calling an entitlement unused.
Power BI licence needs depend on activity and where content is hosted. Free, Pro and Premium Per User access have different sharing conditions; eligible capacity can also affect what a free viewer may consume. Subscribing others to a report, for example, requires a paid Pro or PPU licence. Check the person's authoring, workspace and viewing tasks before changing their licence, and confirm the organisation's purchase terms before claiming a saving.
For scheduled refresh on applicable Power BI Premium capacities, the administrator's Refresh summary shows recent history and scheduled overlap. It does not inventory every reporting job. Check other schedulers and warehouse tasks separately when they are part of the delivery path, such as Snowflake tasks, whose past execution times can be explored in Snowsight or the ACCOUNT_USAGE views.
Power BI Licence Types and Their Sharing Conditions
- Free Licence
- View content only; cannot share reports or publish to workspace
- Pro Licence
- Create, share and publish reports; subscribe others to reports
- Premium Per User (PPU)
- Full authoring, sharing, and access to Premium capacity features
Key Metrics for Unused BI Licence Detection
- Days of Activity Log Available
- 1 day per API request
- Coverage of Embedded Views
- Includes SharePoint Online but excludes some credential flows
Decide what to keep, change or pause
| Finding | Candidate action | Check first |
|---|---|---|
| Paid entitlement without observed use | Confirm the task with the user and manager | Authoring, shared content and activity outside the metric’s coverage |
| Frequent job for a weekly decision | Consider fewer runs | Required cut-off and dependent outputs |
| Job without an identified consumer | Investigate its purpose | Exports, subscriptions and recovery use |
| Duplicate deliveries | Consolidate one route | Recipient needs, filters and access |
Record the decision, owner, affected people and date. For a job considered for retirement, use a recoverable pause and watch for affected outputs.
After changing a licence, check that the person can still complete the approved task and that unwanted elevated access has been removed. Repeat the review after team changes, report retirement or a new dataset dependency.
Scheduled Job Review Cycle for Reporting Compliance
- Quarterly Usage AuditUse Power BI activity log and REST API to assess actual usage patterns
- Annual Dependency ReviewConfirm data cut-offs, consumer needs, and report retirement status
Pre-Change Verification Steps for BI Access and Jobs
- Confirm user’s current tasks with managerVerify if the person still requires their licence for authoring or viewing
- Check all delivery routes including email subscriptionsEnsure no hidden consumers exist outside interactive use metrics
- Validate dependent reports and outputsEnsure pausing a job won’t disrupt downstream reporting
- Review audit logs for past activityUse Microsoft Purview portal or Get-PowerBIActivityEvent cmdlet
Further reading: Power BI service features by license type (learn.microsoft.com).



