Pinned Posts
Forum Widgets
Latest Discussions
eDiscovery case (Premium) and on-premise file share content
We have E5 license and Purview eDiscovery premium. We have a need to create eDiscovery case with on-premise file share data source. As part of this configuration, we have done the following: Installed a graph connector agent on the on-premise file share with azure app registration with the appropriate permissions. In Microsoft 365 admin center, configured file share data source linking to file share graph connector above. The files on the file server were successfully indexed. No issues. However, in the next step, while creating an eDiscovery case (Premium), we don't see "Add Graph Connector as a data source within a case" to add the above graph connector. What are we missing? The user has Global Administrator permissions.
Lineage scenario between Synapse pipeline and Purview failing
I'm currently testing a lineage scenario between a Synapse pipeline and Purview. I used the Lab 22 to test this scenario 'Use Microsoft Purview with Azure Synapse Analytics': https://microsoftlearning.github.io/dp-203-azure-data-engineer/Instructions/Labs/22-Synapse-purview.html#integrate-microsoft-purview-with-azure-synapse-analytics Everything works fine, data are copied, except the lineage scenario which failed with the following error: "The catalog provided for lineage reporting cannot be connected, please check the catalog uri and network connection." Screenshot below: Questions: 1. As Synpase seems to be correctly connected to Purview, in order to troubleshoot this error, is there a way to get further information like stack trace in the Synapse logs? 2. Should the Purview Account and Synapse Workspace be deployed in the same Azure Region? 3. Is Lineage scenario between Synapse and Purview still supported with the latest Purview version? 4. Could you share a sample where the Lineage Scenario between Synapse and Purview works? Thanks for your help, Fred
eDiscovery for email attachment with encrypted sensitivity labels
We are currently testing encrypted sensitivity labels in conjunction with eDiscovery. We applied an encrypted label to a document, and eDiscovery was able to successfully search for the content in both OneDrive and SharePoint. However, the same functionality does not appear to work for email attachments—the content of encrypted attachments is not searchable. Are there any specific settings or configurations that need to be enabled to support encrypted email attachments in eDiscovery? Thanks
