Additional assignment-related features and issues within Microsoft Teams for Education
Version history for student documents in Teams assignments is provided by SharePoint/OneDrive versioning. Version history does not “disappear” per document arbitrarily; instead, it is governed by the versioning and retention configuration of the underlying SharePoint/OneDrive library and by how often Office/AutoSave creates versions.
Key behaviors relevant to authenticity tracking:
- Version history is not a keystroke-by-keystroke log
- Version history in OneDrive/SharePoint captures versions periodically, not for every small edit.
- With AutoSave on, a new version is typically added about every 10 minutes during an editing session, not for every sentence or minor change.
- As a result, some short editing bursts may be “rolled up” into a single version, which can look like history has “reset” or skipped steps.
- Version history can be restored but not expanded retroactively
- For files stored in OneDrive/SharePoint (as used by Teams assignments), earlier versions can be viewed and restored:
- From the document library: right‑click the file → Version History → choose a version → Restore.
- From within Word/Excel/PowerPoint: File → Info → Version History, select a version, then Restore.
- Restoring a version makes that version the new current version; it does not recreate missing intermediate versions.
- Library-level versioning settings control how much history is retained
- SharePoint/OneDrive libraries can be configured to keep a certain number of versions or to prune older ones.
- If limits or retention policies are applied, older versions may be deleted, which can appear as if history has been reset.
- To maintain authenticity evidence, ensure versioning is enabled and configured appropriately on the underlying SharePoint/Teams document libraries.
- Practical steps for your scenario
- For affected assignments, open the underlying document library (in SharePoint) and check Version History on a sample student file to see what remains.
- If versions appear to be missing across all students’ work, review and adjust the library’s versioning and any retention policies so that sufficient history is retained for academic integrity checks.
- Where versions still exist, they can be restored using the Version History tools described above, but any already-pruned versions cannot be recovered via standard versioning.
References: