Microsoft Security | Microsoft Purview
A unified data governance solution that helps manage, protect, and discover data across your organization
Purview: Failure Deletion Scan Rules Set
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(156.8, 81%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
JF
96
Reputation points
I am trying to delete an obsolete custom scan rule set in the Purview interface as it is not needed anymore, but I get the following error: Request failed with status code 409 Request ID: bfa2683d-b31a-45b0-95a1-6ce70900c54a Scan ruleset ScanRules_Synapse cannot be deleted when a dependency exists. It seems like the scan rule set is still being referenced by a scan, although there is no scan referring to the scan rule set anymore. I think the following scenario took place: while deleting a source, its connected scan was not well removed. Therefore, in Purview somewhere, the scan rule set is still referenced by the scan, although the scan does not exist anymore. How can I overcome this issue so I can delete the scan rule set? Or is there some delay before the deleted source and its scan is completely removed from Purview? Thanks in advance.
Microsoft Security | Microsoft Purview
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(86.4, 36%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBM%3C/text%3E%3C/svg%3E)
Bhargava-MSFT 31,356 Reputation points Microsoft Employee Moderator2023-04-05T19:57:11.9733333+00:00 Hello JF, Welcome to the MS Q&A platform.
I was able to reproduce the error when a scan refers to the custom ruleset. But you mentioned the dataset(source) was already removed. If you remove the dataset, all existing scans will be removed immediately from that dataset. I am guessing the scan rule set 'ScanRules_synapse' might be referred to in a different dataset too. This could be the reason for your error. Please find any scans that are still referencing the scan rule set; try to delete them first. This would resolve the issue.
I hope this helps. Please let me know if you have any further questions.
-
JF 96 Reputation points
2023-04-06T09:01:35.3433333+00:00 I have double checked and there are no scans anymore that are referencing the custom scan rule set that I am trying to delete, but the issue persists. I have tried deleting other custom scan rule sets after deleting their associated scan, as you suggested, and this works fine. For this one scan rule set, though, there remains an issue. This particular scan rule set has been connected to a datasource and a scheduled scan in the past and has been running. Recently, I have deleted this datasource from Purview. I did not explicitly delete the scan associated with the source. As you said, normally, when deleting a source, also the associated scans are removed. I think there has been issue here. The scan rule set might still reference the scan associated with the deleted source (although the scan should also be removed normally) which blocks deletion of the scan rule set. Can you verify whether this scenario can indeed occur? Thanks in advance for your help.
-
Bhargava-MSFT 31,356 Reputation points Microsoft Employee Moderator
2023-04-06T17:47:52.78+00:00 Hello JF, If you delete the data source, all associated scans will be removed. You don't need to remove the associated scans explicitly. One last thing, can you please try from a different browser or using an Incognito browser? Not sure if this is some cache issue? And It seems like the issue you are facing is a one-off case. I tried reproducing this from my end, but I don't see this behavior from my end. I suggest opening a support case if this is still an issue so that the support engineer can delete the custom scan rule set from the backend. If you don't have a support plan, please let me know so I can work with you offline to enable a one-time support request. I am looking forward to hearing from you.
-
Bhargava-MSFT 31,356 Reputation points Microsoft Employee Moderator
2023-04-08T00:35:49.3466667+00:00 Hello JF,
I am checking to see if you got a chance to look into my above response. -
Bhargava-MSFT 31,356 Reputation points Microsoft Employee Moderator
2023-04-10T23:39:42.3233333+00:00 Hello JF, I am checking to see if you got a chance to look into my above response.
-
JF 96 Reputation points
2023-04-11T07:32:22.93+00:00 I have tried from a different browser and in incognito mode, but this did not resolve the issue. We will contact our Microsoft support colleagues to see whether they can remove the custom scan rule set from the backend. If needed, I will come back to you. Thank you for your feedback!
-
Bhargava-MSFT 31,356 Reputation points Microsoft Employee Moderator
2023-04-11T16:57:01.4533333+00:00 Hello JF, Thank you for the update. In case if you need any further assistance from my end, please feel free to reach out to me on this thread.
Sign in to comment
Sign in to answer