OneDrive Admin Checklist: Word AutoSave creates conflicts for Teams meetings

When a Teams meeting attendee edits a Word document that is already open by another participant, AutoSave can generate file conflicts and version collisions. The root cause is that Word’s AutoSave feature uploads changes every few seconds, which can overwrite or clash with simultaneous edits from multiple users in a shared meeting workspace. This article explains why AutoSave triggers conflicts during Teams meetings and provides an admin checklist to configure OneDrive and Word settings to reduce or eliminate these disruptions.

Why Word AutoSave Creates Conflicts During Teams Meetings

Word AutoSave saves changes to OneDrive every few seconds as the user types. In a Teams meeting where multiple participants are editing the same document, each person’s AutoSave uploads their current version independently. When two or more users modify the same paragraph simultaneously, the server receives conflicting writes. OneDrive then creates a separate conflict copy, often named with the user’s name and a timestamp, instead of merging the changes cleanly.

The technical cause is the lack of real-time co-authoring coordination during rapid saves. While Word supports co-authoring, AutoSave can outpace the merge logic when edits happen within the same second. Teams meeting chat and shared file tabs compound the issue because the document is opened from a meeting context, not a dedicated SharePoint library with proper co-authoring settings.

How AutoSave Differs from Manual Save in a Meeting

Manual Save (Ctrl+S) only triggers once per user action. AutoSave fires automatically on every keystroke or formatting change. In a meeting with five editors, AutoSave can generate dozens of version uploads per minute. The server must reconcile each upload, and when two uploads arrive for the same part of the document, a conflict is created. Manual saves reduce the frequency of these collision windows.

Admin Checklist to Prevent AutoSave Conflicts in Teams Meetings

Follow these steps to configure OneDrive, Word, and SharePoint settings that reduce or eliminate AutoSave conflicts during Teams meetings.

1. Enable Files On-Demand across the tenant
   In the OneDrive admin center, go to Sync > Files On-Demand and set the toggle to On. This ensures meeting participants stream the file from the cloud instead of editing a local offline copy that may be stale.
2. Set SharePoint versioning to limit conflict copies
   In the SharePoint admin center, select the document library used for Teams meeting files. Go to Library settings > Versioning settings. Set “Require Check Out” to Yes. Set “Keep the following number of major versions” to 100 and “Keep drafts for the following number of major versions” to 10. This reduces the number of orphaned conflict versions.
3. Disable AutoSave globally for meeting-attached documents via Group Policy
   Use the Group Policy Management Console. Navigate to User Configuration > Administrative Templates > Microsoft Word 2016 > Word Options > Save. Enable the policy “Do not allow AutoSave” and apply it to security groups that include meeting participants. This forces manual saves for all documents opened from Teams.
4. Configure a meeting-specific document library with no AutoSave override
   Create a dedicated SharePoint document library for Teams meeting files. In the library settings, under “Advanced settings,” set “Open in the client application” to No. This forces Word Web App usage, which has a slower save cadence and better conflict detection than the desktop app.
5. Communicate the manual save workflow to meeting attendees
   Send a tenant-wide message instructing users to press Ctrl+S before leaving a paragraph or after making three or more edits. This reduces the number of concurrent saves and lowers collision probability.
6. Monitor conflict reports in the OneDrive admin center
   Go to OneDrive admin center > Reports > Sync. Review the “Files with conflicts” metric weekly. If conflicts exceed 1% of total files in a meeting library, enforce the Group Policy from step 3 for that group.

When Conflicts Still Occur After Configuration

Even with the above settings, some conflict scenarios remain. Below are the most common residual issues and how to address them.

Conflict copy appears with “-User Name” suffix

OneDrive creates a file named “Document-User Name.docx” when two saves arrive at the same millisecond. Open both copies side by side in Word, use the Compare feature under Review > Compare, and merge the changes. Then delete the conflict copy. To prevent recurrence, enforce the check-out requirement in the library settings.

AutoSave re-enables after a Word update

Microsoft Office updates sometimes reset AutoSave to the default On state. Run a PowerShell script monthly that queries the registry key HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Word\Options and sets the DWORD “DisableAutoSave” to 1. Deploy the script via Intune or Group Policy to maintain the setting.

Teams meeting recording files also show conflicts

Teams meeting recordings saved to OneDrive can conflict when multiple organizers try to rename or move the file simultaneously. Instruct organizers to use the meeting chat’s file tab to access recordings and avoid editing the file name during the meeting. Set the recording library to require check-out as described in step 2 of the checklist.

AutoSave On vs AutoSave Off in Teams Meeting Documents

Item	AutoSave On	AutoSave Off
Save frequency	Every 2-5 seconds while typing	Only when user presses Ctrl+S or clicks Save
Conflict rate in a 5-person meeting	Approximately 15-20 conflicts per hour	0-2 conflicts per hour
User awareness of changes	Low — saves happen without visible feedback	High — user must consciously save
Recovery after crash	Automatic recovery from last AutoSave	Manual recovery from last manual save
Admin overhead to manage conflicts	High — frequent conflict copy cleanup needed	Low — conflict copies are rare

After applying the checklist, your tenant will see fewer AutoSave conflicts during Teams meetings. Start by enabling Files On-Demand and setting the Group Policy to disable AutoSave for meeting document libraries. Monitor the OneDrive conflict report weekly to confirm the reduction. For persistent issues, enforce check-out on the SharePoint library and run the registry script monthly to prevent AutoSave from reactivating after updates.