Hi
Thank you for posting query in Microsoft Q&A Platform.
It seems like you are experiencing an internal system error while scanning sources in Purview. There could be several reasons why this is happening. One possible reason is that there might be an issue with the credentials you are using to authenticate the scan.
To troubleshoot this issue, you can follow these steps:
- Verify that you have followed all prerequisite and authentication steps for the source you are connecting to. You can find all available sources listed in the Microsoft Purview supported sources article.
- Check the error message first to see the failure details. This will give you a better idea of what might be causing the issue.
- Have credentials to your resource changed or been rotated? If so, you'll need to update to make your scan use the correct credentials.
- Is an Azure Policy preventing updates to Storage accounts? If so follow the Microsoft Purview exception tag guide to create an exception for Microsoft Purview accounts.
- Are you using a self-hosted integration runtime? Check that it's up to date with the latest software and that it's connected to your network.