It’s apparent that Data can become orphaned in the Azure Data Lake when the Data Source object is deleted in TX. Where sensitive data is often in scope this activity critically needs an option for the TX user (who may not have direct access to the ADL) to make a decision on whether to delete that related data when removing the Data Source – perhaps opting to retain it if the Data Source is (for some reason) immediately recreated with the same naming convention (perhaps automate this to avoid human-error) and can be re-linked to the existing data.
- We’re concerned that over time an audit would find significant volumes of orphaned/uncontrolled data in the ADL, potentially exposing personally identifiable or commercially sensitive information.
How can TX help here? Is there a tool on the roadmap perhaps?
Hope you can help,