Topic starter
11/06/2026 10:34 pm
TL;DR: Modern IT asset platforms now bundle discovery, lifecycle automation, and security controls across SaaS estates, with examples such as 225,000 apps in the library and 9 discovery methods, according to Zluri’s comparison of ManageEngine alternatives. The governance lesson is that asset management and identity control are converging, so teams need to treat license lifecycle and access revocation as one operating problem, not separate workflows.
Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “Top 11 ManageEngine ITAM Competitors & Alternatives for 2026”.
By the numbers:
- Zluri says 20% of Microsoft 365 licences can be unused.
- Zluri says it can notify teams 60 days in advance of a Salesforce contract renewal.
Key questions
Q: What breaks when IT asset management has no identity lifecycle linkage?
A: Teams can know which apps are installed and still miss who can use them.
Q: Why does SaaS visibility matter for identity governance?
A: Because access control depends on knowing which applications, identities, and delegated permissions actually exist.
Q: What are the signs that licence governance and access governance are drifting apart?
A: Common signals include unused licences that remain paid for, active accounts tied to abandoned applications, renewal alerts with no access review, and offboarding events that do not result in licence reclamation.
Practitioner guidance
- Map SaaS discovery to identity lifecycle triggers Tie application discovery, directory data, and SSO evidence to joiner-mover-leaver events so app ownership and account ownership stay synchronised.
- Align licence reclamation with deprovisioning Require that unused licences, abandoned apps, and terminated users move through the same offboarding workflow so commercial cleanup and access removal happen together.
- Build audit trails that link contracts to access Keep a traceable record that connects renewal dates, licence status, and account revocation so auditors can see when access was removed and why.
Bottom line: IT asset governance now overlaps with identity governance because discovery and revocation are increasingly part of the same SaaS control surface.
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 6:46 am
IT asset governance and identity governance are converging into a single operational domain. The article’s real signal is not that one tool category is better than another, but that SaaS discovery, licence management, and access revocation now rely on the same underlying truth set. Once a platform can identify unused apps, track licences, and automate offboarding, it is already participating in identity lifecycle governance. Practitioners should stop treating ITAM and IGA as adjacent disciplines and start evaluating where the handoff between them fails.
A few things that frame the scale:
- Nearly 60% of IT leaders cite restrictive cost and complexity as a weakness of legacy identity governance, according to the 2025 State of Identity Governance Report.
A question worth separating out:
Q: When should teams evaluate ITAM as part of IGA?
A: They should do it whenever device assignment, software entitlement, or offboarding decisions are automated. If asset workflows can create or remove access, the ITAM process has become part of the identity governance chain.
👉 Read our full editorial: ManageEngine alternatives expose the identity gap in IT asset governance
This post was modified 4 days ago by NHI Mgmt Group