Error 500 for the Data Quality feature in Microsoft Purview

Question

I am exploring how Microsoft Purview works. Everything worked fine, but suddenly I've gotten problems with the Data Quality feature. Whatever I do, I get these 500 errors and I don't know where to start debugging.

I have scanned two SQL databases and made a couple of data products. There are no problems under the Data Map, so the connection to the database should be alright. I made two data quality scans for the data products and I could open the scan history.

Suddenly, I started getting these 500 errors when I navigate through Data Quality. I can’t open any scans anymore. Furthermore, I can't delete any data products, as they are linked to a data asset. And when I try to remove the assets from the data product, the remove button is greyed out with the message: “Failed to load data quality data, need to check data quality data before removing this data asset.”

I don't think I've edited any settings, but I’m open to the possibility. Is this a known error? Any clues where to start debugging?

Answer 1

Hi Erlend Kallelid ,
When the scan objects become partially out of sync, Purview cannot load the Data Quality state correctly, which causes the UI to return 500 errors and blocks actions like removing assets or deleting the data product. Even though the scans and data sources still exist, the service fails to read their latest configuration.

When you opened the scan from Monitoring and saved it again, Purview revalidated and rewrote the scan metadata in the backend. That save action triggered a refresh of the Data Quality state, which restored the Scheduled scans view and removed the dependency lock on the data product. In other words, nothing was “fixed” manually — the save simply forced the service to resync the scan object.

This can occasionally happen when Data Quality metadata becomes stale or after backend updates, and re-saving the scan is a valid workaround because it rebuilds the internal reference used by Unified Catalog.

Answer 2

Problem solved!.

I was able to find my scans through the monitor. When I made an update to one of the scans and saved it, the error codes disappeared and I was able to find my scans under "scheduled scans" again. Now I'm also allowed to remove the assets from the data product and delete the entire product. Hurra!

But why did it work...