When multiple people edit a document in Microsoft 365 while Copilot is also generating or suggesting content, conflicts can occur. These conflicts happen because Copilot and human editors modify the same paragraph or cell at the same time. Microsoft 365 uses a specific conflict resolution order to decide which change stays and which change is discarded. This article explains the conflict resolution order for Copilot in-document co-authoring, how it works, and what you can do to avoid losing your work.
Key Takeaways: Copilot Co-Authoring Conflict Resolution Order
- Last writer wins at the paragraph level: The most recent change to a paragraph replaces all earlier changes, including Copilot-generated text.
- Copilot changes are applied as suggestions: Copilot edits are treated as user-like changes, not as system overrides, so they can be overwritten by any human edit.
- Manual saving triggers conflict detection: Saving the document manually forces the server to check for conflicts and apply the resolution order.
How Copilot Co-Authoring Conflict Resolution Works
Microsoft 365 co-authoring uses a distributed conflict resolution system. When Copilot generates text in a document, it creates a change set. A change set is a group of edits that are sent to the server together. Human edits are also sent as change sets. The server processes change sets in the order they arrive. If two change sets modify the same paragraph, the server keeps the last change set it received. This is called the last-writer-wins rule at the paragraph level.
Copilot edits are not treated as system-level commands. They are treated as user changes from a special Copilot session. This means a human edit that arrives after a Copilot edit will overwrite the Copilot change. The opposite is also true: if Copilot sends a change after a human edit, the Copilot change overwrites the human edit. The key factor is the order of arrival at the server, not the order of the original edits.
The conflict resolution order does not apply to entire documents. It applies only to the paragraph or table cell that was changed. If you edit paragraph A and Copilot edits paragraph B, no conflict occurs. If both changes touch paragraph C, the conflict resolution order decides which version stays.
Server-Side Merge Logic
The server uses a three-way merge algorithm. It compares the original version of the document, the version from Copilot, and the version from the human editor. If both versions change the same sentence, the server picks the version with the later timestamp. If only one version changes a sentence, that change is kept. The merge happens automatically every time a change set is saved.
Client-Side Conflict Notification
When a conflict occurs, the Word desktop app or Word for the web shows a notification. The notification says that a conflict was resolved. It does not show which version won. You can review the document by turning on Track Changes. Track Changes shows you what Copilot added or removed and what you added or removed. This is the only way to see the conflict after it is resolved.
Steps to Manage Conflicts During Copilot Co-Authoring
- Turn on Track Changes before starting co-authoring
Open the document. Go to Review > Track Changes and select For Everyone. This records every change made by Copilot and every change made by human editors. You can see which change won the conflict after the merge. - Use the Save button manually after each major edit
Press Ctrl+S or click File > Save. Manual saving forces the server to process all pending change sets. This gives you a clearer timeline of which change was sent first. - Wait for Copilot to finish before you edit the same paragraph
When Copilot is generating text, the Copilot pane shows a status indicator. Wait until the indicator stops spinning before you type in the same paragraph. This reduces the chance of overlapping edits. - Use the Undo command to revert unwanted conflict results
If a conflict resolution removed your change, press Ctrl+Z immediately. The Undo command restores your last change set, which may include the overwritten text. You can then re-apply your edit after Copilot has finished. - Review conflict areas with the Compare command
Go to Review > Compare > Compare and select the version before the conflict. Word shows a detailed diff of what changed. This helps you identify which paragraph was affected by the conflict resolution order.
If Copilot Overwrites Your Edits Frequently
Copilot generates text while you are typing in the same paragraph
This happens when Copilot is set to generate suggestions automatically. To fix this, open the Copilot pane and click the Settings gear icon. Under Suggestion mode, select Manual. Copilot will only suggest text when you click the Generate button. This prevents Copilot from sending change sets while you are actively editing.
Two human editors and Copilot are editing the same document
When three or more sessions edit the same paragraph, the conflict resolution order becomes harder to predict. The server processes change sets in the order they arrive. Network latency can cause changes to arrive out of order. To reduce this, assign paragraphs to specific editors. Use comments to coordinate who edits which section.
Copilot changes disappear after a human saves the document
If Copilot generated text and then a human editor saved the document, the human save may have overwritten the Copilot change. This happens when the Copilot change set arrived at the server before the human change set but was processed after. To prevent this, ask all editors to wait 10 seconds after Copilot finishes before saving the document. This gives the server time to process the Copilot change set.
| Item | Copilot Change Set | Human Editor Change Set |
|---|---|---|
| Description | Generated text or suggestion from Copilot | Manual typing, deletion, or formatting by a person |
| Conflict resolution rule | Last change set to arrive at the server wins | Last change set to arrive at the server wins |
| Treatment by server | Treated as a user change from a Copilot session | Treated as a user change from a human session |
| How to see the conflict | Turn on Track Changes before co-authoring | Turn on Track Changes before co-authoring |
| How to revert a lost change | Press Ctrl+Z immediately after the conflict | Press Ctrl+Z immediately after the conflict |
Microsoft Copilot in-document co-authoring uses a last-writer-wins conflict resolution order at the paragraph level. You can manage conflicts by turning on Track Changes, saving manually, and waiting for Copilot to finish before editing the same paragraph. If conflicts happen too often, switch Copilot to manual suggestion mode. Use the Undo command to restore overwritten text. For large documents with multiple editors, assign paragraphs to specific people to reduce overlapping edits.