A unified data governance solution that helps manage, protect, and discover data across your organization
Deleting the scan or re-registering the SAP S/4HANA source will not remove the assets that have already been ingested into Microsoft Purview. As documented in the SAP S/4HANA connector documentation:
"Deleting your scan does not delete catalog assets created from previous scans."
Additionally, SAP S/4HANA currently does not support automatic deletion detection, so if objects are deleted from the SAP source, a subsequent scan will not automatically remove the corresponding assets from Microsoft Purview.
For your scenario of approximately 1.6 million assets:
If all SAP assets are organized under a common parent asset in the catalog hierarchy, deleting the parent asset will also delete all of its child assets.
For a cleanup of this scale, deleting assets individually through the portal is not practical. Using the Microsoft Purview Data Map (Apache Atlas) REST APIs to perform a bulk deletion of the catalog assets is the most practical approach.
After confirming that the assets have been removed from the catalog, you can re-register the SAP S/4HANA source (if required) and run a new Full Scan to rebuild the metadata.
Microsoft documentation:
- https://learn.microsoft.com/purview/register-scan-saps4hana-source
- https://learn.microsoft.com/purview/legacy/classic-catalog-asset-details#delete-asset
- https://learn.microsoft.com/purview/data-map-scan-ingestion
- https://learn.microsoft.com/azure/purview/tutorial-using-rest-apis
If you can confirm whether all 1.6 million assets belong to a single SAP S/4HANA registered source/collection, we can advise whether deleting the parent asset is sufficient or whether a bulk API-based cleanup is required.