Permission & Access Issues

Fix AutoSave and Collaboration for Encrypted Office Documents

Huma Ashraf ChHuma Ashraf Ch Oct 21, 2026 869 views

Question details

The user needs to restore AutoSave and simultaneous editing functionality for Office documents protected by Azure Information Protection labels.

Fix AutoSave and Collaboration for Encrypted Office Documents
Product
Microsoft 365
Device & OS
not provided
Scenario
Attempting to co-author and use AutoSave on documents encrypted with Azure Information Protection (AIP) labels after collaboration was enabled in Microsoft Purview.
Observed behavior
AutoSave and simultaneous editing (co-authoring) remain disabled or fail to function properly despite enabling the collaboration feature in the Purview portal.
Before you start

Verify that you are logged into your Office applications with the correct Microsoft 365 business account and ensure your Office clients are updated to the latest version.

Solution 1Recommended

Contact Your Microsoft 365 Administrator for Support

This issue requires backend investigation of your tenant and sensitivity label policies, which can only be performed by a Microsoft 365 administrator.

Standard troubleshooting steps and forum support lack the necessary backend permissions to resolve advanced Microsoft Purview and Azure Information Protection label issues.

A Microsoft 365 administrator has the access required to inspect your tenant, sensitivity label policies, user permissions, and Office client configurations directly.

1
Identify your administrator

If you do not know who your IT admin is, check with your IT department or refer to the official Microsoft guide on finding your Microsoft 365 administrator.

2
Request a support ticket

Ask your administrator to log into the Microsoft 365 Admin Center and create a formal support request through the 'Help & Support' section.

3
Investigate sensitivity policies

Instruct the admin or Microsoft Support team to examine the sensitivity label policies and ensure that 'co-authoring for files with sensitivity labels' is fully synced and enabled across the tenant.

Contact Your Microsoft 365 Administrator for Support
Administrative Access Required: Only users with administrative privileges can open backend support tickets for Microsoft Purview and Azure Information Protection synchronization issues.
Free Microsoft Office alternative

Try WPS Office for Seamless Document Collaboration

If you frequently encounter complex permission issues and backend syncing errors with Microsoft 365, consider switching to WPS Office. It provides a lightweight, highly compatible alternative with built-in cloud collaboration and file protection features without the heavy administrative overhead.

  1. 1. Download and install: Visit the official WPS Office website and download the free suite for your operating system.
  2. 2. Open your documents: Launch WPS Office and open your existing Microsoft Office files. WPS supports direct editing of .docx, .xlsx, and .pptx formats seamlessly.
  3. 3. Collaborate effortlessly: Save your document to WPS Cloud to instantly enable real-time co-authoring and auto-saving with your team.
Fully compatible with Microsoft Word, Excel, and PowerPoint file formats (.docx, .xlsx, .pptx).Free and lightweight suite with a familiar user interface for an easy, seamless transition.Built-in robust cloud collaboration features for real-time simultaneous editing and automatic saving.Easy-to-use document encryption and permission management without complex backend setups.
microsoft office alternative - wps office

Frequently Asked Questions

Why is AutoSave disabled when I apply a sensitivity label?

AutoSave may be disabled if the sensitivity label applies encryption and the Microsoft 365 tenant has not fully configured the 'co-authoring for files with sensitivity labels' feature in the Microsoft Purview compliance portal.

Can I fix the Azure Information Protection collaboration issue myself?

Generally, no. This issue requires administrative access to the Microsoft 365 Admin Center to inspect tenant-level policies, backend permissions, and Office client configurations. You must contact your IT administrator.

Does enabling collaboration in Microsoft Purview take effect immediately?

No, after an administrator enables co-authoring for files with sensitivity labels, it can take up to 24 hours for the backend changes to sync and take effect across all Office clients and the entire tenant.