Pinned Posts
Forum Widgets
Latest Discussions
9M365PurvieweDiscoveryInfra touching files in office activity logs
Hi, We use Office Activity Logs through Log Analytics Workspace to report on specific files. We noticed that in our most recent report, many files were accessed by 'ExportWorker' with 'ClientAppName' M365PurvieweDiscoveryInfra. This seems to have happened on specific days a couple of weeks ago where the activity 'file accessed' whenever an ediscovery was run on a location that stored the particular file was registered. This was not the case before if I remember correctly. Does anyone know why this activity was registered as such in the logs and/or has also experienced the exportworker of M365PurvieweDiscoveryInfra touch their files when running an ediscovery? Is this a change with the new eDiscovery? It is also undesirable that users can track incident response employees touching their files in case of an investigation.
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
