'Azure Purview Scan Fails on Azure File

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.

Purview Azure File Scans Fail

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?

Scan details with very little info on error!

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.

enter image description here

azureazure-filesazure-purview


Solution 1:[1]

I just performed using manage identity, It’s working fine for me. you can follow below steps:

First, go to Azure purview studio -> Data map -> Register blob storage -> then go to blob storage as shown in the below image assign roles to blob storage. Now in Azure Purview perform a scan.

Ref1 Ref2 Ref3 Ref4 Ref5 Ref6

Reference:

https://docs.microsoft.com/en-us/azure/purview/quickstart-create-collection

https://docs.microsoft.com/en-us/azure/purview/troubleshoot-connections

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source
Solution 1 BhanunagasaiVamsi-MT

Related Questions