Forum Discussion
Audit Log for On-Premises Power BI Report Server
Community SupportHi hashimkhan4626,
Just wanted to follow up. If the shared guidance worked for you, that’s wonderful hopefully it also helps others looking for similar answers. If there’s anything else you'd like to explore or clarify, don’t hesitate to reach out.
Thank you.
Hi
Thanks for follow up. Actualy With May 2025 Power BI Report Server, we are able to capture User Download activity using "Generating DataShape".
Please note that we are not getting information what we need using Execution Logs. We have already extensively explored these pre defined exectution logs1,2,3. If you are able to extend and get the download data by the user who is using Power BI Desktop, Excel Add in or MS Report Builder using Citrix
With the new version Jan 2026 Power BI Report Server, we lost the feature.
1. What is the alternative to monitor the download log user activity using
"Generating DataShape".
Requirement
1. We should be able to monitor which user used which report and downloaded/exported data from the .pbix or .rdl
2. Which tables being used by the .Pbix and .rdl to check the sensitive columns and information
3. Microsoft will be able to release customized version with old feature "Generating DataShape". If this is possible then can you please let me know the process to work?
It is possible to have teams meeting and explain our issues with the new version.
Thanks
Hashim
- v-kpoloju-msft
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.- v-kpoloju-msft
Hi hashimkhan4626,
Just checking in to see if the issue has been resolved on your end. If the earlier suggestions helped, that’s great to hear! And if you’re still facing challenges, feel free to share more details happy to assist further.Thank you.