OneDrive Admin Checklist: Word AutoSave creates conflicts for shared presentations

When multiple users edit a PowerPoint presentation stored in OneDrive, Word AutoSave can trigger file merge conflicts that break co-authoring. This happens because AutoSave saves every keystroke to OneDrive, and when two people save conflicting changes simultaneously, OneDrive creates a separate conflict copy. This article explains why AutoSave causes these conflicts for shared presentations and provides an admin checklist to prevent them without disabling AutoSave entirely.

Why AutoSave Creates Conflicts for Shared Presentations

AutoSave in Microsoft 365 apps saves changes to OneDrive every few seconds. For shared PowerPoint presentations, this frequent saving can cause merge conflicts when two people edit the same slide at the same time. OneDrive detects the simultaneous writes and creates a separate conflict copy named with the user’s name and a timestamp. The original file remains unmerged, forcing someone to manually reconcile the two versions.

The root cause is that OneDrive’s default conflict resolution behavior prioritizes individual saves over collaborative merging. When AutoSave triggers a save from User A while User B has unsaved changes, OneDrive cannot determine which version to keep. Instead of merging, it duplicates the file. This behavior is by design to prevent data loss, but it disrupts co-authoring workflows.

Two technical factors contribute to this problem:

Simultaneous Save Timing

AutoSave saves changes every 5 to 10 seconds. If two users edit the same presentation within that window, their saves collide. OneDrive processes the first save and then receives the second save for the same file version. Because the second save is based on an outdated version, OneDrive cannot apply it cleanly.

File Locking Behavior

OneDrive uses optimistic concurrency for co-authoring. It does not lock the file while someone edits. Instead, it relies on the Office app to merge changes at the paragraph or slide level. When AutoSave bypasses the manual merge process, the server receives raw byte-level changes that conflict.

Admin Checklist to Prevent AutoSave Conflicts

Use this checklist to configure OneDrive and SharePoint settings so that AutoSave works smoothly for shared presentations.

1. Disable AutoSave for SharePoint and OneDrive shared libraries
   In the Microsoft 365 admin center, go to Settings > Org settings > Office cloud policy service. Create a policy for Word, Excel, and PowerPoint. Set AutoSaveOnSharePoint to Disabled. This turns off AutoSave only for files stored on SharePoint and OneDrive shared with other people. Users can still manually save.
2. Enable server-side conflict detection
   Run the following PowerShell command as a SharePoint admin: Set-SPOTenant -EnableAutoSaveConflictDetection $true. This tells OneDrive to attempt a server-side merge before creating a conflict copy. If the merge succeeds, no duplicate file appears. If it fails, OneDrive still creates a conflict copy as a fallback.
3. Restrict AutoSave to the current user only
   In the OneDrive admin center, go to Sync > Co-authoring settings. Enable Prevent AutoSave from saving changes made by other users. This setting limits AutoSave to only the user who opened the file. Other users’ changes are not saved by AutoSave until they manually save or close the file.
4. Set a co-authoring save interval
   In the Office cloud policy service, create a policy for PowerPoint. Set AutoSaveIntervalSeconds to 120. This increases the time between AutoSave saves from 10 seconds to 2 minutes. Longer intervals reduce the chance of simultaneous saves.
5. Train users to use manual save for shared files
   Instruct users to press Ctrl+S instead of relying on AutoSave when editing a shared presentation. Manual saves give OneDrive time to process each save before the next one arrives. Users can still use AutoSave for personal files.
6. Enable version history for conflict recovery
   In the SharePoint admin center, go to Settings > Version history. Set the number of versions to keep to 500 or higher. If a conflict copy is created, users can restore the original file from version history without losing work.

Common Issues After Configuring AutoSave Settings

Users report AutoSave is completely disabled

If you set AutoSaveOnSharePoint to Disabled globally, users lose AutoSave for all SharePoint and OneDrive files, including personal ones. To fix this, create a separate policy that applies only to shared libraries. Use the Path filter in the Office cloud policy service to target folders with multiple editors.

Conflict copies still appear after enabling server-side detection

Server-side conflict detection works only for files that support co-authoring. PowerPoint files with embedded objects or macros may not merge. Check that the file is saved in the .pptx format and does not contain ActiveX controls. Convert legacy .ppt files to .pptx.

AutoSave setting reverts after a policy update

Office cloud policy settings apply at the next app restart. If users leave PowerPoint open for days, the old setting persists. Instruct users to close and reopen PowerPoint after you update the policy. You can also push a restart notification via Intune.

AutoSave Behaviors: Personal vs Shared Libraries

Item	Personal OneDrive Library	Shared OneDrive or SharePoint Library
AutoSave default state	On	On
Conflict copy creation	Rare	Frequent with multiple editors
Co-authoring support	Yes	Yes
Server-side merge available	No	Yes, with EnableAutoSaveConflictDetection
Admin policy control	Limited to AutoSaveOnSharePoint	Full via cloud policy and PowerShell

You can now configure AutoSave settings for your organization to prevent conflict copies in shared presentations. Start by enabling server-side conflict detection with PowerShell, then create a cloud policy to limit AutoSave frequency for shared libraries. For advanced control, use the OneDrive admin center co-authoring settings to restrict AutoSave to the current user only.