IT systems · Practical guide

Microsoft Entra ID for GxP: demonstrating identity and effective access

A user is blocked in Microsoft Entra ID but can still act in an existing application session. Test when access to the regulated process actually ends. Connect identity management, application roles, Conditional Access and logs to the permitted actions. Include technical and emergency accounts in a defined scope.

Table of contents

At a glance

What should you demonstrate when Entra ID serves GxP applications?

Define how Microsoft Entra ID contributes identity and access to GMP-relevant applications. Test approved roles, assignment and removal, effective access policies and relevant logs. Verify the outcome in the target application. Blocking a new sign-in does not necessarily terminate an existing session. Microsoft documentation supports the assessment but does not replace testing of your configuration and access paths.

  • Identity, authentication, and professional qualification are distinct verification requirements.
  • Report-only indicates potential regulatory implications; it does not mandate the implementation of controls.
  • User accounts, technical identities, and emergency access requirements appropriate dedicated controls.
  • Entra protocols do not replace the professional audit trail or a well-founded storage concept.

1. Delimit Tenant, Licenses and Related Applications

Microsoft Entra ID is a cloud-based service for identity and access management. The Entra product family includes additional offerings such as Domain Services, Governance, and Workload ID. These are not automatically fully available in every tenant. Local Active Directory and Entra ID are also not identical systems. Therefore, document where identities are created and which components are involved in access.

A robust configuration state includes tenant, license scope, enterprise applications, protocols, connectors, assignments, and relevant policies. For a cloud service, a single version number is insufficient to describe all currently effective settings. Maintain the evaluated configuration state with date and appropriate configuration documentation; preview functions and additional services are separately categorized.

This article concerns human medicines manufacturing. Annex 11 distinguishes infrastructure qualification from application validation. For Entra, assess service and access controls and demonstrate how they support the intended use of connected applications. This neither assigns a universal GAMP category nor certifies the cloud. Establish other applicable regulatory scopes separately.

Sources: [1] [9] [10]

2. From the approved task to the authorized action think

A successful registration first confirms whether the intended submission pathway functions correctly. It does not yet verify whether a user within the application can perform only the professionally authorized actions. Therefore, for each relevant role, describe at least one permitted and one prohibited action. Additionally, verify role assignment at a user who does not hold that role.

The following matrix serves as an internal reference tool for coordination between QA, IT, and the responsible party for the specialized application. Use stable assignments and document who authorizes changes. A clear group name is helpful but does not replace verification of its members, dissemination, or actual impact.

Work aid: The access chain and its separate validations
LevelEvidence questionExample for the inspection
Professional Approval What task is assigned to this person? Approval aligns with site, process, and representation
Entra assignment Is the correct identity of the application assigned? Check direct membership, exclusion, and false identity
Provisioning or role mapping Does the intended role in the target system meet the expected requirements? Compare target account and specific rights after amendment
Conditional Access Does the intended registration condition actually apply? With the rule active, test an allowed access attempt and an unauthorised one
Application session What actions remain possible after a withdrawal? Test an existing session and a fresh login separately
Documenting the evidence Can the decision be reconstructed later? Approval, modification, intended use, and relevant logs to be linked

Sources: [5] [2] [10]

3. Do not confuse assignment and provisioning with the same action

Automated provisioning can enable users to be created, modified, and disabled in appropriate target applications. Microsoft documentation outlines SCIM and application-specific connectors as mechanisms for this purpose. However, the actual behavior depends on scope, assignment attributes, permitted actions, and the target application. The existence of an existing single sign-on (SSO) connection does not guarantee that permission changes are automatically synchronized.

At the time of entry, role change, and exit, verify that the same individual is consistently assigned throughout the entire chain. A role change shall enable the new responsibility and remove previous rights in accordance with your instructions. For employees with name changes or those rehired, clarify which target account is assigned. A deliberate and contradictory assignment shall serve as a specific negative case and must be reliably detected.

Note the documented limit on nested group memberships in the described group-based application deployment: direct membership is critical, not arbitrary subgroups. Additionally, review deactivated connector actions. A successful connectivity check does not confirm that deactivation has been effectively implemented functionally. For applications lacking corresponding automation, the process must include a clear manual closure step.

Sources: [5] [4]

4. Conditional Access to be evaluated first, then effectively verified

Conditional Access links conditions to access decisions. Microsoft identifies P1 for the basic capability and the appropriate P2 or Identity Protection capabilities for risk-based policies. Verify additional licence and service dependencies for your proposed design. A licence establishes neither the correct target group nor an active policy.

Report-only mode evaluates guidelines but does not enforce access and session controls. Therefore, a failure observed in this mode cannot be considered a detected access block. Additionally, the mode is not entirely free of user impact under all conditions: Microsoft, for example, identifies potential device certificate queries. Hence, plan the evaluation systematically and using appropriate test identities.

For a reliable transition, document the verified regulatory baseline, affected resources, inclusions and exclusions, as well as interactions with other rules. Subsequently, in the intended active state, verify that authorized access functions and unauthorized access actually fails. A single green result from a rule does not confirm that the overall login is permitted. Similarly, it does not establish professional write or release authorizations within the application.

Sources: [2] [3]

5. Treat technical identities and emergency access separately

A service endpoint does not necessarily operate under the developer's user account. Microsoft defines specific conditional access policies and licensing requirements for certain service principals. A user-based policy applied to a group does not automatically protect an embedded service principal. The documented workload scope also has limitations, for example, regarding managed identities and certain multi-tenant applications.

Therefore, establish a directory of actually used technical access points, including purpose, resource rights, responsible owner, and change pathway. Upon employee departure, a technically still required connection may remain in place. Crucially, ownership, confidentiality, and permissions must be controlled, and no personal residual access should be left unaccounted for. Define an appropriate deactivation test for each access pathway.

Emergency administration addresses another concern: the operation must remain action-ready in the event of failure of normal reporting pathways. Microsoft describes protected, monitored emergency accounts and regular practical testing. For your process, authorized users, the justification, accessible access methods, and subsequent evaluation must be established. This does not result in uncontrolled access, unauthorized modification of technical data, or routine use of an emergency account in daily operations.

Sources: [7] [8] [10]

Further reading:

6. Example: Withdrawal test – new application locked, old session active

This scenario does not represent a test of a genuine tenant or product. User U-17 has three permissions in QMS-A: read, edit, and approve. In Labor-B, they have read, enter, and confirm permissions. Both applications have an active session prior to 09:00 hours. Technical connection T-4 operates with its own identity and is separately accountable.

In this example, access is withdrawn with approval at 09:00. The company specifies that user U-17 must lose the ability to perform all six actions within ten minutes. This is neither a Microsoft commitment nor a general GMP deadline. All clocks are synchronised. The tests change only the designated test data.

In this example case, the QMS-A system is locked at 09:03 hours. Laboratory-B still permits actions until 09:10 hours; the actions fail at 09:11 hours following an additional application-side intervention. This constitutes a breach of the example requirement. The first successful lock test alone does not indicate the exact second at which the lock became effective.

Own inspection matrix: Six personal rights and one separate technical access
Time and TestingFinding in this exampleAssessment against the defined expectationEvidence needed
08:59 – Situation overview QMS-A: 3; Labor-B: 3 personal actions allowed 6 of 6 outgoing actions confirmed Roles, test users, and controlled sessions
09:00 – Trigger withdrawal Entra account blocked and further access removal started Trigger identified, no overall result yet Approval and actually performed actions
09:01 – New registration New registration fails This access path is locked; previous sessions still active Login attempt and contemporaneous protocol entry
09:03 – Existing meeting QMS-A All 3 actions fail 0 of 3 here; first confirmed block after 3 minutes Pilot studies with time and appropriate documentation and evidence
09:10 – Ongoing session Laboratory-B All 3 actions remain possible Example limit of 10 minutes not met Open finding, potential consequences and containment measures
09:11 – retest after the application change Also in Lab-B all 3 actions fail 0 of 6 possible; first confirmed global lock after 11 minutes Action, retrospective testing and justified conclusion decision
Separate Test T-4 The compound remains suitable for the approved process. No evidence of personal rights; separately assess ownership. Technical Identity, Purpose and Responsible Owner

Sources: [4] [5] [10]

7. Protocols regarding statement and retention differ

A login protocol addresses different questions than the modification of a technical release. Identify the events provided by Entra, the provisioning service, and the target application. For investigating a role revocation, authorization, identity change, and failed app access may collectively be relevant. A single screenshot of the user overview does not capture this chain.

By default, the Microsoft table lists seven days in Free for audit and login protocols and 30 days in P1/P2. These are product-related retention values, not GMP limits. Entra protocols can also be distinguished from the Microsoft-365 Unified Audit log. A license increase does not restore previously expired data retrospectively unless otherwise secured.

Determine your needs from the relevant proof questions and set up the required longer storage in time. Then check the receipt, assignment and subsequent retrieval at the designated location with a known event. Consider data protection and access rights. Neither an activated export option nor a large amount of memory proves the completeness and usability of the required proofs alone.

Sources: [6] [11] [10]

Further reading:

8. Connect service records to your own configuration

Start with a system description that clearly identifies the identity source, login pathways, intended applications, and responsibilities. Link this to approved roles, configuration states, and risk-based test cases. The service's infrastructure controls and the application's functional testing must align; they do not need to be housed in artificially separated documentation.

Evaluate available Microsoft and implementation partner documentation regarding scope, timeframe, service, and actual coverage. A general security control report does not automatically address your specific inquiry about a particular connector mapping. Conversely, appropriate evidence does not need to be recreated without valid justification. Document which statements you accept and which customer-specific points remain open.

For the conclusion, it must be established whether the intended controls have been adequately demonstrated and whether deviations are appropriately managed. A negative test result is not eliminated by renaming the role. Describe the root cause, potential consequences, corrective action, and required follow-up testing. Historical assignments should be retained for the evaluation of prior actions, even if current access has been revoked.

Sources: [10] [11]

9. Organizing changes and SME participation in practice

QA does not need to administer every identity function. It must work with the process responsible party to determine which tasks require protection and assess the residual risk associated with delays or misassignment. IT defines the technical pathways; the application responsible party confirms role assignments and session behavior. Personnel processes provide reliable triggers for onboarding, role changes, and offboarding. Without this collaboration, technical restrictions remain without adequate functional justification.

The effort depends on the number and diversity of access pathways: cloud and on-premise identities, local app accounts, guest access, connectors, technical accounts, and exceptions. A small company may operate only a few systems but could have multiple critical exception routes. Prioritize based on impact to the process, rather than using user count alone as a metric.

When group rules, authentication methods, or app versions are changed, assess the impact on existing validation evidence. A connector may be affected if its intended behavior changes. Plan appropriate regression testing and operational monitoring, including controlled recalls. Ongoing evaluation leverages incidents, open exceptions, and modified service functions; a general annual testing obligation is not asserted.

Sources: [10] [5] [8]

10. Checklist for effective and demonstrable access

The checklist links decisions to their technical effect. Use it before implementation or a significant change. Record the answer and evidence for each relevant point, and justify any exclusions.

  • Tenant, identity source, licenses, applications, and actual enrollment pathways are described.
  • Approved tasks are mapped to verifiable application rights and responsible owners.
  • Account access, role changes, and sign-off consider target accounts, matching, and authorized connector actions.
  • Conditional Access was verified with inclusion/exclusion criteria in the actually enforced state.
  • Existing sessions, direct app integrations, and new registrations were evaluated separately.
  • Technical identities and emergency access accounts have appropriate controls and traceable responsibilities.
  • Relevant protocols are retained for the required duration and are practically recoverable.
  • Changes, exceptions, incidents, and post-test evaluations are considered in the assessment of ongoing operations.

Sources: [10] [4] [6]

Project experience and collaboration

Test a revoked role against the actual business operation

With identity and application owners, we trace an approved role to an actual action in the target system. After controlled revocation, we check a fresh login separately from sessions already open. Depending on the architecture, a focused test may demonstrate the existing process or an extra application control may be necessary. We record when revocation takes effect and which logs support that conclusion. Your responsible team performs the operational change.

Frequently asked questions about Microsoft Entra ID

Must Entra ID be validated or qualified?

First define its role in your system landscape. Link infrastructure and service controls to the validated use of the GMP applications. Select requirements and evidence for your use and test configuration and integration where identity or access can affect a process decision. This does not establish a universal category for a cloud product.

Sources: [1] [10]

Does Single Sign-on also assign the correct role within the application?

No. Registration and professional authorization are distinct functions. The role may originate from inherited attributes or be managed directly within the application. Verify the permitted and prohibited actions for an authorized test user, as well as a counter scenario without assignment. Document which entity actually assigns the role and the process by which changes reach effective action.

Sources: [5] [10]

Why can a locked user still work within an application?

The application can manage its own session. Microsoft states that Entra cannot directly revoke a session token issued by the application. Therefore, the actual impact depends also on application behavior and logout procedures. Test a previously opened session separately from a new login, and establish appropriate additional measures. Do not assume an immediate blocking effect.

Sources: [4]

Is a report-only result already considered a passed block test?

This is an evaluation record outlining potential regulatory impact. Since Report-only does not enforce the relevant controls, it does not substantiate any actual preventive action. Use it for preparation and subsequently perform a controlled review of the intended active state. Consider concurrently applicable rules, exceptions, and resources. Additionally, potential user impacts of the testing must be evaluated in advance.

Sources: [3]

Do we need automated provisioning for each intended use?

Not necessarily. What is essential is a reliable, validated process for setup, modification, and removal. Automation depends on the application's support and configuration. For a manual process, clear responsibilities, triggers, and closure documentation are required. Additionally, always verify the actual impact in the target environment. An automated transfer without accurate mapping is not more reliable than an appropriate, controlled manual process.

Sources: [5] [10]

Does our MFA rule also apply to the technical laboratory interface?

You cannot derive this from a user guide. First determine whether the connection uses a user account, a service principal, or another technical identity. Microsoft documents specific requirements and coverage limitations for workload identities. Assess the specific access path, its privileges, and protective measures. An interactive MFA requirement is not a reasonable general justification for every automated service.

Sources: [7]

How are emergency accounts treated in the GMP environment?

Define the technical purpose and controlled use. The emergency access should be available in the event of failure of normal administrative pathways, yet remain protected, monitored, and traceable in usage. Practically assess the intended scenario and evaluate the subsequent actions. A technical exception to a registration requirement does not constitute professional authorization for arbitrary data modifications within a quality management system.

Sources: [8] [10]

Are 30-day exit protocols for GMP sufficient?

Product storage is not a professional determination of your documentation requirements. Determine which events you need to retain for the relevant process, for how long, and where potential records may otherwise be located. If the standard retention period is insufficient, appropriate storage must be available in a timely manner. Verify the actual content and retrievability. A subsequent license upgrade cannot recover expired entries that have not been otherwise secured.

Sources: [6] [11]

What documentation is required by a small and medium-sized enterprise before the first test?

Useful are an up-to-date list of applications, approved roles, actual login pathways, and responsibilities for identities and target systems. Supplement this with known exceptions, technical accounts, and the current regulatory stance. Then define required decisions and appropriate test identities. The key preparatory step is clarifying who is authorized to perform specific professional actions and how the revocation of such access is confirmed.

Sources: [10]

Must all access tests be repeated with every cloud change?

The extent required arises from the impact assessment. A change may affect both modified and previously unchanged functions, for example, if an app update alters session behavior. Continue to provide robust supporting evidence and specifically supplement the relevant testing activities. Document the current state under consideration, open uncertainties, and the associated decision. Neither an automated end-to-end test nor a general test waiver may be inferred therefrom.

Sources: [10] [4]

Sources and review date

Source date: 6 October 2026. Product information relates to the specified Microsoft Learn materials and their prerequisites. The actual tenant configuration and target application must be verified separately. Regulatory reference: the described human medicinal product GMP application. Figures and timeframes are subject to internal assumptions.

  1. What is Microsoft Entra?
  2. What is Conditional Access?
  3. Analyze Conditional Access Policy Impact
  4. Revoke user access in Microsoft Entra ID
  5. How Application Provisioning works in Microsoft Entra ID
  6. Microsoft Entra data retention
  7. Conditional Access for workload identities
  8. Manage emergency access accounts in Microsoft Entra ID
  9. EudraLex Volume 4 – Human Medicinal Products – GMP
  10. EU GMP Annex11: Computerised Systems
  11. EU GMP Chapter4: Documentation

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Integrate access controls with the GxP process

We help you jointly evaluate Entra-configuration, functional roles, and actual usage impact, and establish appropriate evidence for your operations.

  • 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 →