
Contents
An AI assistant answers from the text it indexed. In SharePoint one procedure usually exists as the current major version, as older major versions in version history, as a minor draft visible only to editors, and as copies elsewhere. To stop outdated answers, decide which of these copies reach the index, keep drafts out of readers’ answers, and require that every answer names the document and the version it used.
Where do outdated answers come from?
A language model does not know which text is authoritative. It receives passages that a retrieval step selected, and it writes an answer from them. If a passage from a superseded procedure is in the index, it can be selected.
In a SharePoint tenant a quality procedure typically has four kinds of copies. The current published major version. Earlier major versions in the version history. A minor draft that an editor is working on. And duplicates: a PDF export in a project folder, an attachment in a mailbox, a copy on a Teams channel.
Microsoft notes that for Microsoft 365 customers “versioning is now turned on by default when you create a new library or list, and it will automatically save the last 500 versions of a document.”[1] The history is there whether or not anyone intended an assistant to read it.
So the question for a quality or compliance manager is not “is the model good”. It is “which of these copies does the assistant read, and does it tell me which one it used”.
What does SharePoint versioning keep, and who sees drafts?
Microsoft’s support documentation is precise here. “Major versions are identified by whole numbers, such as 5.0; minor versions are identified by decimal numbers, such as 5.1.”[1]
A library owner can choose major versions only or “major and minor versions”, can “limit the number of versions and drafts to retain”, and can “set who can see draft items”.[2]
Draft visibility is the setting that matters most for AI. “When you track major and minor versions, you can specify whether people must have permission to edit files before they can view and read a minor version.”[1]
When that is applied, “people who have permission to edit the file can work on the file, but those who have permission only to read the file cannot see the minor version.”[1] Where content approval is also required, Microsoft says readers without draft rights “will see the last approved or major version of the file”; content approval itself is the subject of the next chapter.[1]
At the organisation level, Microsoft Learn states that the “Default Version History limits for your organization is set to Manual version history limits with 500 major version count limit and no expiration.”[3]
When a library limit is lowered, old versions are not removed at once; “the process of version deletion occurs gradually, with up to 20 versions being removed for every new version created.”[4]
The practical consequence: a rule you replaced two years ago is still stored, by default, in the version history of the same file. Whether it reaches an AI index is a design decision of the assistant, not a property of SharePoint.
Should an AI assistant read old versions at all?
There are two legitimate positions.
The first: an assistant for daily work should read only the current major version. Anyone asking “what is the review cycle” wants today’s rule, and an older number in the answer is simply wrong.
The second: an auditor or a complaint investigation sometimes needs the rule as it stood on a past date. For that, earlier major versions are useful, but only if the answer says clearly that a version is superseded and only to a person who may open the file anyway.
Reading version history is technically simple, so it must be a deliberate choice. Microsoft Graph returns the stored versions of a file, newest first, to any app with Files.Read.All (or a higher) application permission.[5] Microsoft notes that previous versions may be retained only for a finite period, depending on admin settings.[5]
An indexer can therefore read the stored versions of every file it can reach. Whether it should, and whether the result is labelled, is what you are buying when you choose an assistant. The same question applies to any assistant you evaluate, with or without Microsoft Copilot.
How can a reader tell which version an answer used?
Three signals make an answer verifiable. The source next to the answer names the document and the version, not only a file name. The answer distinguishes a current rule from a superseded one in words, not in a tooltip. And the link opens the specific version, so that a reader can compare the passage with the file.
Without these three, the assistant may be right, but a compliance manager cannot prove it, and a value that cannot be traced to a version is hard to defend in an audit.
What we do not know
We found no Microsoft documentation describing how any specific assistant treats minor versions or version history, so this chapter makes no claim about that. The test above is the only honest way to know for your tenant.
Indexing delay differs by product and configuration. If you run the check before the next indexing run, you test yesterday’s content.
Duplicates outside the library, such as PDF exports in project folders or mail attachments, are not covered by versioning at all. Version labels help only where the file lives in one place.
Our own measurements come from a demonstration environment with a sample company, not from a production tenant, and not from libraries with hundreds of versions per file.
How KSJ does it
In Answergrove, our assistant for Microsoft 365, only the current version of each document is indexed and searched by default. Earlier major versions (1.0, 2.0, 3.0 and so on) can be indexed on request; it is a per-installation setting, off by default. Minor versions and versions whose text is identical to a later one are skipped.
When an earlier version is used, the answer marks it as a previous, superseded version, and it is shown only to a person who may open the current file. Each source next to the answer names the document, the page and the version.
In our demo environment with the sample company Contoso, measured on 20 September 2026, the Quality Manual has version 4.0 and a history of 3.0, 2.0 and 1.0. With earlier versions switched on, 3.0 was indexed and 2.0 and 1.0 were skipped because their text was identical to a later version. A normal question was answered only from 4.0.
With the option “Search previous versions too” ticked, the answer said the review cycle is now 12 months, shorter than the 24-month cycle in version 3.0, and showed a second source labelled “version 3.0 (previous version)” linking to the version history.
For a quality manager who maintains ISO 9001 procedures in SharePoint, this applies familiar document-control thinking to the index and to the answer: see how Answergrove shows the version behind an answer.
Drafted with AI assistance, checked against the cited Microsoft sources and approved by Kaspars Jurjāns.
References
- ^ a b c d e “How versioning works in lists and libraries” (opens in a new tab). Microsoft Support. Retrieved 17 November 2026.
- ^ a “Enable and configure versioning for a list or library” (opens in a new tab). Microsoft Support. Retrieved 17 November 2026.
- ^ a “Set default organization version limits – SharePoint in Microsoft 365” (opens in a new tab). Microsoft Learn. Retrieved 17 November 2026.
- ^ a “Set version limits for a document library – SharePoint in Microsoft 365” (opens in a new tab). Microsoft Learn. Retrieved 17 November 2026.
- ^ a b “List versions – Microsoft Graph v1.0” (opens in a new tab). Microsoft Learn. Retrieved 17 November 2026.

