Purview Self-serve analytics does not upload the data to storage

Radosław Kamiński 0 Reputation points
2025-01-13T11:20:08.8+00:00

Hello,

I have a problem with self-serve analytics setup in Purview. I configured this feature to export the data to ADLS Storage Gen2 (Settings -> Unified catalog -> Solution integrations). Connection test is successfull, managed identity that I'm using has a Storage Blob Data Contributor role assigned but no data is exported and storage remains empty.

I'm not able to see any errors or logs in purview and there is no notification that the data export failed.

Does any know how to make this work?

Microsoft Purview
Microsoft Purview
A Microsoft data governance service that helps manage and govern on-premises, multicloud, and software-as-a-service data. Previously known as Azure Purview.
1,360 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Chandra Boorla 7,335 Reputation points Microsoft Vendor
    2025-01-20T19:50:02.8533333+00:00

    @Radosław Kamiński

    Thank you for providing the additional details. Since you've followed all steps, including creating a new ADLS storage account with public network access enabled, and still face issues with data export from Purview, here are some additional steps to consider:

    Verify Storage Account Configuration - Ensure that the new ADLS storage account is correctly configured to allow exports from Purview. Check if there are any specific policies or restrictions applied at the container level that might prevent data from being written.

    Check Purview Export Jobs - Navigate to Monitoring > Export Jobs in Purview to see if there are any active or failed jobs related to the export. This will give insights into why data is not being exported.

    Azure Monitor and Logs Analysis - Use Azure Monitor and review the logs for any anomalies or errors related to data export from Purview. Ensure there are no network or permission-related errors.

    Purview Version and Updates - Ensure that both Purview and the underlying services (e.g., Azure Data Lake Storage) are up-to-date. Sometimes, updating Purview or any dependent services might resolve persistent issues.

    Retry with Different Settings - Try changing the storage container or the destination path once again. Sometimes, a fresh configuration with minor adjustments can resolve export issues.

    I hope this information helps, please do let us know if you have any further queries.

    Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.

    Thank you.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.