Copilot / Documents, Data & Research
Copilot: compare two document versions systematically
Name the files Old and New and include their revision dates. Select one section to compare before attempting the entire document.
Environment and inputs: Copilot user guide · Feature and source access depend on the active account, app and organization settings. Optional file or app steps have a text-excerpt fallback. No fixed model version, price or usage quota is assumed.
What you will make
A practical Copilot guide to compare two document versions systematically. Use the sample input and prompt, then check the result. Use a fictional Microsoft 365 workplace task as the practice setting. Identify the file or excerpt that supports the requested result.
Prepare the source and scope
Name the files Old and New and include their revision dates. Select one section to compare before attempting the entire document. Open your available Microsoft Copilot experience and confirm whether it can read the intended work source.
Try this prompt
In Copilot, provide the prepared input, then send the following request. For real work, replace fictional details with approved facts.
Compare the approval-workflow sections in Old and New. Return Added, Removed and Changed requirements with both section references. Ignore cosmetic formatting changes.
Review the result
Verify one item from each change type directly in both files; ensure a moved paragraph is not counted as a new requirement. Record each correction and its supporting source.
If the answer is wrong or incomplete
Comparison can miss tables or scanned text. Review those parts separately before treating the difference list as complete. If the active Copilot surface cannot access the file or app, paste an authorized excerpt into chat. Keep the same review criteria for the text-only workflow.
Practice and completion check
Repeat with one incomplete input. Check the answer against the review criteria, remove unsupported claims and save the prompt with its source version. This workflow has not been verified in a customer deployment.