OneDrive Admin Checklist: Word AutoSave creates conflicts for review workflows

When multiple reviewers edit the same Word document stored in OneDrive, AutoSave can create file conflicts that disrupt review workflows. These conflicts appear as separate copies named with the reviewer’s device name and a conflict number, breaking the single-source-of-truth model that review processes depend on. This article explains why AutoSave triggers conflicts in shared editing scenarios, provides a step-by-step checklist for administrators to mitigate the issue, and details related failure patterns such as version history bloat and accidental overwrites.

Why AutoSave Creates Conflicts in Review Workflows

AutoSave in Word saves changes to OneDrive every few seconds. When two or more people open the same document, OneDrive expects co-authoring behavior: each person edits a separate paragraph, and the service merges changes automatically. In a review workflow, however, reviewers often edit the same sentence or paragraph sequentially, not simultaneously. OneDrive detects simultaneous saves to the same region of the document and creates a conflict file instead of merging.

The conflict file appears in the same folder with a name like DocumentName (User-PC-1).docx. The original file remains unchanged. The reviewer who caused the conflict sees a yellow bar in Word with the message “A conflict was resolved. See the conflict file.” This behavior is designed for non-co-authoring edits, but it disrupts formal review processes where a single document should track all changes through Track Changes mode.

Additionally, if a reviewer opens a document, makes changes, and closes without saving, AutoSave already saved partial changes to OneDrive before the close. The next reviewer sees those partial changes as the current version, which may break a review cycle that expects a clean baseline. Administrators must understand this timing issue to configure the environment correctly.

Admin Checklist to Prevent AutoSave Conflicts

1. Assess your review workflow type
   Determine whether reviewers edit simultaneously or sequentially. If reviewers take turns, AutoSave conflicts are likely. If they edit in parallel on different sections, co-authoring may work. Document the workflow before making changes.
2. Disable AutoSave for review documents via Group Policy
   Use the Group Policy template for Microsoft 365 Apps for enterprise. Navigate to User Configuration > Administrative Templates > Microsoft Word 2016 > Word Options > Save. Enable the policy “Do not allow AutoSave” and apply it to a security group containing reviewers. This forces manual saves and eliminates conflict creation.
3. Configure OneDrive sync conflict settings
   In the OneDrive admin center, go to Sync > Conflict resolution. Set the option to “Let me choose” or “Always keep both files.” The latter creates a conflict file for every save clash, which is not ideal for review workflows, but it prevents data loss. For review workflows, set to “Let me choose” so reviewers can decide.
4. Enable versioning with a low limit
   In the SharePoint document library hosting the review files, open Library settings > Versioning settings. Set “Create major versions” to 10 or fewer. This prevents conflict copies from filling the version history. Reviewers can still revert to a previous version if needed.
5. Use a dedicated review library with check-out required
   In the document library settings, enable “Require check-out” under Library settings > Versioning settings. When a reviewer checks out a document, no other user can edit it. AutoSave still works for the checking user, but no conflict occurs because only one person can edit at a time.
6. Train reviewers to disable AutoSave manually
   Instruct reviewers to open Word, go to File > Options > Save, and uncheck “Enable AutoSave for files stored in the cloud.” This per-user setting stops automatic saves. Reviewers must press Ctrl+S to save changes. This is the simplest fix for small teams.
7. Monitor conflict frequency with audit logs
   In the Microsoft 365 admin center, go to Audit > Search. Search for “File conflict detected” in the activity list. Review the frequency and document names. If conflicts occur more than once per week, enforce check-out or disable AutoSave for that library.

If AutoSave Still Creates Conflicts After Configuration

Reviewers see “A conflict was resolved” after saving

This message appears when OneDrive merged changes but created a conflict file for a specific paragraph. Open the conflict file, review the changes, and manually merge them into the original document. After merging, delete the conflict file. To prevent recurrence, ensure only one reviewer has the document open at a time.

AutoSave re-enables after a Word update

Microsoft 365 updates sometimes reset user settings. If you disabled AutoSave via Group Policy, verify the policy is still applied by running gpresult /h report.html on a reviewer’s machine. If the policy is missing, reapply the Group Policy object. For per-user settings, reviewers must recheck the option after each feature update.

Conflict files accumulate and exceed storage quota

Conflict files count toward the OneDrive or SharePoint storage quota. Set a retention policy in the Microsoft 365 compliance center to delete conflict files older than 30 days. Go to Compliance center > Data lifecycle management > Retention policies. Create a policy that applies to documents with “conflict” in the name and deletes them after 30 days.

AutoSave vs Manual Save in Review Workflows: Key Differences

Item	AutoSave Enabled	AutoSave Disabled (Manual Save)
Save frequency	Every few seconds	Only when user presses Ctrl+S or clicks Save
Conflict risk	High when multiple users edit same paragraph	Zero if only one user edits at a time
Version history entries	Many small versions	Fewer, more meaningful versions
Track Changes behavior	AutoSave saves Track Changes markup, which can confuse reviewers	Manual save captures a complete review state
Co-authoring support	Full support for simultaneous editing	Not recommended for simultaneous editing

You can now assess your organization’s review workflows and apply the appropriate configuration: disable AutoSave via Group Policy for sequential review, enable check-out for shared libraries, or train reviewers on manual saving. Next, review your document library versioning limits to prevent storage bloat from existing conflict files. As an advanced step, create a Power Automate flow that moves conflict files to a separate archive folder automatically, keeping the main library clean.