OneDrive Admin Checklist: Word AutoSave creates conflicts for policy documents

When multiple editors work on the same policy document in Word, AutoSave can create sync conflicts that overwrite changes or generate duplicate files. These conflicts happen because AutoSave saves every keystroke to OneDrive in real time, and when two users edit the same paragraph simultaneously, Word cannot merge the changes cleanly. This article explains the root cause of these conflicts, provides a step-by-step admin checklist to prevent them, and describes related failure patterns you should watch for.

Why Word AutoSave Creates Conflicts in Policy Documents

Word AutoSave saves changes to OneDrive every few seconds by default. This feature works well for personal files, but in a shared policy document library, multiple editors can make changes at the same time. When two users edit the same paragraph, Word attempts to merge the changes. If the merge fails, OneDrive creates a conflict copy with a name like “Policy_v2 (User Name’s conflicted copy 2025-03-15).docx.”

The conflict occurs because Word does not lock the document for exclusive editing. Each user sees the last saved version, not the current keystrokes of the other editor. When both save, the server detects a version mismatch and generates a conflict file. Policy documents are especially vulnerable because they are often edited by multiple stakeholders simultaneously during review periods.

The Role of OneDrive Sync

OneDrive sync adds another layer of complexity. If a user opens a policy document from a synced folder instead of the web app, the local copy may be out of date. When AutoSave triggers, it writes to the local file, which then syncs to the cloud. This can overwrite changes made by another user who opened the same document from a different device. The result is either a lost change or a conflict file that an admin must manually resolve.

Admin Checklist to Prevent AutoSave Conflicts in Policy Documents

Use the following steps to configure your tenant and document libraries so that AutoSave does not create conflicts for policy documents. Apply these settings before the next review cycle.

Step 1: Disable AutoSave for the Policy Document Library

1. Open the SharePoint document library
   Navigate to the library that contains your policy documents. Click the gear icon and select Library settings.
2. Click Advanced settings
   Under General settings, click Advanced settings.
3. Set Open in the client application
   Find the option Open in the client application and set it to No. This forces users to open policy documents in the browser, where AutoSave is still active but sync conflicts are less frequent because the browser version uses real-time co-authoring.
4. Click OK
   Save the setting. Users will now open policy documents in Word for the web by default.

Step 2: Enforce Check-Out for Policy Documents

1. Return to Library settings
   From the same document library, click Library settings again.
2. Click Versioning settings
   Under General settings, click Versioning settings.
3. Require Check Out
   Under Require Check Out, select Yes. This forces each user to check out a document before editing. No other user can edit the same document until it is checked back in.
4. Set a draft item security level
   Under Draft Item Security, select Only users who can edit items. This prevents viewers from seeing incomplete versions.
5. Click OK
   Save the versioning settings.

Step 3: Restrict Sync for the Policy Library

1. Open the OneDrive admin center
   Go to https://admin.onedrive.com and sign in with your global admin account.
2. Click Sync
   In the left navigation, click Sync.
3. Set sync restrictions
   Under Restrict syncing to specific domains, add the domain of your managed devices. Under Block sync on unmanaged devices, select Block sync. This ensures that only company-managed devices can sync the policy library.
4. Click Save
   Apply the sync restrictions.

Step 4: Configure Word AutoSave Defaults via Group Policy

1. Download the Office Administrative Templates
   From the Microsoft Download Center, download the latest Office Administrative Template files.
2. Open Group Policy Management Console
   On a domain controller, open the Group Policy Management Console and create a new GPO linked to the OU containing your policy editors.
3. Navigate to Word AutoSave setting
   Go to User Configuration > Policies > Administrative Templates > Microsoft Word 2016 > Word Options > Save.
4. Disable AutoSave
   Double-click Do not show AutoSave option, select Enabled, and click OK. This hides the AutoSave toggle in Word and forces users to save manually.
5. Link the GPO
   Link the GPO to the correct OU and run gpupdate /force on affected workstations.

If AutoSave Conflicts Still Appear After Configuration

Users Report Conflicted Copies Appearing in the Library

If you still see conflicted copies after applying the checklist, check the version history of the policy document. Open the document, click the document title, and select Version history. Look for versions with the label “Conflict.” Delete any conflict versions that are not needed. Then verify that all users have the latest version of Word. Older versions of Word may not respect the Require Check Out setting.

AutoSave Still Active Despite Group Policy

If the Group Policy setting does not disable AutoSave, check that the policy is applied to the correct user group. Run gpresult /h report.html on a test machine and look for the Word AutoSave setting. If it shows as “Not Configured,” the GPO may not be linked correctly. Also verify that the Office Administrative Templates are the latest version. Older templates may not include the AutoSave setting.

Check-Out Not Enforced for Existing Documents

Require Check Out applies only to documents created or uploaded after the setting is enabled. Existing policy documents will not be checked out automatically. To apply the setting to existing documents, open the library in File Explorer, select all policy documents, right-click, and choose Check Out. Then check them back in immediately. This forces the check-out flag on each file.

AutoSave vs Manual Save for Policy Documents: Key Differences

Item	AutoSave Enabled	Manual Save (AutoSave Disabled)
Save frequency	Every few seconds while typing	Only when user presses Ctrl+S or clicks Save
Conflict risk	High with multiple simultaneous editors	Low because saves are deliberate and less frequent
Co-authoring support	Full real-time co-authoring with merge	Co-authoring still works but merges only on manual save
Version history entries	Many small versions, cluttering history	Fewer versions, easier to review
Best use case	Individual drafts or non-critical files	Policy documents, contracts, compliance files

With AutoSave disabled and Require Check Out enabled, policy documents are protected from accidental overwrites and sync conflicts. Users must deliberately save their changes, and only one person can edit at a time. This eliminates the most common cause of conflict files in policy libraries.

After applying the checklist, test the configuration with a small group of editors before rolling out to the entire organization. Ask each editor to open the same policy document, make a change, and save. No conflict copies should appear. If conflicts still occur, review the versioning settings and verify that all editors are using a supported version of Word. As a final step, configure an alert in the SharePoint library to notify you whenever a conflict file is created, so you can respond quickly.