Topic starter
12/06/2026 12:45 am
TL;DR: Automation can speed onboarding, mid-life access changes, and offboarding, but it also shifts identity governance from manual ticket handling to lifecycle control across apps, roles, and deprovisioning, according to Zluri. The main issue is not task speed alone, but whether access changes are consistently applied across the full identity surface.
Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “How to Automate IT Tasks”.
Key questions
Q: What breaks when automated onboarding and offboarding do not cover every app?
A: The control breaks at the application boundary.
Q: When should IAM teams prioritise offboarding over onboarding automation?
A: IAM teams should prioritise offboarding whenever residual access creates a greater security risk than delayed provisioning.
Q: How do organisations know whether identity lifecycle automation is actually working?
A: They should measure execution coverage, revocation delay, and audit completeness across the full app estate, not just in the IdP.
Practitioner guidance
- Define lifecycle coverage across all applications Build an application and entitlement inventory that shows where onboarding, change and offboarding workflows actually execute, then identify systems still handled manually.
- Verify offboarding reaches every access path Check that deprovisioning removes access from SaaS apps, local entitlements and any non-SSO paths, not only the primary identity provider.
- Separate request convenience from approval governance Keep workflow automation and approval policy distinct so speed gains do not erase role boundaries, permission scope or authorisation checks.
Bottom line: IT automation improves IAM only when provisioning, change and deprovisioning cover the full application estate, not just the primary identity system.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 4 days ago by NHI Mgmt Group
12/06/2026 10:12 am
Lifecycle automation is only as strong as the identity surface it actually covers: The article’s real message is not that automation saves time, but that IAM control fails when lifecycle actions stop at the directory. If onboarding, change and offboarding do not extend to every application and entitlement, the organisation has faster admin activity without better governance. Practitioners should treat coverage completeness as the core control question.
A question worth separating out:
Q: How should security teams structure access request tickets for better governance?
A: Security teams should structure access request tickets with mandatory tags for request type, application, urgency, and owner so the workflow can enforce policy before approval. That makes routing more reliable, improves auditability, and reduces the chance that privileged or sensitive requests are treated like routine access.
👉 Read our full editorial: IT automation and identity lifecycle control: what changes for IAM
This post was modified 4 days ago by NHI Mgmt Group