Data Protection Issues

How to Stop Microsoft Purview Labels from Encrypting Automated Word Emails

Maira Mehtab Sep 22, 2026 869 views

Question details

Users need to stop Microsoft Purview sensitivity labels from automatically encrypting the notification emails triggered by comments and @mentions in Word documents.

Product: Microsoft Word, Microsoft Purview
Device & OS: not provided
Scenario: A user is attempting to rely on automated email notifications for Word document comments and mentions, but the emails are being encrypted by compliance policies.
Observed behavior: Normal automated message notifications are replaced with protected-message notices due to automatic sensitivity label encryption applied by Microsoft Purview.

Before you start

Ensure you have Global Administrator or Compliance Administrator permissions in your Microsoft 365 tenant to modify Purview sensitivity labels and policies.

Solution 1Recommended

Review and Adjust Purview Label Encryption Settings

Check your current automatic labeling and encryption configurations in the Purview portal to ensure they exclude system-generated notifications.

Microsoft Purview labels configured to apply encryption automatically can inadvertently encrypt system-generated emails, such as those triggered by @mentions in Microsoft Word. Adjusting the label policies in a test environment can help identify and resolve the conflict.

Access the Compliance Portal

Log in to the Microsoft Purview compliance portal using your administrator credentials and navigate to the Information Protection section.

Edit the Sensitivity Label

Select the 'Labels' tab, locate the specific sensitivity label causing the encryption, and click 'Edit label'.

Modify Encryption Scope

Navigate to the 'Encryption' settings and review the configuration. Ensure that the scope or auto-labeling conditions do not inadvertently encompass automated service emails.

Test the Configuration

Publish the adjusted label policy to a dedicated test group or test environment to verify that Word comment notifications are no longer encrypted before deploying it tenant-wide.

Testing Environment: Always validate compliance and encryption policy changes in a test environment first to prevent accidental disruptions to your organization's data protection workflows.

Solution 2

Open a Support Ticket with Microsoft Support

If adjusting the policies does not resolve the issue, specialized tenant-level troubleshooting from Microsoft is required.

Free Microsoft Office alternative

Try WPS Office for a Hassle-Free Document Collaboration Experience

If complex Microsoft Purview compliance settings and automated email encryptions are complicating your team's workflow, consider switching to WPS Office. It provides a lightweight, highly compatible alternative without the heavy enterprise administrative overhead.

1. Download WPS Office: Visit the official WPS Office website and download the free installer for your operating system.
2. Install the Application: Run the setup file and follow the on-screen instructions to complete the installation.
3. Collaborate Seamlessly: Open your existing Word documents directly in WPS Office and use the native commenting and sharing features without worrying about complex background encryption policies.

Seamless compatibility with Microsoft Word (.docx) formats.Lightweight interface without complex tenant-level compliance setups.Built-in collaboration tools for efficient team commenting and sharing.Free to use with powerful document processing capabilities.

microsoft office alternative - wps office

Frequently Asked Questions

Why do Word comment mentions show up as protected messages in my email?

If your organization uses Microsoft Purview, automated emails triggered by @mentions in Word may inherit the document's sensitivity label, causing the email server to automatically encrypt the notification message.

Can I disable encryption for automated Word emails only?

Yes, but it requires an administrator. They may need to adjust the auto-labeling policies in the Microsoft Purview compliance portal or configure transport rules in the Exchange Admin Center to bypass encryption for specific system-generated sender addresses.

Do I need admin rights to fix Purview label encryption issues?

Yes, modifying Microsoft Purview sensitivity labels and encryption policies requires Compliance Administrator or Global Administrator privileges in your Microsoft 365 tenant.

Microsoft Office Security Issues