We define how accounts are created at onboarding, which permissions are renewed on a role change and how access is removed at offboarding. We organize approval steps and access records according to the systems in use.
SSO centralizes sign-in in one place. MFA verifies identity with an additional factor. Access approval records who granted the permission. Permissions inside the application are managed separately. We address all four separately.
01
Is an Entra ID P1 or P2 license required?
Conditional Access and dynamic groups require at least P1; risk-based policies, PIM and access reviews require P2 or Entra ID Governance. What can be done with your current licenses is determined first.
02
Is automatic integration with our HR system possible?
It depends on the HR system’s API or export capabilities. If direct integration isn’t possible, a semi-automated model is set up with an approved form and workflow.
03
Can all applications be connected to SSO?
Applications that support SAML, OIDC or LDAP can be connected. For legacy applications that don’t, compensating controls such as a password vault or access restrictions are recommended.
04
How often should access reviews be done?
Usually every three months for critical systems and every six or twelve months for others; the frequency is set according to the risk assessment.
Implementation approach
Inventory first, then SSO
01 / ANALYSIS
Inventory and process analysis
Accounts, applications and the current HR–IT flow are mapped.
02 / PLAN
Model design
The role model, approval flow and technical integrations are designed.
03 / EXECUTION
Implementation
SSO, MFA, automation and groups are enabled in phases, starting with a pilot group.
04 / HANDOVER
Review cycle
The first access review is carried out and handed over to the process owners.