Table of contents
At a glance
How do you assess Active Directory for GxP use?
Identify the business actions that depend on AD DS and document domains, group memberships, policies and application roles. Test whether access grants and revocations take effect under actual sign-in, replication and session conditions. Include traceable changes and evidence of restart. Where GMP applies, link infrastructure qualification to application-level evidence. The product name alone does not define the scope.
- AD DS and Microsoft Entra ID are independent services.
- The valid scope of use is required; a group list alone is insufficient.
- Nestling, replication and existing sessions can affect withdrawal.
- Upon restoration, previous right statuses must be professionally assessed and categorised.
1. Distinguish the directory service from the specialist process
Active Directory Domain Services, or AD DS, manages within Windows Server, among other things, users, computers, and domain resources. This is a distinct service from Microsoft Entra ID. This guide examines the on-premises domain environment and its impact on connected systems. An existing cloud synchronization expands the data chain under consideration, though it is not treated as an equivalent function herein.
GxP relevance arises, for example, when AD groups determine who is authorized to review results in a laboratory application. Therefore, start with the authorized function and trace back its permissions. Simply logging into a computer does not prove access to the correct procedure nor the exclusion of an unauthorized release. Local accounts or application-specific roles may also be significant.
Within the applicable human medicinal product GMP scope, Annex 11 distinguishes between validated usage and qualified IT infrastructure. This does not establish a fixed GAMP category for the product name. Define which infrastructure characteristics and application-specific access requirements must be demonstrated. Not every directory object requires the same level of documentation; however, commonly shared services remain relevant if their unavailability or modification impacts the considered process.
2. Maintain a verifiable domain inventory
The referenced Microsoft pages primarily list Windows Server 2025, 2022, 2019, and 2016 as applicable versions. These do not replace an existing assessment of your operating system, patch level, or supported functionality. Document domain controllers, domains, locations, trust relationships, name resolution, and the actually used login pathways. For a third-party service provider, their responsibility extends to these elements; the site alone does not establish ownership of responsibility.
Forest, domain, organizational unit, and security group are distinct structural components. An organizational unit can control the application of group policies and administrative delegation; however, it does not yet represent a professional review role. Document the assignment such that QA understands which technical component influences which business decision.
For an existing environment, a robust as-is capture is often more critical than a new standard form. Do exported groups and policies align with the authorized organization? Are there decommissioned applications retaining active groups? Can an external administrator modify settings without the process owner being notified? These findings determine the next review cycles. A version change additionally requires assessment of affected dependencies; a current product identifier alone does not suffice to address these questions.
3. Fully resolve all roles and nested groups
Microsoft distinguishes between security groups and distribution groups. Security groups may contain other groups in accordance with the respective group scope rules. Therefore, direct memberships should not be the sole basis for assessment. A user may retain the same authorization through an alternative path, even if the most visible entry has been removed. The question about the process is: Which individuals hold the effective role overall?
Separate approval by the process responsible party from the technical implementation. For each critical role, it must be clearly traceable which group path it generates, who is authorized to modify that path, and how an exception is evaluated. This constitutes a standalone work guide; Microsoft does not define laboratory roles or GMP releases for your organization.
The following mapping illustrates why a single screenshot from user administration rarely constitutes complete validation evidence. Information may be retained in existing documents, provided the relationships and content remain clear and up to date. Specifically, additional alternative login pathways and application maintenance responsibilities should be addressed. A technically restricted user must not perform the same action via a locally assigned role that remains active in the system.
| Level | Specific subject | What is being verified |
|---|---|---|
| Business process | Approved Tester Role | Responsible Person and Authorized Professional Competence |
| AD DS | Direct and nested memberships | Complete intended user group |
| Group Policy | Target computer and actual scope of application | Intended setting at the relevant workstation |
| Sign-in | User context and existing session | Effect of a change in the used access pathway |
| Business application | Assignment of the group to the inspection function | Permitted Action and Targeted Denial |
4. Group guidelines at the target check
A group policy directive links settings to permissions and a scope of application. Microsoft describes components within Active Directory and the SYSVOL directory. For your evaluation, it is essential to determine what actually takes effect on the relevant computer or for the specific user. The presence of a GPO only confirms a portion of the configuration.
Select a justified normal condition and a deviating target state. For example, a laboratory workbench should retain the same authorized access restrictions before and after a planned change of organizational unit. Assess the resulting configuration and the affected behavior. A test machine outside the scope of applicability might inadvertently overlook the actual error.
If two guidelines or an exception are relevant, the test must record the actual resulting state. Do not accept a flat-rate update time from a foreign structure. Changes to assignment, permission or setting are evaluated for their effects; the scope of the test follows the affected behavior. A successfully applied GPO also does not replace the role check in the application or the evaluation of its data records.
5. Include replication and meetings in the deprivation of rights
AD DS replicates directory information across a location-based topology. Therefore, changes and their impact across all relevant access paths must be evaluated separately. Investigate which domain controller serves authentication and which instance is relevant for the specific access scenario. The Microsoft documentation does not establish a general requirement for immediate consistency or a universally applicable synchronization interval.
Additionally, the user context includes Windows access tokens containing user and group identifiers. Applications may also employ their own session and authorization mechanisms. Therefore, it cannot be assumed that any ongoing session immediately loses its previous privileges upon a changed group list. The actual coupling must be known for the specific application in use.
Define the professionally appropriate end state for a role revocation. Review new applications and existing active sessions separately. If the process requires immediate suspension of a critical action, a subsequent directory reconciliation alone is insufficient as justification. Establish an appropriate controlled revocation pathway and validate its effectiveness. Such tests must be conducted in a coordinated environment and must not inadvertently impact an ongoing production run.
6. Example: Fully remove a reviewer role
The following example does not represent a completed product test. In a test environment, DC1 and DC2 provide two predefined login paths for laboratory use of LAB-01. Persons A, B, and C are authorized to view results. Persons A and B are initially authorized to perform review functions. The application maps these two functions separately to defined security groups. Additional local reviewer roles are disabled in the initial state.
Person B rotates to a new role and is to fully relinquish the reviewer responsibility while retaining read-only access. The pre-defined expected outcome following completion of the exit procedure is: all three individuals have read access, with only Person A performing the review. With three individuals, two actions, and two access pathways, twelve individual observations are generated. Eight permitted and four denied actions are expected. This figure applies exclusively to this specific scenario and does not represent a general minimum test requirement.
Before each table case, the same authorized role status and a new session are created; the access path used is recorded. Additionally, in a targeted error scenario, User B remains authorized through a nested group: the comparison must detect the incomplete revocation. A further case uses an open session prior to revocation and evaluates its behavior against the explicitly defined revocation procedure. Both additional cases are separately documented and not included in the twelve normal observations.
| Access route | Person | Read | Check |
|---|---|---|---|
| DC1 | Person A | Permitted | Permitted |
| DC1 | Person B | Permitted | Denied |
| DC1 | Person C | Permitted | Denied |
| DC2 | Person A | Permitted | Permitted |
| DC2 | Person B | Permitted | Denied |
| DC2 | Person C | Permitted | Denied |
7. Link technical logs to process records
A documented group change addresses a different question than the documented review of a laboratory result. For the authorization process, you need to establish the link between request, decision, implementation, and verified outcome. For professional competence, the recording of application usage remains critical. A directory log does not substitute for this linkage and is not an electronic signature attached to a result.
Annex 11 addresses the documentation of system access provisioning, modification, and revocation. The technical and organizational evidence required to support these activities is defined within the respective system. Verify that the necessary information is actually captured, remains accessible, and can be clearly interpreted and evaluated. The mere presence of an enabled logging mechanism does not constitute sufficient evidence.
For GMP records, consider relationships between records and controlled corrections. Define how to correct assignment to the wrong person while preserving the meaning of the earlier decision. Retention depends on purpose and applicable requirements. A generic Windows log period or a number copied from a template cannot justify retention across all records.
8. After restoration, reassign the permissions again
Microsoft states that a forest recovery restores domain objects to the state of a trusted backup. During this process, objects added after the backup and all subsequent modifications are lost, including interim group changes. Therefore, for a regulated access process, technical recoverability alone is insufficient: which later approved role changes are missing following the recovery?
A standalone example of a failure: the backup originates from the period prior to Person B's rollover. If this prior state is restored, the restart procedure must detect the interim changes and appropriately handle them prior to reauthorizing usage. The evidence must link the backup state, pending modifications, and the actual access verification in LAB-01. The mere operation of a machine alone would not constitute sufficient closure criteria.
Plan the approach jointly with the infrastructure provider and the affected functional processes. Consider secure recovery, reachable point of contact, dependencies, and required fallback procedures. Microsoft’s detailed recovery guidance is not a general instruction to reset a production forest for testing purposes. An appropriate test environment and protective measures must be defined in advance. Recovery objectives and test depth shall align with the specific risk; blanket time commitments are therefore inappropriate.
9. Preparation, participation, and resource requirements realistically planned
For a SME, it should be clearly defined prior to commencement of operations who is responsible for service management, who authorizes application roles, and who evaluates the impact. The infrastructure administration is familiar with domains and group policies, while the application owner is responsible for role mapping, and QA defines the technical requirements. An external IT partner can provide technical evidence; however, open responsibilities do not disappear as a result.
Several domains, sites, nested groups, undocumented exceptions and applications with local user management can increase effort. Limited test access and an unclear change history also matter. User count alone gives little guidance. Define the intended structure for a new deployment. For an existing one, reconstruct actual access paths and address deviations.
The following preparation checklist helps in defining the order specifically. It is not a general regulatory minimum action list. Existing, relevant documentation may be utilized; its currency and coverage must be demonstrable.
- Identify affected functional activities and their authorized roles.
- Capture domain controllers, versions, locations, and relevant registration pathways.
- Map direct, nested and local permission paths.
- Provide GPO scope and key exemptions.
- Name approval, withdrawal, and re-start procedures.
- Prepare safe test accounts, starting states and observable expected actions.
- Backup, change logs, and point of contact information available.
10. Finalize changes with professional technical impact
A new domain controller, altered group nesting, or a different integration of the laboratory application may trigger different validation checks. First assess which previously justified assumption is affected. When role mappings are changed, focus on permitted and prohibited actions; when a new site is introduced, access paths, replication behavior, and failure modes become critical.
For the final release decision, results, deviations, and remaining actions are consolidated. A technically error-free installation is a contributing factor, not automatically equivalent to the full technical justification. Conversely, a change does not require repeating all previous tests without rationale. Document which existing records remain valid and which new observations are required.
In ongoing operation, relevant faults, rights exceptions and changes should be included in the evaluation. Repeated unexplained deviations between approved role and application access deserve treatment other than a corrected spelling in a description. Keep an eye on the result: The correct person can perform the intended action, another cannot, and subsequent changes can be assessed in a controlled manner.
Project experience and collaboration
Verify effective permissions in the application
For a critical role, we trace approved group membership to an action the business application actually permits. With IT, we test revocation, nested groups and sessions that remain open. Better evidence may resolve an unclear mapping. If unauthorised access remains effective, the operations team must investigate its cause. We plan negative tests and a recovery case together. The evidence concerns actual access behaviour in your process.
Frequently asked questions about Active Directory
Must Active Directory be fully validated in a general or blanket manner?
The scope is determined by the intended use and the affected processes. In the appropriate GMP scope, infrastructure qualification and evidence for the application function are to be distinguished. A flat label for the entire directory service does not answer whether the right person in your application can perform the correct action. Define these requirements and their dependencies first.
Is AD DS the same as Microsoft Entra ID?
No. AD DS is the Windows Server domain service being considered here for on-premises domains. Microsoft Entra ID is a separate cloud-based identity service. In a hybrid environment, the actual usage transitions must be explicitly described. Evidence derived from groups or sessions in AD DS must not be unverifiedly used as proof of Entra roles or cloud application access.
Sources: [8]
Why is the distance from a single group not sufficient?
A person may retain access through other direct or nested memberships and applications may have local roles. Determine who still has effective access and test the actual action after revocation. Group scope and valid nesting depend on the AD structure. Not every possible combination is technically permitted.
Sources: [3]
Why might an existing session behave differently from a new login?
Windows uses access tokens containing user and group information. The specialist application may also maintain its own session context. Consequently, there is no immediate, general update of all existing sessions following every directory change. Compare both states against your established withdrawal procedure and consult with the application owner to determine which mechanism actually determines authorization.
How do we demonstrate that a group policy actually has an effect?
Assign the desired setting to a specific target computer or user and verify the resulting state and relevant behavior. Consider scope and exceptions. A saved GPO or successful configuration export alone does not prove that the required protection actually exists at the laboratory workbench.
Sources: [4]
Can the AD protocol replace the audit trail of the laboratory application?
It documents a different object. A change in permissions within the directory does not automatically indicate who has modified or approved a technical data record. Determine which records are required for access management and technical process control and how they interrelate. An electronic signature is not automatically generated solely by a successful domain authentication.
What additional checks are required when multiple domain controllers are in use?
Consider the actually used locations and access paths, as well as the impact of replicated changes. It is essential to determine whether the intended behavior is achieved under relevant conditions. A fixed general wait time cannot be inferred from replication documentation. Use targeted normal and out-of-specification cases instead of conducting extensive testing of each controller without relevant technical context.
Sources: [5]
Why should changes to rights be included in the restoration plan?
A restoration can revert to an earlier system state. As a result, role changes applied after the backup may be missing. Therefore, the restoration procedure should integrate the backup state with the relevant subsequent changes and assess critical application access rights. The manufacturer describes the technical recovery; its suitability for your specific process remains to be demonstrated separately.
What must be available prior to project start and who is involved?
Useful are a current system overview, approved roles, group paths, GPO assignments, application mappings, and secure testing capabilities. Infrastructure administration, application owners, and QA must collaborate; the IT service provider may also be involved. Missing documentation represents a planned workload item. Without a subject-matter expert, a reliable target state cannot be derived from technical exports.
What factors determine effort and subsequent revalidation assessments?
Crucially, the number of distinct authorization paths, locations, exceptions, associated applications, and the quality of existing evidence must be considered. Upon changes, it is assessed which assumptions and functionalities are impacted, potentially requiring either a targeted access test or a more comprehensive evaluation. Neither a fixed time window nor a one-size-fits-all full retest approach is suitable for every environment.
Sources and review date
Source date: 6 October 2026. Microsoft Learn documentation primarily applies to Windows Server 2025, 2022, 2019, and 2016; installed build, domain structure, and application integration must be individually verified. Tables and expected deviations are standalone reference aids.
- Microsoft: Active Directory Domain Services overview
- Microsoft: Understanding the Active Directory logical model
- Microsoft: Active Directory security groups
- Microsoft: Group Policy overview
- Microsoft: Active Directory Replication Concepts
- Microsoft: Access tokens
- Microsoft: Active Directory Forest Recovery – Determine how to recover the forest
- Microsoft: Compare Active Directory to Microsoft Entra ID
- European Commission: EudraLex Volume 4
- European Commission: EU GMP Annex 11 Computerised Systems
- European Commission: EU GMP Chapter 4 Documentation
Sources checked: .
Establish verifiable access records
We support you in aligning the AD-DS inventory with the requirements of your specialist applications and verifying the critical authorization pathways.
- 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.

