Practical guides · Practical guide

Microsoft 365 for GxP: defining a specific validation project

An SOP sits in SharePoint, the team works in Teams and Power Automate sends the approval request. Which part should validation cover? Trace the workflow and its records, then define the test scope, where external support will help and who will own the process afterwards.

Table of contents

At a glance

How do you plan GxP validation for Microsoft 365?

Start a Microsoft 365 GxP validation project by identifying a specific process and its authoritative records. Describe the services, tenant, configuration, roles and data flows involved. Supplier information can support parts of the assessment. Determine what evidence the configured workflow still needs, and plan tests, change control, incident handling and retention. A subscription or general cloud assurance record does not establish suitability for the intended use.

  • "Microsoft 365" alone does not constitute an adequate validation scope.
  • File, release qualification, notification, and signature are distinct forms of evidence.
  • License, configuration, and actual service scope must be clearly defined.
  • The validated workflow requires a responsible operating organization.

From Document Process to Inspection Task

For example, describe the development, review, approval, and provision of a Standard Operating Procedure (SOP). Specify which document serves as the primary record at each stage. A link within a message is not automatically equivalent to the approved version. Similarly, a notification must not be considered a complete and approved record without proper evaluation.

Do you understand the process limits: Who creates, checks, decides and uses the result? Which version must be comprehensible later? What tasks remain outside of the considered process? Thus, a general platform designation becomes a concretely verifiable application. For other GxP areas as a human medicine GMP, the regulatory framework has to be supplemented appropriately.

Sources: [1] [2]

Capture services, configurations, and identities

Prepare a concise inventory of actually used components. This may include SharePoint libraries, Teams access, Power Automate workflows, identity management, and associated applications. Additionally, identify the relevant tenant, intended user groups, and operational responsibilities.

Microsoft states in its GxP documentation that there is no GxP certification available for cloud service providers. The outlined qualification guidelines for Office 365 describe shared responsibilities and recommended customer controls. Verify the version and scope of the currently available documentation, as well as appropriate audit information; a general certificate list does not validate your process.

Annex 11 No. 3.1 requires formal agreements and clearly defined responsibilities for relevant services. No. 3.2 identifies competence, reliability, and a risk-based audit decision. No. 3.4 addresses the availability of relevant quality and audit information for inspectors. Assign manufacturers, implementation partners, and internal operations separately. Verify what specific service and contractual basis are actually agreed upon.

Sources: [3] [1]

Further reading:

What should a record actually demonstrate?

Distinguish a process decision from its technical representation. “Document approved” may mean only that a status field was set. Check the actual workflow to establish whether the authorised person made a traceable decision on the correct version. A success entry in an automation log does not establish that decision.

Proceed with the matrix, identifying the statement your process requires at each step and what remains unresolved. Whether the mentioned functions are actually available and properly configured within your tenant will be verified at the respective site of use.

What should a record actually demonstrate?
SubjectProcess questionReview the own workflow.
Document Which version was evaluated? Identity, version, and reference of the decision
Role Who was authorized to create, review, or approve? Effective permissions and deputy arrangements
Process What decision was made? Transitions, error cases, and traceability
Message Was a notification sent, or was a decision documented? Significance and relationship to primary record
Retention What information remains usable later? Document, context, traceability and authorized access
Change Which new system affects the process? Assessment, appropriate testing, and controlled implementation

Sources: [1] [2]

Further reading:

Define roles and organise collaboration with external parties

During project planning, technical process ownership, tenant administration, and concrete implementation must align. An administrator can assign permissions. However, which role is authorized to decide on a specific quality process must be clearly defined from a technical standpoint. External advisory services can assist in this clarification; internal responsibility and evaluation remain explicitly governed.

Arrange concrete results for a service provider: process description, evaluated configuration, requirements, suitable tests and handover. Determine the necessary access and the permitted use of data. A general access to the entire tentant is not a necessary standard requirement for each test. Permissions should match the task.

Sources: [1] [4] [5]

Perform appropriate tests on the complete process flow.

Alongside the normal workflow, plan for relevant failures and exceptions. These may include a rejected review, a changed document version, an unauthorised person or an interrupted automated step. Set the expected response before testing.

In particular, assess the interrelationship between the services in use. If a workflow references a document version, it should remain evident whether that version has been modified subsequently. In the event of a transfer failure, your team must establish an appropriate handling of the open action. The extent of the review shall follow the specific implementation and its impact; it does not arise from a comprehensive list of all Microsoft 365 functionalities.

Sources: [1] [6]

Further reading:

Planning example: A SOP release across multiple services

Suppose a company edits an SOP in a document library and starts a review workflow. Before testing, agree which version is reviewed, who may decide and what evidence must remain. In one test, change the document during review. In another, attempt the action with a person who lacks authority.

For the planning example, define how individual cases shall be handled, and compare this with the actual configuration. Depending on the outcome, a clearer process rule, a configuration change, or an alternative technical solution may be appropriate. Whether an approval as an electronic signature is suitable must be assessed based on the specific implementation.

Further reading:

Consider changes and ongoing maintenance from the outset

A cloud project does not end with the first successful execution. Identify who evaluates changes to libraries, roles, workflows, and associated services. Also consider changes introduced by Microsoft: the Notification Center announces new and updated features along with required actions. Assign viewing of these notifications to a specific role and document whether a message relates to a GxP process and what preparatory steps follow. Even a minor configuration change can impact the validity of a compliance assertion. The response depends on the actual impact.

In addition, maintain a clear approach to how deviations, open activities, and required records are managed. A service provider should assign these responsibilities to the intended operational roles. Not every change necessitates a full revalidation. However, without a proper assessment, it remains unclear whether the previous validation evidence remains applicable to the current state.

Sources: [1] [7]

Further reading:

Takeover of existing data and subsequent exit

During introduction, existing documents and their interrelationships may be carried over. Describe which information must remain available and how its usability is verified. Simple file transfer does not automatically address questions regarding version, status, and prior decisions.

Consider a potential future change of the solution. What documentation must be provided in clear and understandable form? Who is familiar with the necessary interrelationships? How is a representative data retrieval verified? These questions already help during the project to properly define the long-term retention requirements. They do not establish a general, fixed retention period for all Microsoft 365 data.

  • Leading records and required context identify.
  • Associate roles, rights, and representations with the process.
  • Select justified normal, error, and change cases.
  • Define responsibility for operations and subsequent configuration changes.
  • Describe migration and retrievable data as separate outcomes.

Sources: [1] [2]

Further reading:

Project experience and collaboration

Define the Microsoft 365 process you need to assess

With your process owners, we follow a real Microsoft 365 workflow, such as drafting and approving an SOP. We identify the services, roles and records involved and review the evidence already available. An existing SharePoint configuration may need different checks from a new automated approval workflow. With QA and IT, we use the findings to define the tests and the tasks needed to run the process afterwards.

Frequent Questions on Microsoft 365 in the GxP Environment

Must the entire Microsoft 365 tenant be validated?

The scope must be justified based on the intended use and relevant dependencies. A specific document or data process does not necessarily require the same evaluation as any other tenant function. At the same time, critical shared services and controls must not be overlooked. Therefore, clearly define the actual process and system boundary required.

Sources: [1]

Is approval within a workflow automatically an electronic signature?

No. Annex 11 No. 14 specifies the same effect as handwritten signatures within the company for electronic signatures in the EU-GMP framework, the permanent link to the data set as well as date and time. An expiration permit does not fulfil these characteristics solely by their name. Check the concrete implementation. Additional requirements from Part 11 are to be classified in the corresponding US scope.

Sources: [1] [8]

Is the manufacturer's documentation sufficient for our application?

Manufacturer information can support key aspects of the evaluation. However, they do not automatically reflect your configuration, roles, or specific process rules. Assign each statement to the evidence that exists and identify where additional internal verification is required. The combination of evaluated manufacturer information and appropriate internal assessments is essential.

Sources: [1]

What role does the license play?

Microsoft specifies a default log retention period of 180 days for audits (standard). A longer retention period up to one year requires the responsible party to hold an appropriate E5 or equivalent license; retention for ten years additionally necessitates the corresponding add-on. The applicable guideline and the specific data set type must also be verified. Therefore, please clarify which logs are required for how long and whether the license and configuration actually cover the required retention period.

Sources: [9]

Can Copilot be validated within the same project?

A AI deployment must have a clearly defined specific purpose, relevant data, identified risks, and appropriate controls. It shall not be considered validated solely because the broader Microsoft 365 process has been evaluated. Additional professional boundaries apply to generative AI. A dedicated and distinct validation task may be required.

Sources: [1] [10] [11]

What should an external partner deliver at the end?

The agreed results are expected to be provided with date reference, evaluated open items, and clear usage conditions. Your team also requires the necessary operational and change authorisation capabilities. The handover should demonstrate through a representative process whether internal responsible parties can understand and continue the process and its associated documentation.

Sources and review date

Primary source date: 17 October 2026. Microsoft's responsibility model serves as a technical guidance and does not constitute a comprehensive regulatory or contractual release. Specific functionalities depend on service, license, configuration, and environment. Annex 22 is referenced exclusively as a consultation draft from 2025. The article describes an independent planning approach and does not represent a general GxP certification of Microsoft 365. EU GMP statements relate to human medicinal products (EudraLex Volume 4). The linked eCFR text pertains to 21 CFR Part 11.

  1. European Commission: EU GMP Annex 11, Computerised Systems, January 2011 revisionHuman medicinal products – GMP; in particular, §§1–4, 7, 10–13, 16–17; specific application for each section.
  2. European Commission: EU GMP Chapter 4, Documentation, January 2011 revisionControlled documentation and records; official EudraLex entry with original chapter.
  3. Microsoft: GxP – Qualified Approach and Shared ResponsibilityManufacturer information and available qualification guidelines; no GxP certification of the cloud provider.
  4. European Commission: EU GMP Chapter 7, Outsourced ActivitiesOutsourced GMP-related activities, suitability, responsibilities, agreements, and monitoring.
  5. Microsoft Learn: Shared responsibility in the cloudTechnical responsibility boundaries for Cloud/SaaS; no official authorization required for customer usage.
  6. ICH Q9(R1): Quality Risk Management, official text from the European CommissionRisk-driven decisions, appropriate formalities, and handling of subjectivity; own matrices are implementation proposals.
  7. Microsoft: Track changes in the Microsoft 365 message centreManufacturer notifications received as input into the company's change evaluation process.
  8. eCFR: 21 CFR Part 11, Electronic Records; Electronic SignaturesFDA-related records and signatures within the actual scope of application; no blanket EU requirement.
  9. Microsoft: Audit logs and retention policiesStorage dependent on license, dataset type, and guideline; no regulatory universal deadline.
  10. European Commission: Annex 22 Artificial Intelligence – consultation draft 2025Draft, not considered a mandatory requirement; generative AI explicitly not treated as a released core application.
  11. European Commission: 2025 Consultation on Chapter 4, Annex 11 and new Annex 22Draft consultation status and assignment of designs; no evidence of coming into force.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Clarify a specific data or document pathway.

Describe a relevant process and the services utilized for it. Useful information includes details on roles, key documentation, and known open items. This enables the professional boundary definition prior to a comprehensive engagement.

  • Cloud and SaaS validation →

    Maintain the validated state of cloud and SaaS systems as suppliers issue new versions. We define the boundary between your responsibilities and the supplier’s and agree how each release will be assessed.

Send a project enquiry Customer testimonials →