Purview does not reflect assets that are removed from PowerBI Workspace

Question

We have setup Power BI/ Fabric tenant in MS Purview to be scanned twice a week to capture the new workspaces and reports created. When a report or workspace is removed from the tenant, purview does not capture this information and remove the corresponding assets- this results in incorrect representation of the reports and spaces we have in our Power BI PROD. Is there a way to fix this issue as we don't want business to be looking for/ trying to access reports that no longer exists in a workspace.

Answer 1

@Gokul Sundararajan

It seems you're encountering an issue with Microsoft Purview not reflecting the deletions of reports and workspaces from Power BI. This can definitely cause confusion for users trying to access assets that no longer exist.

Currently, Microsoft Purview scans capture new workspaces and reports but may not immediately reflect deletions. When a report or workspace is removed in Power BI, Purview may not update accordingly during the scheduled scan, which results in outdated assets remaining in the catalog.

Here are a few suggestions that may help address this issue:

Increase Scan Frequency - If possible, consider increasing the frequency of your scans in Microsoft Purview. This might help reflect deletions more promptly and keep the catalog up to date.

Manual Refresh - You can manually trigger a scan to refresh the data. This will help in catching any deletions that have occurred since the last scheduled scan.

Check Asset Deletion Notifications - Ensure that asset deletion notifications are set up correctly. Sometimes the notifications for deleted assets may not be configured to trigger updates in Purview.

Use the “Deleted Assets” Report - Microsoft Purview provides a “Deleted Assets” report within the Unified Catalog. You can use this to identify assets that were removed recently, which may help highlight any discrepancies in the catalog.

Feature Request - If none of the above solutions are ideal, appreciate if you could share the feedback on our feedback channel. Which would be open for the user community to upvote & comment on. This allows our product teams to effectively prioritize your request against our existing feature backlog and gives insight into the potential impact of implementing the suggested feature.

I hope this information helps. Please do let us know if you have any further queries.

---

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know. Thank you.