Skip to content
Skip to main content
Cloud Services Technical Explainer

Does file ownership prove authorship?

No. Ownership proves the service assigned control of the cloud object to an account or organisation. Authorship concerns who created the relevant content, which may involve different people, versions and systems.

Ask which authorship question matters

A document may contain an imported template, text from several collaborators, automated fields and later edits. “Who authored the file?” is often too broad. Identify the passage, image, calculation or version relevant to the investigation.

Then separate:

  1. who first created or uploaded the object;
  2. who supplied the relevant content;
  3. which account or process saved the change;
  4. who controlled that account or process; and
  5. who currently owns the object.

Ownership can change without content changing

Organisational policy may assign employee files to the tenant. Administrators can transfer ownership after offboarding, and moving or copying an object between workspaces may create a new owner. None of these events means the recipient wrote the existing content.

Conversely, a non-owner with edit permission may author a substantial revision. Collaborative editing and detailed version history are therefore more relevant than the owner label.

Attribute the specific change

Version or revision records may identify the account associated with a change. Session and device evidence can connect that account to a person; communications and distinctive content may provide independent corroboration.

State each supported proposition separately: “Account C-54119 owned the object” and “Account C-77503 saved paragraph 12 in version V-19” are different findings.

In OneDrive, organisation TEN-4 owns the drive containing briefing.docx. Dave's account C-77503 uploads object OBJ-4407; Priya's account C-66308 proposes paragraph 12; editor C-54119 accepts it before version V-19. The owner, uploader, proposer, accepter and person responsible for the final words are not automatically the same.

Test the specific authorship proposition
EstablishedThe records can distinguish control, upload, proposal and acceptance for the relevant content.
Still openWho controlled each account and whether the proposed words originated elsewhere.

The next useful comparison is the exact changed range and suggestion record against version content, account sessions, device activity and communications showing the wording's provenance.

Current Microsoft version-attribution example - checked 3 September 2026

Microsoft Graph currently exposes lastModifiedBy for a driveItemVersion. That is useful service-level attribution for the version, but it should be kept separate from drive ownership and from paragraph-level authorship where collaborative revision data says more.

The point to remember

Ownership identifies control, not creative responsibility. Attribute the relevant content through its version, recorded actor, session and corroborating evidence.

Reference: CLD-072Cloud Services