Audit Log for On-Premises Power BI Report Server

Hi hashimkhan4626, 
Thanks for the detailed follow-up.

The behaviour you were using earlier (“Generating DataShape”) is not a documented or supported auditing feature in Power BI Report Server, so it isn’t guaranteed across versions and currently has no direct replacement in the Jan 2026 release. Now, PBIRS does not natively support tracking detailed data export activity (who downloaded what data), or table/column level usage from PBIX or RDL reports. The existing ExecutionLog tables can still help you understand who accessed which report and in what format (like Excel/CSV), but they won’t capture the actual data or dataset-level details you’re looking for.

As an alternative, you can partially monitor export behaviour using Execution Logs (based on render format) and combine that with backend SQL Server auditing (like Extended Events) to get visibility into query activity. For stricter governance, you may also consider limiting export options or applying row-level security. If full auditing (including export tracking and lineage) is a critical requirement, this is currently only available in Power BI Service (via audit logs and Purview). Regarding your request for restoring the old behaviour or a custom build, that isn’t something supported however, you can submit this as a feature request through the official feedback channel for product team consideration. Fabric Ideas - Microsoft Fabric Community

Thank you for using the Microsoft Fabric Community Forum.