Impact of deleting Microsoft Purview account on access policies
Deleting a Microsoft Purview account that has active (that is, published) policies will remove those policies. This means that the access to data sources or datasets that was previously provisioned via those policies will also be removed. This can lead to outages, that is, users or groups in your organization not able to access critical data. Review the decision to delete the Microsoft Purview account with the people in Policy Author role at root collection level before proceeding. To find out who holds that role in the Microsoft Purview account, review the section on managing role assignments in this guide.
Before deleting the Microsoft Purview account, it's advisable that you provision access to the users in your organization that need access to datasets using an alternate mechanism or a different Purview account. Then orderly delete or unpublish any active policies
- Deleting DevOps policies - You'll need to delete DevOps policies for them to be unpublished.
- Unpublishing Data Owner policies.
- Deleting Self-service access policies - You'll need to delete Self-service access policies for them to be unpublished.
Check these concept guides