Blogs by Ashwin

  Recommended Practices In order to reduce the number of errors related to eDiscovery holds, the following practices are recommended:  If a hold distribution is still pending, with a status of either On (either) or Off (Pending), wait until the hold distribution is complete before you make any further updates. Check whether a hold policy is pending before you make any further updates to it.  Merge your updates to an eDiscovery hold in a single bulk request rather than updating the hold policy repeatedly for each transaction. Error: PolicySyncTimeout If this error appear in the ResultCode: PolicySyncTimeout, then check the LastResultTime to see if it is longer than two hours since the sync reached the time-out.  Resolution Run the Set-CaseHoldPolicy -Identity "policyname" -RetryDistribution command to resolve the issue. Also in the case hold page in the Microsoft Purview portal, select Retry to redeploy the policy. Error: PolicyNotifyError If you see this error in the...

  Introduction  If you face a problem or error concerning searches in Microsoft Purview eDiscovery (Standard), attempt operation again to eliminate temporary issues. If the suggested solutions do not resolve your search problem, reach out to Microsoft Support. Based on your specific issue, collect output using the Get-ComplianceSearch or Get-ComplianceSearchAction PowerShell cmdlet prior to submitting a support request.  Search Issue: Difference Between Estimated and Downloaded Search Results Symptoms The estimated and downloaded search result statistics are different when you see the search result statistics in the Expert Summary <timestamp>.csv file in the downloaded eDiscovery search results folder. Both the eDiscovery export tool and the search details pane in the Microsoft Purview compliance portal display the estimated search result statistics.  Cause A search result estimate is just an estimate and does not represent the precise number of items that sati...

  Symptoms Depending on the situation, you may encounter the following error message when attempting to use Exchange Admin Center (EAC) on the on-premises server to conduct In-Place eDiscovery searches in Microsoft Exchange Server 2019 or 2016 for cloud-based mailboxes in a Microsoft Exchange hybrid deployment environment: Scenario 1 You are trying to search a remote mailbox that doesn't have an online archive enabled. In this scenario, an error message resembling the following will appear- Export failed with error type: 'FailedToSearchMailboxes'. Details: The underlying connection was closed: An unexpected error occurred on a receive. Endpoint: https://mail.contoso.com:444/EWS/Exchange.asmx Scenario 2 You are trying to search a remote mailbox that has an online archive enabled. The estimate of search results succeeds. However, when you try to copy the results to a discovery mailbox, the attempt fails and returns an error message resembling the following- Failed Search or E...

  Introduction If you experience a problem concerning Microsoft Purview Data Loss Prevention (DLP) policy tips, initiate an automated diagnostic for DLP policy tips within the Microsoft 365 admin center. The diagnostic evaluates the configuration of DLP policies and rules for policy tips, highlights any issue found, and provides recommendations for solutions.  Run Diagnostic For DLP Policy Tips To run the diagnostic: Select "Run Tests: DLP policy tips" button to open the diagnostic in the Microsoft 365 admin center. Enter the below information- User Principal Name (UPN) or email address of the user. DLP rule name or GUID. Outlook or OWA (Outlook on the web)       3. Go for Run Tests button. DLP Policies in Exchange Online DLP policies are where DLP policy tip settings are set up. Due to the deprecation of old Exchange Online Data Loss Prevention policies in the Exchange admin center, it is recommended to move any DLP polices you generated in Exchange Online to t...

  Introduction The PowerShell Gallery hosts the ComplianceDiagnostics tool, which is a PowerShell module. The program offers a number of data gathering templates from which you can choose. What diagnostic information is collected depends on your choice. Usually, a Microsoft Support engineer instructs you on which data collection template to utilize and requests diagnostic data. Prerequisites In order to use the ComplianceDiagnostics tool, ensure that your environment meets the following requirements: Installed PowerShell 5.0 or its latest version. Installed ExchangeOnlineManagement module 3.0 or a later version. The PowerShell Gallery should be in the list of PowerShell repositories on your local computer. You should be a Compliance administrator in Microsoft Purview.  PowerShell execution policy should be set to RemoteSigned.  Install Tool Install the latest version of the ComplianceDiagnostics tool by running the following cmdlet: Install-Module ComplianceDiagnostics -F...