OneDrive Admin Checklist: Word AutoSave creates conflicts for coauthoring teams

Teams that coauthor Word documents stored in OneDrive or SharePoint often see conflict messages or duplicate files when multiple people edit the same file at the same time. The root cause is usually a mismatch between Word’s AutoSave behavior and the versioning logic used by OneDrive sync. This article explains why AutoSave triggers coauthoring conflicts and provides an admin checklist to configure OneDrive and Word settings so real-time collaboration works without interruptions.

Why AutoSave Causes Coauthoring Conflicts in Word

Word’s AutoSave feature saves changes to the cloud every few seconds while you type. When two or more people edit the same document at the same time, each person’s AutoSave sends a separate version to the server. OneDrive and SharePoint use a merge algorithm to combine these versions. If two edits touch the same paragraph or formatting element, the merge creates a conflict version that appears as a separate file with “(conflicted copy)” in the name.

The conflict occurs because AutoSave bypasses the manual save-and-merge workflow that coauthoring was designed for. In older versions of Word, users saved manually, which gave the server time to merge changes one at a time. AutoSave saves continuously, so overlapping edits are more likely to collide. Additionally, if OneDrive sync is running on a local machine and the file is also open in Word Online or another desktop instance, the sync client may upload a stale version that overwrites newer changes, producing another conflict.

The problem is not limited to Word. Excel and PowerPoint also have AutoSave, but Word documents are the most frequently coauthored and have the highest conflict rate due to the volume of simultaneous text edits. Admins must adjust settings for all three applications to reduce conflicts across the tenant.

Admin Checklist to Stop AutoSave Coauthoring Conflicts

Use this checklist to configure Word, OneDrive, and SharePoint settings. Apply these changes at the user level or tenant level depending on your organization’s control requirements.

Step 1: Disable AutoSave for coauthored documents via Group Policy

1. Open the Group Policy Management Console
   Run gpedit.msc on a domain controller or a management workstation with the Microsoft 365 administrative templates installed.
2. Navigate to Word AutoSave policy
   Go to User Configuration > Administrative Templates > Microsoft Word 2016 > Word Options > Save. Double-click “AutoSave OneDrive and SharePoint Online files by default on Word.”
3. Set the policy to Disabled
   Select Disabled and click OK. This prevents Word from automatically saving to the cloud for all users who receive this policy.
4. Apply the policy to the correct OU
   Link the GPO to the organizational unit that contains the coauthoring team members. Force a gpupdate /force on affected machines.

Step 2: Enable Files On-Demand on all coauthoring devices

1. Open OneDrive Settings
   Right-click the OneDrive cloud icon in the system tray and select Settings.
2. Go to Sync and backup > Advanced settings
   Click the Sync and backup tab, then click Advanced settings.
3. Turn on Files On-Demand
   Under Files On-Demand, select “Save space and download files as you use them.” This ensures that files are not fully synced locally, reducing the chance of a local save overwriting a server change.
4. Deploy via Intune or Group Policy
   Use the OneDrive ADMX policy “Allow syncing OneDrive accounts for specific organization” combined with “Files On-Demand enabled” to force this setting on all domain-joined machines.

Step 3: Enable server-side coauthoring merge optimization

1. Open the SharePoint admin center
   Go to admin.microsoft.com > SharePoint > Settings.
2. Locate the Coauthoring section
   Scroll to the Coauthoring section. Click the link to open coauthoring settings.
3. Set merge interval to 15 seconds
   Change the merge interval from the default 30 seconds to 15 seconds. This makes the server merge changes more frequently, reducing the number of overlapping edits per merge cycle.
4. Enable conflict resolution notifications
   Turn on “Notify users when a conflict is resolved.” Users see a message when their edits cause a conflict, helping them avoid the same action in the future.

Step 4: Train users to use the browser version for real-time coauthoring

1. Direct users to Word for the web
   When multiple people need to edit the same document simultaneously, open it in a browser at office.com. Word for the web handles real-time coauthoring without the sync conflicts that occur in the desktop app.
2. Disable desktop AutoSave during coauthoring sessions
   If users must use the desktop app, show them how to toggle AutoSave off using the slider in the top-left corner of the Word window. They should save manually after each significant change.

If Conflicts Persist After Configuration

OneDrive sync is uploading a stale local version

Even with Files On-Demand enabled, a local copy can become outdated if the user opens the file offline. When the user reconnects, OneDrive uploads the local version, overwriting newer server changes. To fix this, pause OneDrive sync before opening a coauthored file from a local folder. Right-click the OneDrive icon > Pause syncing > 2 hours. Resume sync only after closing the file.

Word Online shows “Another user is editing this file”

This message appears when a desktop instance of Word has the file locked for editing. The user should close the desktop version and refresh the browser tab. If the lock persists, the admin can force-close the file session from the SharePoint admin center: go to Active files, locate the document, and select “Close file.”

Conflicted copies appear even with AutoSave disabled

If users are saving manually at the same time, the server still creates a conflict version when two saves overlap. Train users to communicate before saving or to use the browser version exclusively for coauthoring. You can also increase the merge interval to 60 seconds to give users more time between saves.

AutoSave On vs AutoSave Off for Coauthoring Teams

Item	AutoSave On	AutoSave Off
Save frequency	Every few seconds	Only when user presses Ctrl+S or clicks Save
Conflict rate	High, especially with 3+ editors	Low, conflicts only when two users save simultaneously
User experience	No manual saves needed, but frequent conflict notifications	Manual saves required, fewer interruptions
Best for	Single-author editing or documents with infrequent changes	Multi-author coauthoring sessions with real-time collaboration

For teams that coauthor daily, turning AutoSave off and using Word for the web is the most reliable configuration. Admins who cannot disable AutoSave globally should apply the Group Policy only to the specific user group that coauthors frequently.

You can now configure Word AutoSave, OneDrive Files On-Demand, and SharePoint coauthoring settings to prevent conflict versions from appearing in your shared document libraries. Start by applying the Group Policy to disable AutoSave for the coauthoring team, then verify that Files On-Demand is enabled on every device. For an extra layer of protection, direct users to open coauthored files in Word for the web instead of the desktop app. A useful advanced tip: use the SharePoint REST API to programmatically close orphaned file locks by calling the _api/web/lists/getbytitle('Documents')/items(id)/undocheckout endpoint.