Purview error when scanning Azure File

[aspnet4you]

I setup Purview with private endpoint as documented at the link below. All setup seems to be working with private Endpoints for account, portal and injestion. Also, setup a Self Hosted Runtime.
https://docs.microsoft.com/en-us/azure/purview/concept-best-practices-network#option-2-use-private-endpoints

Now, 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 are 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! Registration is able to discover the folders and files in Azure File share. 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?

Related post at Stackoverflow

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 2aaa823b-dd5a-39f2-760b-1ba15e81554c
• Version Independent ID: bd72379d-f2ff-7795-0a74-bebd66167713
• Content: Connect to and manage Azure Files - Microsoft Purview
• Content Source: articles/purview/register-scan-azure-files-storage-source.md
• Service: purview
• Sub-service: purview-data-map
• GitHub Login: @viseshag
• Microsoft Alias: viseshag

[shashishailaj]

@aspnet4you
Thank you for your feedback . We will investigate and update the thread.

[aspnet4you]

Same issue with scanning AWS S3. I have the proper IAM role with policy and Purview can read the metadata validated by Test Connection. Unfortunately, S3 scan always fails without much details in the error message!

Also, it takes way long time to scan Kilobytes and Megabytes of S3 buckets. Is Purview is really ready for prime time?

[CHEEKATLAPRADEEP-MSFT]

@aspnet4you Since this issue is not related directly to the doc, I would recommend you to create a thread on the forums - Microsoft Q&A or Stack Overflow
Once you post your issue on forums, it will have visibility across the community which is a better suited audience for such types of issues.