That convenience should not be confused with a new, complete audit system. The feature is a conversational layer over the workbook history Excel already has available. It can make existing information faster to interrogate, but it cannot reconstruct changes that were never tracked, are no longer retained, or fall outside supported history. For important financial, operational, or compliance-sensitive workbooks, that distinction determines whether Copilot is a useful investigation assistant or an insufficient recovery plan.
What the new Excel skill is designed to do
Microsoft describes the change-history skill as a way to understand how a workbook has evolved over time. It is available in Excel on Windows, Mac, and the web as part of the August 2026 rollout.
Its most practical function is summarization. Rather than starting with a vague sense that “something changed,” a user can ask Copilot to catch them up on recent workbook activity. The request can be broad, covering the workbook as a whole, or narrowed to a specific worksheet, table, range, or cell. Users can also focus the question on a particular person or a time period.
That scope matters in real work. A shared workbook can contain dozens of benign edits alongside one consequential formula change. An account manager may only need to know what changed in the current month’s pipeline table. A finance reviewer may want to examine updates to a forecast range after a planning deadline. A workbook owner taking over from a colleague may need a summary of edits associated with that colleague rather than a narrative of every change in the file.
Copilot can also identify who changed a cell and when, and Microsoft says it can summarize changes made by a particular user or by Copilot itself. This creates a potentially useful separation between asking what changed and asking whose activity should I inspect first.
The feature is not limited to description. Microsoft says it can help undo specific edits or restore formulas by returning a workbook to a prior working state. That could shorten the path from spotting a suspicious result to correcting it, particularly when a formula was working earlier and the workbook history gives a clear point at which it changed.
A faster investigation tool, not a replacement audit record
The most important limitation is straightforward: Copilot reports only history that is already available in the workbook’s change history.
In practical terms, Copilot does not create an independent record of workbook activity. It cannot fill in omissions caused by unsupported Excel versions or by features whose changes are not tracked. Microsoft also states that supported changes are tracked for up to 365 days. If the relevant event is older than that period, a Copilot question cannot make it reappear merely because the user asks for a longer historical summary.
This affects how Windows users should frame the feature. It is sensible to use Copilot to triage a confusing workbook, identify an editor, or find the likely period in which a problem was introduced. It is not sensible to assume that a calm-sounding summary establishes that no other relevant activity occurred.
For example, a prompt scoped to a critical range may produce a helpful recap of the available change record. But an absence of reported changes is only evidence about the history Copilot can access. It is not proof that the range was untouched in every possible sense.
That is especially relevant in organizations where people work across a mixture of current Microsoft 365 apps, older Excel clients, and different workbook workflows. The history available to Copilot can have gaps when unsupported versions or untracked features are involved. A team that needs defensible records should establish its controls around known retention, storage, access, and review requirements—not around the assumption that an AI summary is exhaustive.
How to use it effectively in a shared workbook
The feature is most likely to be valuable when questions are precise and tied to a decision. A broad request may be a sensible first step when reopening a workbook after time away, but narrower questions will generally be more actionable.
Useful lines of inquiry include:
- Recent changes across the workbook when a user needs a quick catch-up.
- Changes on a named worksheet when a workbook has separate input, calculation, and reporting areas.
- Activity in a table, range, or individual cell when a number or formula looks wrong.
- Changes by a particular collaborator when handing off responsibility or reviewing a contribution.
- Changes during a defined time period, such as after a forecast cut-off or before a published report.
- Changes attributed to Copilot itself, when a team needs to distinguish AI-assisted activity from the rest of the available history.
The resulting summary should be treated as the beginning of review, not its endpoint. A good workflow is to use the summary to locate the relevant sheet, range, editor, or interval, then inspect the workbook result itself before making a consequential decision. If a formula is restored or an edit is undone, check the downstream calculations and outputs as well. A seemingly local correction can alter totals, lookups, models, or reports elsewhere in the workbook.
This is an inference from the feature’s documented dependence on available history: the more significant the business consequence of a change, the less appropriate it is to rely solely on a natural-language recap of it. Copilot can reduce the time needed to find the issue; human review remains necessary to decide whether the identified change was actually erroneous and whether a proposed restoration produces the intended outcome.
Recovery has a boundary: use Version History for larger rollbacks
Microsoft’s documentation draws an important line between investigating or correcting discrete activity and recovering a prior state of the workbook.
The new skill can help with specific edits and restoring formulas to a prior working state. But for restoring multiple changes or recovering an older workbook version, Microsoft directs users to Version History. That is the more appropriate control when the issue is not one formula or one recent mistake, but an entire sequence of edits, an unclear collaboration session, or a need to return to a known-good file state.
Version History has storage requirements that users should verify before they need it. It requires the workbook to be stored in OneDrive or SharePoint in Microsoft 365. A file kept only on a local Windows PC does not meet that documented requirement.
Retention also differs by account context. Personal Microsoft accounts can retrieve the last 25 versions. For work or school accounts, retention depends on how the relevant SharePoint or OneDrive library has been configured. There is no single retention assumption that every organization can safely make.
The practical lesson is to place important shared workbooks in the appropriate cloud-backed location before a recovery event occurs. A team that relies on emailed copies, local folders, or ad hoc file duplication may still have informal fallbacks, but those are not the documented Version History workflow described for Microsoft 365.
Why Copilot history and Version History complement each other
The two tools answer different questions.
Copilot change history is conversational and investigative. It is built to help a user understand available workbook activity: what changed, when it changed, and who was associated with the change. Its strength is reducing the friction of exploring a complicated edit history.
Version History is a recovery mechanism for earlier file states. Its strength is rollback when a broader set of changes must be reversed or an older version must be recovered.
A resilient workflow uses both in sequence. Start with Copilot when the problem is uncertain: identify the likely time window, the affected sheet, or the editor connected to the change. If inspection confirms that a discrete edit is the problem, use the available correction path carefully and validate the result. If the scope is larger, or the workbook needs to be returned to an earlier state, switch to Version History rather than trying to reconstruct a broad rollback one small edit at a time.
This division is also a safeguard against overinterpreting the promise to “undo specific edits.” Microsoft’s documented guidance explicitly points to Version History for multiple changes and older versions. Users should therefore avoid assuming that every complex selective rollback scenario is supported through a conversational request alone.
Claims users should treat cautiously
Some descriptions of the feature go beyond what Microsoft’s public feature material clearly establishes.
The August 2026 announcement says the skill rolled out then, but the material reviewed does not establish a formal “generally available” designation. That may sound like a small wording difference, yet it matters for IT teams that distinguish a rollout from a feature status tied to support, entitlement, or deployment commitments.
There are also reports that edits made manually and those made with Copilot assistance can be visually distinguished with different colors, and that users can selectively undo a named person’s Copilot-assisted changes while retaining that person’s manual edits. Those specific controls are not described in the public Microsoft support material for the change-history skill. They should not be built into training, governance rules, or recovery runbooks until Microsoft documents them for the relevant environment.
Similarly, availability should be verified in the organization’s actual Excel and Microsoft 365 deployment rather than assumed from the announcement alone. The supplied material establishes the rollout across Windows, Mac, and web, but it does not provide a feature-specific entitlement matrix that guarantees immediate access for every kind of account or tenant.
What Windows users should do now
For ordinary collaborative spreadsheets, the new skill can make Excel less opaque. It gives a workbook owner a quicker way to ask where activity occurred, identify who edited a cell, summarize a limited period, or investigate a formula that no longer behaves as expected.
For business-critical workbooks, use it as one layer in a larger discipline:
- Store files that need recoverability in OneDrive or SharePoint in Microsoft 365.
- Confirm that Version History is available before a major collaboration cycle begins.
- Use Copilot history to narrow an investigation to a worksheet, range, user, or time period.
- Validate the actual workbook values, formulas, and downstream outputs before accepting a summary or restoring a formula.
- Use Version History when the recovery need involves multiple changes or an earlier file version.
- Plan around the 365-day limit for supported tracked changes, and do not assume history is complete where older or unsupported Excel workflows are involved.
The change-history skill is a meaningful usability improvement because shared Excel workbooks often fail not through a lack of data, but through a lack of context. Copilot can help recover that context quickly. Its value is highest when users understand its boundary: it explains the history Excel has retained; it does not replace retention policy, cloud versioning, careful workbook design, or review of changes that matter.