Table of contents
At a glance
How can you use SharePoint Online for controlled SOPs in a GxP process?
SharePoint Online can support controlled SOPs. Demonstrate that the configured solution handles drafting, review, approval, effective dates, use and retention. Version history, content approval and retention serve different purposes. Assess how they are configured, alongside permissions, connected flows and organisational controls. Microsoft documentation supports the assessment, but your SOP process needs its own evidence.
- The currently valid SOP version at the workplace is the central review result.
- Permissions to edit drafts, approval status and the effective date must be consistent.
- Version history is not an automatic audit trail; approval is not an automatic signature trail.
- Retention, audit logs, and flows must be verified against their actual licenses and limitations.
Define the intended SOP process and the system boundary
Start with a verifiable scope of use. Example: "SharePoint Online manages the released manufacturing SOPs for Site A and provides them to authorized personnel on the job site." Also identify the documents that fall outside this scope. Batch records, training certifications, and signed forms are separate documentation types; their requirements cannot be unreviewedly derived from a SOP library.
For GMP-related computerized activities, EU GMP Annex 11 is a key reference. Chapter 4 addresses document control. Part 11 should be classified based on the relevant electronic records and the underlying FDA record-keeping requirements, known as the Predicate Rules. The use of SharePoint alone does not determine the scope of applicability.
Map the journey of a SOP from the editable original to the work instruction at the point of use. Integrate Microsoft 365 identities, SharePoint libraries, Power Automate flows, and where applicable, signature or training systems. Separate vendor operations, tenant administration, and subject-matter document ownership. Microsoft explicitly outlines this shared responsibility. A generic GAMP category for SharePoint does not replace this distinction.
Link document status, version, and validity unambiguously
A SOP must have a professionally unambiguous identity. As a planning approach, suitable elements include document number, title, responsible department, revision identifier, release reference, validity date, and reference to the superseded version. Define which information is binding and who is authorized to amend it. Separate file versions and professional SOP revisions may follow different governance rules.
Chapter 4 requires clear identification, approval, signature, and date by authorized personnel; the effective date must be specified. Therefore, a state model is recommended for implementation. "Approved" and "valid at the workplace" may differ, for example, if prior training must be completed. The following table represents a business requirement, not a description of a pre-configured SharePoint function.
| State | Technical Regulation | Evidence in test |
|---|---|---|
| Draft | Processing by named authors; not a valid work document | Reader sees no unpublished draft content |
| Under review | The inspection pertains to a specific version. | Content, version reference, and decision can be linked. |
| Approved, not yet valid | Commencement is pending defined prerequisites | Workplace continues to show the current version |
| Valid | Approved work instruction is clearly accessible. | Call provides document number and valid revision |
| Superseded | Previous version remains accessible according to retention concept | Historical use is not conflated with current validity. |
Sources: [12]
Review draft rights with genuine user roles
The SharePoint content approval and draft security settings determine which users can view unapproved content. Microsoft defines this through different user groups. Activation of approval alone does not guarantee effective protection against viewing drafts. Therefore, verify the actual combination of library settings and access rights.
Use separate test accounts for readers, authors, reviewers, and administrators. A successful test performed by an administrator does not constitute evidence of reader view access. In addition to the home view, verify direct document links, intended search paths, and permitted access from integrated applications. A filtered view should not be considered proof of access restriction.
When dealing with an already filled library, special attention is required: According to Microsoft, existing elements are assigned the status "Approved" upon subsequent activation of content approval. This technical status does not indicate that a prior professional evaluation has been conducted. Assess existing documents prior to the transition and subsequently verify the status, authorized readers, and version assignments.
Sources: [2]
Content approval, modern approval, and electronic signature differ
In addition to content approval, Microsoft also documents modern permissions for lists and libraries. The support page expressly declares that content approval is not integrated with these modern permissions. Therefore, name the function used in requirements and tests. An identical or similarly labeled status field is not a proof of the same behavior.
In modern approvals, stored content changes may lead to the suspension of an ongoing approval. Microsoft also outlines the impacts of metadata modifications and differing historical view perspectives. Review such cases at the implemented function. A decision must be clearly justified based on the actually reviewed content.
A content approval alone does not constitute validation evidence of a Part 11-compliant electronic signature. When electronic signatures are required, the evaluation must include, among other factors, identity, signature intent, timestamp, and permanent association with the electronic data set. Applicable requirements for electronic signatures must also be considered. A login or click-to-release action alone is insufficient as conclusive proof.
First, outline the meaning in the process of the signature. Then evaluate the specific signature solution, including integration, exported display, and retention. An external signature product also requires a full workflow review.
Plan versioning, storage, and deletion separately
SharePoint can manage version histories based on configurable retention limits. Microsoft defines both automatic and manual retention limits; specific cleanup actions permanently delete versions and bypass the recycle bin. The mere availability of previous versions therefore does not constitute a permanent archive. Verify which versions should be retained for how long and what controls govern changes or deletions.
Microsoft Purview provides retention policies and retention tags. For SharePoint, Microsoft describes features such as the Preservation Hold Library and its integration with document versions. The impact depends on the applied rule. A policy, a tag, and the declaration as a record must not be equated arbitrarily.
Document the scope, start date, duration, handling of retired containers, and actions at the expiry date. Also review exceptions and rights to modify the rules. The available functionality and required licensing must be confirmed for tenant and user; a Microsoft 365 license designation alone is insufficient as an architectural decision.
Conduct a targeted recoverability assessment: A selected historical SOP shall be available with readable release reference. Additionally, evaluate backup, restoration, and the scenario of a system change. Evidence of appropriate documentation is required for storage, restoration following an interruption, and professional archiving.
Test Power Automate until the technical final state is achieved
In the Microsoft example for document approval, Power Automate uses the content approval status via the SharePoint connector. The ETag serves as a reference to the respective element version. Microsoft notes that this action is required for documents and pages. This represents a specific technical dependency; it is not an electronic signature verification.
Review a specific change after the submission of the approval request. Can the response still be used for the original version? How does the process prevent or detect the release of content that has since been updated? Receipt of an email response does not necessarily confirm the correct final status in SharePoint.
For documented automated, scheduled, and immediate Cloud workflows, Microsoft specifies 30 days as the maximum runtime for a single run, including pending approvals. The regular run cycle also has a limited retention period. Therefore, it is not inherently suitable as a long-term release justification.
Define escalation, rejection, termination, repetition, and compound failure. Identify flow owners and technical linkages. When connected to a training or signing system, compare document identifier, revision, decision, and timestamp at both ends. Verify both a repeated message and a failed status return.
Maintain the evidence of a SOP release on a permanent basis
A robust traceable justification addresses three key questions: What content was reviewed, who made the decision, and when did the decision become valid? As a professional recommendation, the document preparation, release decision, and effective date should remain clearly linked to a single, unambiguous reference. Define which data are decisive and ensure that a reviewer can clearly understand and trace the relationships at a later time.
Version history, approval information, and Microsoft Purview audit logs must be evaluated separately. Microsoft specifies different retention requirements and licensing conditions for audit logs. Therefore, do not infer long-term availability—such as multi-year retention—from a currently successful log search.
Develop a traceability matrix for critical events. This shall include changes to content or validity date, releases, deletion attempts, and modifications to relevant rights. For each event, verify the responsible party, timestamp, document reference, and available details. If a change justification is required, its capture and assignment must be explicitly documented. Responsibility, review trigger, and actions to be taken in case of anomalies shall be incorporated into the operating procedure.
Test example: Modify a SOP during review
The following example describes technical requirements and expected test results, not the intended behavior of SharePoint. Assume that SOP-017 Revision 3 is currently valid. Revision 4 shall include a new cleaning procedure and shall only be implemented after completion of review and formal approval, with a defined date of implementation.
As prerequisites, the library configuration, the selected authorization function, the flow state, and four test roles are documented. An electronic signature has not been demonstrated here; if it is part of the intended process, a separate signature test is required. For each step, the initial version, user, action, observed final state, and reference to validation evidence are recorded.
| Step | Action | Expected result |
|---|---|---|
| 1. Draft | Author prepares Revision 4; Reader opens the workbench access | The reader receives the currently valid revision 3; the draft is protected pursuant to rights assignment |
| 2. Testing | Author submits a clearly referenced version | The reviewer can precisely identify this content using document identifier and version reference. |
| 3. Amendment | Author modifies the content during ongoing review | The previous request cannot release the amended content without notice; intended interruption or error is detectable |
| 4. Reconsideration decision | New version undergoes review and, if applicable, approval | Decision and required evidence relate to the new version |
| 5. Implementation | Defined prerequisites and validity date have been achieved | The proposed workplace call-up provides Revision 4; Revision 3 is identifiable as superseded. |
| 6. Disruption | Return status or connection fails | No unsupported validation; the responsible party receives the specified error message |
Demonstrate changes, inventory migration, and operation
Microsoft provides change notifications via the Message Center. Assign relevant messages from your SOP solution to: affected behavior, responsible party, assessment, and required review. Add your own changes to libraries, roles, flows, retention rules, and connected services. A static file version does not prove an unchanged overall process.
Maintain a manageable catalog of critical regression tests. Upon an update, select appropriate tests based on the impact assessment. During a migration of existing data, compare documents, metadata, valid versions, and release relationships. Unresolved gaps are evaluated; a new technical approval status does not replace a prior missing decision.
For operations, the Department, QA, and IT require a common handover procedure. It should include authorized administration, incident management, access changes, regular reviews, and recovery procedures. Outages are planned from a workplace perspective: What controlled contingency procedure is on standby, who activates it, and how is the return to normal operations documented?
- Proposed SOP usage, system boundaries, and applicable requirements are approved.
- State model, roles, and valid work instructions are clearly defined.
- Approval function and, if applicable, digital signature solution are clearly defined.
- Retention, deletion, verification, and licensing are assessed at the actual tenant.
- Tests link requirements to results, deviations, and a decision on usage.
- Procedures and responsible parties for the ongoing operation are defined.
Project experience and collaboration
Make the current approved SOP available at the point of use
For an SOP library, we check which version an employee can access at the workstation. With the document owners and IT, we trace a procedure from draft to approval, effective date and reader access. This identifies targeted changes to the existing library or requirements for a new workflow. Either approach must reflect your responsibilities, training processes and available software functions.
Frequent Questions on SOP Guidance with SharePoint
Is SharePoint Online approved for GMP document management?
SharePoint does not provide a flat-rate GMP approval for your SOP process. Microsoft expressly declares that there is no GxP certification for cloud providers. The decisive factor is whether your set-up solution can be proven to support the intended use. Evaluate and check rights, permits, storage and operational procedures.
Is the version history sufficient as a retrievable and auditable archive?
No. Version boundaries and cleansing activities may impact the availability of previous versions. Define retention requirements, protection against unauthorized changes, retrievability, and readable export. Evaluate the associated functions collectively. A visible version list alone does not meet these requirements.
Is a SharePoint content approval considered a Part 11 signature?
The content permission alone does not provide this evidence. First, it is necessary to clarify whether Part 11 and electronic signatures apply to the specific process. Then, identity, signature meaning, timing, attachment to the data set and other relevant controls on the actual solution are evaluated.
Sources: [13]
Do readers automatically only see approved SOPs?
Not automatically. Document approval, visibility settings for drafts, and the actually effective rights determine the reader's view. Verify these settings using an actual reader account via the intended access pathways. The process must also distinguish between approved and already in force documents when these states are temporally distinct.
Sources: [2]
What happens when the content approval is retrospectively activated?
Microsoft states that existing elements already receive the status "Approved." This does not provide evidence of a professional release or technical clearance of prior elements. Assess the existing document inventory prior to transition and subsequently verify the status, versions, and visibility for readers.
Sources: [2]
Are modern approvals equivalent to content approvals?
No. Microsoft documents features separately and refers to the lack of integration of content approval with modern approvals. Specify which functions your solution utilizes. When reviewing changes, also check ongoing requests, status fields, and available approval history.
Sources: [3]
Can Power Automate wait indefinitely for a release?
For the documented cloud flow types, the maximum runtime for a single run is 30 days, including pending approvals. Longer, process-specific workflows require appropriate design considerations. Escalations, terminations, and follow-up responses must be reviewed; permanent release documentation must be separately planned.
Sources: [9]
What is the correct retention period for SOPs in SharePoint?
There is no general SharePoint retention period applicable to all SOPs. Derive duration and start date from applicable documentation requirements, the supported process, and your documentation concept. Then review the specific retention configuration, including archived versions, deletion rules, and exceptions.
Does a Microsoft 365 license suffice for all required controls?
Must every Microsoft update be revalidated?
The scope of the test should follow from a documented impact assessment. Affected functions, own flows, interfaces and risks determine the selection. A reusable catalog of critical SOP processes facilitates this decision. Essential configuration changes belong in the same controlled change procedure.
Sources and review date
Primary sources reviewed on 6 October 2026. The Commission continues to apply Annex 11 and Chapter 4 in the 2011 versions. Microsoft documentation describes functionalities, not the release of a specific SOP solution. Tables, inspection sequence, and checklists are professional recommendations. The suitability of a specific system must be assessed based on its intended use.
- Microsoft Learn: GxP and Shared Responsibilities
- Microsoft Support: Content Approval and Draft Visibility
- Microsoft Support · Modern approvals in lists and document libraries
- Microsoft Learn: Version limits and data retention behavior in SharePoint
- Microsoft Learn: Retention for SharePoint and OneDrive
- Microsoft Learn: License requirements for Microsoft Purview
- Microsoft Learn: Retention Policies for Audit Logs
- Microsoft Learn: Document approval with Power Automate and ETag
- Microsoft Learn: Duration and Storage Limits of Cloud Flows
- Microsoft Learn: Prepare for Microsoft 365 changes using the Message Center
- European Commission: EU-GMP Annex 11, January 2011 version
- European Commission: EU GMP Chapter 4, Documentation
- eCFR: 21 CFR Part 11, particularly §§ 11.1, 11.10, 11.50, 11.70 and Subpart C
- European Commission: EudraLex Volume 4, current source list
Sources checked: .
Assess the SharePoint SOP process with Daniel Herrmann
Your point of contact is Daniel Herrmann. At Daniel Herrmann Consulting, we combine the assessment of GxP usage with specific documentation and testing activities. For your SOP solution, we first evaluate the current version in use at the workplace and the associated supporting evidence. From this, a mutually agreed testing and action plan is established; technical decisions and approvals remain the responsibility of your respective authorities.
- 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.

