OneDrive for Business Word AutoSave opens read-only for policy documents: Fix Guide

When you open a policy document stored in OneDrive for Business, Word shows the file as read-only and AutoSave is disabled. This happens even when you have edit permissions. The root cause is usually a conflict between the document’s sensitivity label and the default AutoSave behavior for protected files. This guide explains why AutoSave turns off for policy documents and provides the steps to restore full editing and AutoSave functionality.

Why AutoSave Opens Policy Documents as Read-Only

Policy documents in OneDrive for Business are often protected by Microsoft Purview Information Protection sensitivity labels. These labels can apply encryption, watermarking, or header/footer restrictions. When a label includes encryption that restricts editing or printing, Word disables AutoSave by default. The application does this to prevent data loss or unauthorized changes during sync conflicts.

Another common cause is the document containing legacy metadata or embedded objects that conflict with the label’s protection. For example, a document with an older rights management template may appear read-only even if the label itself allows editing. Word checks the file’s protection status before enabling AutoSave, and any inconsistency forces read-only mode.

A third factor is the OneDrive sync engine version. Older sync engines do not support co-authoring on files with sensitivity labels. If the sync client is outdated, Word treats the file as a local copy and disables AutoSave to avoid sync conflicts.

How Sensitivity Labels Interact with AutoSave

Sensitivity labels can be configured with user-defined permissions or predefined permission sets. Labels that use the “Do Not Forward” or “Encrypt-Only” templates automatically disable co-authoring and AutoSave. Only labels configured with the “Allow co-authoring for encrypted documents” option enable AutoSave. This setting is available only in Microsoft 365 E5 or A5 plans.

Steps to Restore AutoSave Editing for Policy Documents

The following steps address the three main causes. Perform them in order until the document opens with AutoSave enabled.

1. Check the sensitivity label on the document
   Open the policy document in Word. Go to the Home tab and look at the Sensitivity button in the ribbon. Click it to see the applied label. If the label shows “Encrypted” or “Do Not Forward,” AutoSave will not work. Ask your IT admin to apply a label that allows co-authoring.
2. Remove hidden metadata with Document Inspector
   In Word, go to File > Info > Check for Issues > Inspect Document. Run the inspection. Remove any items found, especially hidden text, document properties, and custom XML data. Save the file. This can resolve false triggers that make Word think the file is incompatible with AutoSave.
3. Update the OneDrive sync app
   Right-click the OneDrive cloud icon in the system tray. Select Settings > About. Note the version number. Go to onedrive.com/download and download the latest sync client. Run the installer. After the update, restart your computer. An updated sync client supports AutoSave for sensitivity-labeled files.
4. Enable the modern sync engine for Office
   Right-click the OneDrive cloud icon and select Settings. Go to the Office tab. Under “Use Office 2016 or later to sync,” make sure the checkbox is selected. This forces OneDrive to use the sync engine that supports co-authoring and AutoSave on protected documents.
5. Remove and re-add the document to OneDrive
   Move the policy document out of the OneDrive folder to your desktop. Wait for the sync to remove it from the cloud. Move it back into the OneDrive folder. This resets any cached protection state that may be causing the read-only issue.
6. Test with a new document
   Create a new Word document in the same OneDrive folder. Apply the same sensitivity label. Save and close. Reopen the document. If AutoSave is active, the issue is specific to the original policy document. If AutoSave is still disabled, the label itself is the cause.

If AutoSave Still Shows Read-Only After the Main Fix

Word shows “Upload Failed” or “Sync Pending”

This indicates a connectivity issue between Word and OneDrive. Close Word. Open the OneDrive folder in File Explorer. Look for a red X or yellow triangle on the file. Right-click the file and select “Resolve conflict.” Follow the prompts. If the icon remains, pause and resume OneDrive sync from the system tray menu.

AutoSave is greyed out even for non-policy documents

This is a broader Word or OneDrive configuration issue. Go to Word > File > Options > Save. Ensure “AutoSave files stored in the cloud by default in Word” is checked. Also check that the document is saved to a OneDrive location, not a local folder or a SharePoint site that is not synced with OneDrive.

The sensitivity label cannot be changed by the user

If the label is locked by your organization, you cannot enable AutoSave yourself. Contact your IT administrator. Ask them to create a new label or modify the existing one to include the “Allow co-authoring for encrypted documents” option. This option requires Microsoft 365 E5 or A5 licensing.

AutoSave Enabled vs AutoSave Disabled for Policy Documents

Item	AutoSave Enabled	AutoSave Disabled
File opens in Word	Editable with AutoSave active	Read-only with AutoSave greyed out
Sensitivity label type	Label with co-authoring allowed	Label with “Do Not Forward” or “Encrypt-Only”
OneDrive sync engine	Modern sync engine version 19.192 or later	Legacy sync engine or no update
Document metadata	Clean, no hidden items	Contains hidden metadata or custom XML
Co-authoring	Supported for multiple users	Not supported

After applying the steps above, you can open policy documents in Word with AutoSave active. Start by checking the sensitivity label and removing hidden metadata. If the issue persists, update the OneDrive sync app and enable the modern sync engine. For labels that block co-authoring, work with your IT administrator to adjust the label configuration. A quick way to test AutoSave is to create a new document in the same folder and apply the same label. If the new document works, the original file likely has corrupted metadata that requires Document Inspector.