Blogs by Ashwin

  Problem When a user of Microsoft Exchange Online attempts to open a message encrypted with Microsoft Purview Message Encryption in Outlook Web App, they receive the error message: We cannot display your message at this moment. This problem happens even when user is capable of sending encrypted messages using Outlook Web App.  Cause This issue arises due to alterations in the MIME types linked to the default Outlook Web App policy, resulting in the removal or modification of the text/html MIME type.  Solution To address this issue, restore the MIME types linked to the default Outlook Web App policy to their original settings. To achieve this, follow these steps: Connect to Exchange Online via Remote PowerShell. Run the following commands: $owapolicy = Get -OwaMailboxPolicy Set -OwaMailboxPolicy -AllowedMimeTypes @{remove = "text/html"} -BlockedMimeTypes @{remove = "text/html"} -ForcedSaveMimeTypes @{add = "text/html"} -Identity $owapolicy.Identity Conclus...

  Error: Settings Not Found Symptoms While checking the details pane for a retention policy in the Microsoft Purview portal, an error message appear, "Settings not found."  Cause The retention policy has no retention rules. Resolution To resolve this issue, use either of the following methods. Method 1: Use the Microsoft Purview Portal In the Microsoft Purview portal, search for the policy on the following tabs-  Data Lifecycle Management > Microsoft 365 > Retention policies Data Lifecycle Management > Microsoft 365 > Label policies Records Management > Label policies  Select the policy, and then select Edit. In Retention settings, add rules to the retention policy. Method 2: Use PowerShell Connect to Security & Compliance PowerShell. Use the applicable cmdlet for the workload to add rules to the retention policy.   Use the New-RetentionComplianceRule cmdlet for policies that target- Microsoft Exchange Online email Microsoft SharePoint si...

  Common Causes: There are several reasons why MRM might not process a mailbox as expected. For example-  Retention hold is applied to the mailbox . In other words, the mailbox's RetentionHoldEnabled fieldis set to True. For instance, the PST Import service is used to transfer the mailbox.  The ElcProcessingDisabled attribute of the mailbox is configured to True. This configuration stops the MFA from processing the mailbox completely. The mailbox has been applied retention tag, but that tag is presently disabled. As a result, messages in the mailbox will not be achieved or removed at any time. The mailbox awaiting processing is sizeable and holds numerous items. This may result in MFA archiving or removing content at a reduced speed.  The retention policy assigned to the mailbox consists solely of personal tags. If the user fails to apply these tags manually, MRM may not manage the mailbox.  Troubleshooting Check the RetentionHoldEnabled Property of the Mailbox ...

  Introduction Mistakes in policy can happen during  during the synchronization and distribution phases in Microsoft Purview. This step is essential for enforcing policies. The method of enforcement varies based on the specific type of policy: For retention policies, the system creates rules to enforce policy settings, such as retain and delete behaviors. For published label policies, enforcement means that the system makes published labels available for use in user-defined locations. Users can then manually apply the published labels. For autoapply label policies, enforcement means that the system applies labels to content according to user-defined criteria.  Policy errors can occur in both static and adaptive scope policies.  How to Check Policy Errors? Method 1: Use the Microsoft Purview Portal In the Microsoft Purview Portal-  Navigate to Data Lifecycle Management > Microsoft 365. For every policy listed under the Retention policies tabs, click on the pol...

  Symptoms During the use of Disposition tab in Microsoft Purview Records Management in the Microsoft Purview portal to manage disposition reviews, the following message may occur: The remote server returned an error: (401) Rbac check failed. Cause This error happens when you lack the necessary permissions for disposition reviews, causing the Role-Based Access Control verification to fail. Permissions within the Microsoft Purview portal are determined by the RBAC permissions framework. Resolution Confirm that the error is a result of the RBAC check failing. Replicate the problem and collect the relevant network activity logs from Microsoft Edge. Next, review the network logs for the presence of the RBAC "401" error message. If the error message is present, ensure that you or your associated group holds membership in one of the following role groups: Content Explorer Content Viewer Content Explorer List Viewer Microsoft Purview Records Management with the Disposition Managemen...

  Symptoms Using a query that contains particular words, phrases, or values of searchable characteristics, you can set up an auto-reply retention label. But in your company, the label does not automatically apply to the items in a user's email.  Cause This issue may occur for one or both of the following reasons: The user applied a personal tag to the items that should be auto-labeled or to folders that contain the items that should be auto-labeled.  A Message Records Management (MRM) policy applied a retention policy tag to folders that contain the items to be auto-labeled.  Resolution If the user has assigned a personal tag to either the items or the folders  housing those items, eliminate the personal tag. However, if a retention policy tag form an MRM policy has been applied to the folders containing the items, discontinue the retention policy tag associated with the MRM retention policy.  Conclusion The issues related to auto-apply retention label are ...