Compliance Problems

How Long Does It Take to Enable Co-Authoring for Encrypted Excel Files?

Maira Mehtab Oct 1, 2026 869 views

Question details

The user needs to know if a 24-hour waiting period applies when enabling co-authoring features for Excel files that are encrypted using Microsoft Purview sensitivity labels.

How Long Does It Take to Enable Co-Authoring for Encrypted Excel Files?

Product: Microsoft Excel / Microsoft Purview
Device & OS: not provided
Scenario: An administrator or user is attempting to enable multiple-user editing (co-authoring) on enterprise documents protected by sensitivity labels.
Observed behavior: Co-authoring may not be immediately available after turning on the feature, prompting the user to question the required backend synchronization time.

Before you start

Ensure you have global administrator or compliance administrator permissions in your Microsoft 365 tenant before attempting to modify Microsoft Purview sensitivity label settings.

Solution 1Recommended

Verify Purview Configuration and Propagation Time

Confirm your Microsoft Purview tenant settings and allow adequate time for the backend deployment to synchronize across all services.

Enabling co-authoring for documents protected by sensitivity labels is a tenant-wide configuration in Microsoft Purview. When you activate this setting, it requires background synchronization across Microsoft 365 services, endpoints, and user accounts. It is standard for this propagation process to take up to 24 hours to fully complete.

Access the Compliance Portal

Navigate to Co-authoring Settings

Go to the Settings menu and select 'Co-authoring for files with sensitivity labels'.

Enable the Feature

Toggle the setting to turn on co-authoring for encrypted documents if it is not already activated.

Wait for Synchronization

Allow up to 24 hours for the configuration changes to deploy and take effect across your organization's Excel desktop and web applications.

Verify Purview Configuration and Propagation Time

Enterprise Deployment: During the 24-hour window, some users might still experience file locks or read-only prompts when opening encrypted files.

Solution 2

Consult Microsoft Learn Specialists

Seek assistance from specialized Microsoft Purview engineers if co-authoring remains unavailable after the 24-hour waiting period.

Free Microsoft Office alternative

Try WPS Office for Seamless and Secure Collaboration

While Microsoft Purview configurations require complex tenant administration and extended waiting periods, WPS Office offers a lightweight, highly compatible alternative. It provides straightforward cloud-based collaboration without the heavy enterprise configuration overhead.

1. Download and Install: Visit the official WPS Office website to download and install the software.
2. Upload to WPS Cloud: Save your spreadsheet to WPS Cloud to instantly unlock multi-user sharing capabilities.
3. Invite Collaborators: Click 'Share' to generate a collaboration link and easily invite colleagues to edit the file in real-time.

Completely free, lightweight, and easy to deploy across teamsHigh compatibility with Microsoft Excel (.xlsx) and other standard formatsBuilt-in WPS Cloud support for real-time spreadsheet co-authoringFamiliar user interface requiring no extensive retraining

microsoft office alternative - wps office

Frequently Asked Questions

Why can't I co-author an encrypted Excel file immediately after turning the setting on?

Co-authoring for encrypted files relies on Microsoft Purview sensitivity labels. Modifying this setting at the tenant level requires extensive backend synchronization across all Microsoft 365 services and endpoints, which typically takes up to 24 hours to complete.

Does WPS Office support real-time co-authoring for spreadsheets?

Yes, WPS Office supports real-time collaboration. By saving your standard spreadsheets to WPS Cloud, multiple users can view and edit the same document simultaneously without needing complex enterprise compliance configurations.

Who has the authority to enable co-authoring for sensitivity labels?

Only IT administrators assigned with global admin or compliance admin roles in the Microsoft 365 admin center have the required permissions to modify Microsoft Purview compliance settings.

What happens if a user tries to edit the encrypted file before the propagation finishes?

If backend synchronization is incomplete, users attempting to open the encrypted file may encounter file-lock errors or be restricted to read-only access until the changes fully deploy.

Microsoft Office Security Issues