Table of contents
At a glance
Does Microsoft Purview Audit provide an adequate GxP audit trail for SharePoint?
Purview Audit alone does not provide the GMP change evidence considered here. A file activity event can report that content or properties changed without showing old and new text or cell values or the reason for the change. Annex 11 section 9 calls for a documented reason for changes to or deletion of GMP-relevant data. Link relevant activity events to content versions, decisions and controlled retention. Test the combined evidence against the critical events in your process.
Define the question before choosing a log
Start with a technical question: Who modified the content of an SOP, who authorized its effective implementation, and which version was in effect on the day of batch release? These questions require distinct pieces of information. An access event can verify user access. A file version can demonstrate the content of a specific version. A release certification documents the responsible decision. None of these elements should be considered a substitute for the others without thorough verification.
Define the critical events within your document process. This may include changes, deletions, release, recall, permission modifications, and administrative interventions. Determine the required scope based on actual usage. A general "record everything" approach is difficult to audit and does not address the underlying professional context. Annex 11 and PIC/S provide the framework for traceability and review; the specific coverage matrix serves as a practical implementation tool.
Four pieces of evidence with different purposes
Distinguish file contents and versions, document metadata, workflow decisions, and service-related audit events. SharePoint and Microsoft Purview are not interchangeable terms. The Microsoft documentation describes numerous file, list, permission, and administrative activities. The specific events available in the actual setup and the context associated with each must be verified based on the deployed service and license scope.
An "File modified" event does not automatically capture both the previous and current versions of a section. A version history alone does not necessarily clarify the technical or scientific rationale for a change. A separate approval workflow must establish a clear and explicit linkage to the affected document version. If only the file name and current link are stored, subsequent renaming or modification of the file may obscure the connection, even though all components remain technically accessible.
Lifecycle coverage matrix
Assign each event the available evidence source, required information, and known limitation. Consider all actually used pathways: browser, Office client, synchronization client, automation, and administrative actions. A successful test in the browser interface does not automatically establish equivalent evidence for an interface. The technical pathway is particularly relevant when an application operates under a user's name.
Microsoft specifies a context of app@sharepoint for certain SharePoint activities. Therefore, evaluate whether the triggering identity and the professional authorization remain traceable. A technical actor is not inherently erroneous, but must not appear as personally responsible approver without substantiation. Also document temporal delays in the availability of audit events. The expected researcher window will be derived from current documentation and internal testing.
| Fact event | Information needed | Possible source of evidence |
|---|---|---|
| Modify SOP content | Previous and new status | Controlled file versions |
| Make effective | Deciders, timing, exact version | Release process and document status |
| Delete file | Affected object, actor, timestamp | Purview Event and Retention |
| Extend access rights | Affected access and reason | Administrative event and request |
| Automation changes status | Technical actor and trigger | Flow-Proof and Audit Event |
| Search historical record | Then valid content and release | Linked historical investigation |
Example: Revision 4 becomes effective
In this example, an SOP is updated to include a new cleaning instruction. Author A edits revision 4. Reviewer B approves it, and the person responsible makes it effective on a specified date. Three months later, an employee must show which revision applied to a particular operation. The evidence must identify the content, version, approval and effective date. Downloading the current file cannot establish which version was in effect at the time.
First, verify the normal workflow using an independent reference. Following approval, modify a critical section and assess whether the process maintains control over this change. Add a renaming, a time shift, and a denied access event. A clear and logical connection is expected; identical technical datasets across protocols are not required. Distinguish between missing data, incorrectly configured filters, and unavailability of logging before concluding a finding.
Storage: Specifically verify license and guidelines
The retention of audit events depends, among other factors, on license, service, event, and active policy. Microsoft differentiates between Audit Standard and Premium, as well as additional options for extended retention periods. Therefore, do not adopt a generic standard retention period from a quotation or an outdated screenshot. Verify which users perform the relevant actions and which policy is actually applied to these events.
Determine the required time period from the affected records and applicable requirements. Document storage and audit log storage can be configured separately. The fact that an SOP is still available does not prove that its required change history remains available for as long. Evaluate a required export or other storage solution including integrity, completeness, access and research. A regularly filed CSV file is not yet a reliable archive without these controls.
A review requires a specific technical question
Define which events are regularly or occasion-specificly reviewed. The scope aligns with risk and process considerations. Critical modifications to active documents require a different evaluation approach than a routine read-only access. A review must demonstrate who performed the review, who assessed the findings, and what corrective actions were initiated. An exported log without evaluation presents only a data collection.
Review the filters and reports used. Incorrect time zone, incomplete object designation, or missing activity type may obscure relevant events. Therefore, an empty hit area should not automatically be interpreted as "no change." Use known positive control events to validate the search criteria. When analysis is automated, evaluate the associated logic and any changes to event schemas. Responsibility for assessment remains clearly assigned to operations.
Consider administrative interventions and restoration actions
Consider who has authority to modify versioning, permissions, retention, and audit configuration. Broad administrative rights may be operationally necessary; their assignment and use must be supported by appropriate controls. Verify that a reviewer can independently access necessary information. A work instruction that designates the same administrator as the sole controller of their own actions should be critically evaluated.
Restoration, migration, and account changes can influence historical relationships. Test a representative restoration scenario with content and context. Is the approval of the correct version properly linked? Can former employees still be clearly identified? The goal is not a artificially immutable system, but a controlled lifecycle. Changes must not inadvertently destroy the required evidence of validation. Remaining limitations must be documented with regard to their process impact and evaluated prior to release.
Event-based decision making for suitability assessment
The outcome may represent adequate coverage, targeted enhancement, or the selection of an alternative document architecture. Justify the decision for each critical event. "Microsoft 365 is compliant" is not a reliable conclusion for a customer-specific SOP process. Similarly, a protocol boundary alone does not automatically imply that SharePoint is unsuitable for any GxP purpose.
Provide the coverage matrix, configuration, test events, retention decision, and review rules to operations. Identify triggers for a reevaluation: license change, new flow, additional library, modified roles, migration, or relevant product change. Quality is demonstrated by the ability of a subsequent reviewer to reliably reconstruct the required justification. A comprehensive audit export lacking a clear and understandable link to the document does not meet this objective.
Sources: [1]
Project experience and collaboration
Reconstruct a document change from the available evidence
Document owners prepare a controlled content change, then locate the evidence for it. We compare the Purview event, the affected content version and the business decision to establish what a later reviewer can explain. Where the relationship is adequate, we define retrieval and review. Missing content or reasons for change need a suitable addition. With IT, we agree permissions and retention so the evidence remains usable after editing is complete.
Frequently asked questions about SharePoint logs in GxP
Does Purview capture the previous and current content of every Excel cell?
No. FileModified indicates a change to the file's content or properties. Microsoft logs no further FileModified events for the same user and document within the next five minutes; extended editing sessions may be aggregated as a FileModifiedExtended event. Such an entry does not constitute a cell change log. The specific values that were changed must be traceable through appropriate content versions or additional records. Verify that these records provide the level of detail actually required for your process.
Sources: [3]
Are audit logs retained for as long as the SOPs?
Not automatically. Document and audit log retention may follow different rules. Review active policies, user licenses, and event types. The required historical context must remain available throughout the justified retention period; a long document retention period alone does not establish this.
Sources: [4]
Is a technical user permitted in the audit log?
Automations can run under a technical identity. The decisive factor is whether action, triggering order and responsible decision are sufficiently comprehensible. A technical action must not be issued without appropriate proof as personal approval of an employee.
Must every file access be reviewed in a GxP context?
The scope of the review will be determined by process and risk. Relevant changes, deletions, or administrative interventions may have a different impact compared to routine read accesses. Specify the concrete review questions, selection criteria, and escalation procedures. A universal review frequency cannot be derived from this.
Sources: [2]
Is a monthly CSV export from Purview sufficient?
An export can be part of the concept. However, completeness, integrity, assignment, storage, and future retrievability must be assessed. The file must also be actually evaluated when it serves the review process. Exporting and professional review are two distinct activities.
When should SharePoint be supplemented with a specialized QMS?
If necessary process control, historical traceability, or operating rules cannot be adequately managed within the intended architecture, compare specific requirements and overall effort. A specialised product also does not replace configuration validation or evidence of appropriate use.
Sources and review date
As of October 14, 2026. Regulatory classification and manufacturer responsibilities are separately documented. Examples, test matrices, and templates are standalone reference tools; they are customized for actual usage purposes.
- European Commission: EU GMP Annex 11, Computerised Systems (2011)Current version as per EudraLex inventory as of 14.10.2026. Application, risks, operation, and data lifecycle; specific testing proposals are derived independently.
- PIC/S: PI 041-1, Good Practices for Data Management and Integrity (2021)Inspection Guidance on Data Integrity; in particular electronic data, transmission, access, and review.
- Microsoft: Audit log activitiesService-related events and SharePoint app context; no complete cell line derivation proven. Reviewed on 14.10.2026.
- Microsoft: Manage audit log retention policiesStorage depends among other factors on license, active service, event, and guideline. Reviewed on 14.10.2026.
Sources checked: .
How we can support you
Daniel Herrmann Consulting combines professional assessment with hands-on work on the specific system. During the first meeting, we clarify your intended use, existing documentation, and the next most appropriate action step.
- Computer system validation →
Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

