OneDrive Admin Checklist: Word AutoSave creates conflicts for offline edits

When users edit Word documents offline while OneDrive is disconnected, AutoSave can create file conflicts that lead to data loss or duplicate files. This happens because AutoSave tries to save every keystroke, but without a connection to OneDrive, the local version and the cloud version diverge. This article explains why offline edits trigger conflict errors, provides a step-by-step checklist for administrators to prevent and resolve these issues, and lists related failures you may encounter.

Why Word AutoSave Creates Conflicts During Offline Editing

Word AutoSave continuously writes changes to the local cache every few seconds. When the user is offline, these changes are stored in a local draft folder instead of being sent to OneDrive. When the user reconnects, OneDrive synchronizes the local file with the cloud version. If the cloud version was also edited by another user, or if the local file diverged significantly, OneDrive cannot merge the changes automatically. It then creates a conflict copy with a name like “Document (version 1).docx” or adds a “Conflicted Copy” suffix. The user must manually compare the files and decide which version to keep.

The root cause is that AutoSave does not pause when the network drops. Word continues to write changes locally, but it does not track the cloud version’s state. When OneDrive resumes syncing, it detects a mismatch and flags the file as conflicted. This is by design to prevent data corruption, but it creates confusion for users who expect a seamless merge. Administrators can reduce these conflicts by controlling AutoSave behavior, enforcing sync settings, and educating users on offline workflows.

Admin Checklist to Prevent and Resolve Word AutoSave Conflicts for Offline Edits

The following checklist is organized in order of priority. Complete each step before moving to the next.

1. Enable Known Folder Move via OneDrive admin center
   Go to the Microsoft 365 admin center > OneDrive admin center > Sync > Known Folder Move. Turn on “Move known folders to OneDrive” and apply it to all users. This ensures Desktop, Documents, and Pictures are synced before the user goes offline. Users must have OneDrive running and be connected at least once to enable offline access.
2. Configure AutoSave default in Group Policy
   Download the latest Office Administrative Templates. Open Group Policy Management Editor. Navigate to User Configuration > Policies > Administrative Templates > Microsoft Word 2016 > Word Options > Save. Set “Disable AutoSave by default” to Enabled. This prevents AutoSave from activating on new documents. Users can still turn it on manually if they prefer.
3. Disable AutoSave for OneDrive and SharePoint files via policy
   In the same Group Policy path, find “AutoSave OneDrive and SharePoint Online files by default” and set it to Disabled. This stops AutoSave from automatically saving files stored in OneDrive or SharePoint. Users will see a prompt to enable AutoSave, but it will not start automatically.
4. Set the offline sync policy to block large file sync on metered networks
   In OneDrive admin center > Sync > Device and network policies, enable “Block sync on metered networks” and “Block sync on metered networks when roaming.” This prevents OneDrive from trying to sync large files when the user is on a cellular or metered connection, reducing the chance of interrupted syncs.
5. Communicate the offline editing best practices to users
   Send a brief email or post in your internal knowledge base explaining that users should turn off AutoSave when working offline. Steps: In Word, go to File > Options > Save, and uncheck “AutoSave OneDrive and SharePoint Online files by default.” Alternatively, toggle the AutoSave switch in the top-left corner of the Word window to Off before disconnecting.
6. Monitor conflict reports in the OneDrive admin center
   Go to OneDrive admin center > Reports > Usage. Review the “Sync conflicts” metric. If the number is high, investigate which users or devices are generating conflicts. Use the per-user sync log to identify patterns.
7. Test the configuration on a pilot group
   Apply the Group Policy settings to a test group of 5 to 10 users. Monitor conflict reports for two weeks. If conflicts drop to zero, roll out the policy to all users. If conflicts persist, check for third-party sync tools that may interfere with OneDrive.

If Users Still Experience Conflicts After the Checklist

Word shows “Conflicted Copy” or “Version 1” files after offline editing

This occurs when the user did not disable AutoSave before going offline, or when the file was open on another device. Instruct the user to open both the original file and the conflicted copy side by side. Use Word’s Compare feature: Review tab > Compare > Compare. Select the original document and the conflicted copy. Word will highlight differences. The user can then merge the changes into the original and delete the conflicted copy.

OneDrive shows a red X on Word files after reconnecting

A red X means the file failed to sync. This often happens when the conflicted file exceeds the 250 MB file size limit for conflict copies. Ask the user to close Word, right-click the file in File Explorer, and select “View sync conflicts.” OneDrive will show the conflict resolution dialog. The user should choose “Keep both” or “Keep the version on this device.” After resolving, the red X should disappear.

AutoSave does not turn off even after policy change

The policy change may not apply immediately because Word caches settings. Run gpupdate /force on the user’s machine and restart Word. If the issue persists, verify that the policy is applied by opening Word, going to File > Options > Save, and checking if the AutoSave checkbox is grayed out. If it is not grayed out, the policy may be set to Not Configured. Reapply the policy and run gpupdate again.

AutoSave On vs AutoSave Off for Offline Editing: Key Differences

Item	AutoSave On	AutoSave Off
Save frequency	Every few seconds while typing	Only when the user presses Ctrl+S or clicks Save
Offline behavior	Saves to local draft, creates conflict on reconnect	Saves to local draft, syncs cleanly on reconnect
Conflict risk	High, especially for long offline sessions	Low, because the user controls when to save
User awareness	Users may not realize AutoSave is running offline	Users must remember to save manually before disconnecting
Admin control	Can be disabled via Group Policy	Default behavior when policy is applied

Word AutoSave is designed for always-on connectivity. For users who frequently work offline, disabling AutoSave is the most effective way to avoid conflicts. The checklist above gives administrators the tools to enforce this behavior at scale.