Microsoft Purview: Failure deleting a Collection

Anna Dabrowski 6 Reputation points
2022-07-18T21:27:41.297+00:00

I am testing Collection structures in Microsoft Purview, this includes using the functionality for adding and deleting Collections. I have deleted all the Assets from a Collection that I would like to remove, it also has no associated Sources. However, I am unable to delete the Collection, and encounter the following message: "Request failed with status code 409 The collection [collection name] is being referenced by other resources and can't be deleted."

There is no additional information provided about which "resources" reference this collection. How can I investigate which other resources reference this Collection in order to remove the references and enable deletion?

Please also note: This Collection has no sub-Collections. I also deleted the Source that had been registered and whose Assets were previously scanned into this Collection. I haven't found a way to use the Governance Portal in order to investigate if Scans somehow continue to exist after a Source is removed and all its Assets are deleted. ("You can delete a collection if it does not have any assets, associated scans, data sources or child collections." from: https://video2.skills-academy.com/en-us/azure/purview/concept-best-practices-collections)

Thank you.

Microsoft Purview
Microsoft Purview
A Microsoft data governance service that helps manage and govern on-premises, multicloud, and software-as-a-service data. Previously known as Azure Purview.
1,020 questions

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anna Dabrowski 6 Reputation points
    2022-08-01T15:56:20.58+00:00

    Hello,

    It may be better for you to get the details internally, since details of how the fix was implemented were not shared with me.

    To the best of my knowledge, a delete operation that I had tried to perform on a Data Source within the Governance Portal interface wasn't completed on the backend (they "found user sent the request to delete this data source", which for some reason still existed). I no longer saw the Data Source in the interface and was unaware it hadn't actually been deleted. However, it still existed and referenced the Collection I was trying to delete.

    The solution was that Microsoft staff had to investigate and identify that the Source still existed, and then delete it.

    0 comments
  2. Johnny Tao 0 Reputation points
    2024-06-18T00:13:50.71+00:00

    Hi,

    I have the same problem today.

    Request failed with status code 409 Request ID: ... [collection name] (ul34hz) is being referenced by assets and can't be deleted. Surely no assets are attached to it.

    User's image

    0 comments
  3. Mariusz Pyśk 0 Reputation points
    2024-06-19T09:44:56.56+00:00

    I have the same issue today so it seems it can be reproduced.

    0 comments
  4. Mariusz Pysk 0 Reputation points
    2024-06-25T14:54:15.2266667+00:00

    Hi
    I've contacted with Microsoft support which helped me with this issue.

    It turned out collection contained zero-size assets, which were not deleted when I've deleted scan.

    To find and delete such objects, I've followed these steps:

    1. Open Purview: https://purview.microsoft.com/
    2. Once it opens, URL includes tid: https://purview.microsoft.com/home?tid=1234a123-1aef-123a-a123-1d12345678be
    3. At the end of the url add parameter: &feature.ext.catalog={"enableToggleEmptyFile":"true"} this option allows to show or hide empty files (zero size files), url after modification will lok like:

    https://purview.microsoft.com/home?tid=1234a123-1aef-123a-a123-1d12345678be&feature.ext.catalog={"enableToggleEmptyFile":"true"}

    1. In the search text box on te top of the screen put ***** (star) and confirm by enter - it will search for all files
    2. Click "View all in Data Catalog" on the right
    3. Switch off "Hide zero-size file" option
    4. Select collection in the filters to display assets related to the problematic collection
    5. delete zero size assets
    6. Delete collection

    I hope this solution can help if anybody have the same issue.

    0 comments