I am trying to run a Purview Scan from self managed runtime to Azure File and it is consistently failing. Unfortunately, there is not much help (logs) from the platform (Purview) other than a correlation id!
Both the Blob and File share in the same storage account. I can get to scan the blob successfully using Service Principal.
As of now, you can't use anything but storage account key as credential to scan Azure File! I did configure the credential in Key Vault and granted Purview MSI (and Service Principal) access to read the secrets. However, I haven't have a success to scan Azure File. Any reason why Purview scanner is failing? Also, any clue where to look for debugging logs in Purview platform?
AWS S3 data source scan is consistently failing. I have the latest version of Self Hosted Runtime. Tried to use Azure Managed Runtime but none is working.