Blogs by Ashwin

  About If you are experiencing problems with the Microsoft Purview Information Protection scanner, check the health of your deployment by utilizing the Start-ScannerDiagnosticsPowerShell cmdlet to start the scanner diagnostic tool. The diagnostics tool checks the following details and then creates a log files with the results: Whether the database is up to date. Whether network URLs are accessible. Whether there's a valid authentication token and policy can be acquired. Whether the profile is defined in the Azure portal. Whether offline/online configuration exists and can be acquired. Whether the rules configured are valid.  The Start-ScannerDiagnostics command does not perform a comprehensive check of prerequisites. If you encounter problems with the scanner, you need to verify that your system meets the scanner's requirements, and that your scanner's configuration and installation are finished.  Verify Scanning Details Per Scanner Node and Repository Run the Get-ScanSt...

  Introduction Microsoft Purview Information Barriers can aid your organization in adhering to legal obligations and industry standards. For instance, you can implement information barriers to limit interactions between certain user groups to prevent any potential conflicts of interest.  Issue: Users are unexpectedly blocked from communicating with others in Teams Users report unexpected issues when they try to communicate with others via Microsoft Teams like- A user searches for, but can't find, another user in Teams. A user can find, but can't select, another user in Teams. A user can see another user but can't send messages to that user in Teams. What To Do? Assess whether the users are influenced by an Information Barriers policy. Based on how these policies are set up, information barriers may be functioning correctly. Alternatively, you may need to adjust your organization's policies.  Use the Get-InformationBarrierRecipientStatus cmdlet together with the Identity...

  Symptoms When you transfer a mailbox from an on-premises Exchange setup to Exchange Online within a hybrid deployment, the retention policy associated with that mailbox ceases to function. You may encounter this problem despite having completed one or both of the actions listed below: You recreated the retention policy and assigned it to the mailbox. You recreated the retention tag and included it in the retention policy. Cause Retention hold has been activated on the mailbox. Typically, retention hold is automatically activated when a mailbox transitions from the on-premises environment to Exchange Online. When a mailbox is under retention hold, the application of the retention policy for that mailbox is halted. To verify that retention hold is enabled on a mailbox, follow these steps: Connect to Exchange Online by using remote PowerShell. Run the command- Get-mailbox user@contoso.com |fl Examine the output. If the RetentionHoldEnabled parameter is set to True, retention hold is...

  Process In an Exchange Hybrid Deployment With or Without On-Premises Microsoft Lync Server 2013 Restore In-Place Hold Settings In order to restore In-Place Hold settings: Open the Exchange Admin Center via on-premises admin credentials on the Exchange Server. If your organization is enabled for a hybrid deployment with Microsoft Exchange Online in Microsoft 365, click the Enterprise tab in the navigation bar. First select Compliance Management and then in-place eDiscovery & hold. To enter the properties page, double-click the In-Place Hold entry you wish to restore In-Place Hold settings for, or select Edit.  Then select In-Place Hold from the properties page. The user's In-Place Hold settings are shown. Click the Save button after clearing the Place content matching the search query in selected mailboxes on hold check box.  Click the In-Place Hold after reopening the same properties page. You can see that the check box for Place content matching the search query in...

  Symptoms The following scenarios might happen: A user is a mailbox in Microsoft 365. In-place hold or litigation hold is enabled for the mailbox.  The user tries to edit calendar items from Microsoft Outlook Web App (OWA) or Microsoft Outlook.  In these scenarios, the user receives the following error message: Couldn't update the following event- <EventName> Cause This issue occurs because the Versions folder (that is part of the Recoverable Items folder) is full. To check the Recoverable Items folder statistics- Get-MailboxFolderStatistics -Identity cloudtest -FolderScope recoverableitems  | ft name, *size* Resolution Since the user's mailbox is currently on hold, the contents of the Versions folder hold great significance. To address this situation, it is necessary to activate the archive mailbox for the user in question, and subsequently transfer all items from the Versions folder into the archive mailbox. To do this, follow these steps: Enable the archive...

  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...