OneDrive for Business Word AutoSave troubleshooting for Teams meetings: creates conflicts

When you edit a Word document during a Microsoft Teams meeting, AutoSave can create file conflicts even when only one person is typing. The conflict appears as a separate copy of the file with a generated name, such as Document (conflict copy). This happens because Teams temporarily locks the file for live collaboration features like co-authoring and meeting recording annotations. This article explains why AutoSave triggers conflicts in Teams meetings, how to stop the behavior, and how to recover your work without losing changes.

Why AutoSave Creates Conflicts in Teams Meetings

When you join a Teams meeting and share a Word document from within the meeting window, Teams applies a temporary lock on the file. This lock enables live co-authoring, annotations, and recording highlights. AutoSave, which normally saves every few seconds, attempts to write to the file while it is locked. OneDrive detects the write conflict and creates a separate conflict copy instead of overwriting the original.

The conflict copy is stored in the same OneDrive folder as the original file. Its filename includes the phrase (conflict copy) followed by a timestamp. The original file remains unchanged. This behavior is by design to prevent data loss, but it causes confusion when you expect a single file to contain all edits.

The problem is most common when you share the Word document directly from the Teams meeting Share menu using the Share from Window option. Sharing your entire desktop instead does not trigger the same file lock, because Teams does not need to manage the document content.

Steps to Stop AutoSave Conflicts During Teams Meetings

1. Disable AutoSave for the active document
   In Word, go to File > Options > Save. Under AutoSave, select the checkbox labeled Disable AutoSave for this file only. Click OK. This stops Word from writing to the file until you re-enable AutoSave after the meeting ends.
2. Save a manual copy before sharing
   Press Ctrl+S to save the file once. Then click File > Save As > OneDrive and create a copy with a different name, such as Document_MeetingDraft. Share this copy during the meeting. The original file remains untouched.
3. Share your entire desktop instead of the Word window
   In the Teams meeting, click Share > Content > Share from Desktop. Select your entire screen. This prevents Teams from locking the Word file. You can edit the document normally, and AutoSave will not create conflicts.
4. Use Word for the web during the meeting
   Open the document in a browser at office.com. Click Edit in Browser. Teams does not lock files opened in the web version. AutoSave in Word for the web works without creating conflict copies.
5. Close the file after sharing
   If you already shared the file, close it in Word after the meeting. Open it again from OneDrive. The conflict copy may still appear, but the original file will be editable without further conflicts.

If Conflicts Have Already Appeared

OneDrive shows a conflict copy named Document (conflict copy 2025-03-15 1430)

Open both files side by side. In the original file, go to Review > Compare > Combine. Select the conflict copy as the document to merge. Word will show each changed line and let you accept or reject them. After merging, delete the conflict copy from OneDrive.

AutoSave keeps creating new conflict copies every few minutes

This happens when you leave the file shared in the meeting and AutoSave is still enabled. End the meeting or stop sharing the window. Then disable AutoSave using the steps above. If the file is still locked, restart Word.

The original file shows no changes after the meeting

All your edits were saved to the conflict copy. Open the conflict copy and save it over the original file. Use File > Save As and choose the original filename in the same OneDrive folder. Confirm the replacement. Delete the conflict copy afterward.

AutoSave On vs AutoSave Off in Teams Meetings: Key Differences

Item	AutoSave On	AutoSave Off
File locking by Teams	Triggers conflict copies when file is locked	No conflict copies because Word does not write
Recovery after meeting	Must merge conflict copy with original	Original file contains all manual saves
Real-time co-authoring	Works but creates duplicates for each save	Disabled; only one user can edit at a time
Best for	Editing alone without sharing in meeting	Editing while sharing in a Teams meeting

After the meeting, you can re-enable AutoSave by going to File > Options > Save and clearing the Disable AutoSave for this file only checkbox. Press Ctrl+S to ensure the last change is saved. Use Version History on the OneDrive website to restore the file to any point before the meeting if the conflict copy overwrote your work.