Topic starter
12/06/2026 1:07 am
TL;DR: ITAM and ITSM serve different parts of the SaaS operating model, with ITAM focused on the asset lifecycle and ITSM on service delivery and support, according to Zluri. For IAM teams, the distinction matters because discovery, lifecycle control, and offboarding require asset governance, not just service desk workflows.
Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “ITAM vs. ITSM”.
Key questions
Q: What is the difference between ITAM and ITSM in SaaS environments?
A: ITAM governs the asset itself, including inventory, ownership, cost, renewal, and retirement.
Q: What breaks when SaaS governance depends only on service desk workflows?
A: Ownership becomes unclear, shadow applications can stay outside the control model, and deprovisioning can miss apps that never appear as service tickets.
Q: Why does asset registry accuracy matter for SaaS access control?
A: Because identity decisions depend on knowing what software exists, who owns it, and whether it is still active.
Practitioner guidance
- Separate asset records from service requests Use ITAM as the source of truth for SaaS ownership, contract status, licence state, and retirement, then let ITSM handle request fulfilment and incident work.
- Reconcile SaaS discovery with identity records Cross-check discovered applications against assignee data, business owners, and renewal status so access reviews and offboarding act on current inventory rather than stale tickets.
- Use asset lifecycle data in offboarding Require a verified asset owner and retirement status before removing access, reclaiming licences, or closing the application record.
Bottom line: ITAM and ITSM are complementary, but only ITAM gives SaaS governance the asset-level truth required for identity control.
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:49 am
ITAM, not ITSM, is the governance layer that determines whether SaaS can actually be controlled. The article draws a clean line between asset management and service management, and that line is operationally important for identity teams. Access decisions, licence recovery, and offboarding all depend on an accurate asset picture, not on ticket closure. When SaaS governance is routed through service workflows alone, identity control becomes reactive and incomplete.
A few things that frame the scale:
- Gartner predicts that AI systems will initiate 50% of all service requests by 2030, driven largely by agentic AI.
A question worth separating out:
Q: What is the difference between SaaS asset lifecycle control and service management?
A: Asset lifecycle control tracks discovery, ownership, licensing, and retirement of the application itself, while service management handles support, incidents, and request fulfilment. Both matter, but only lifecycle control gives IAM and IGA teams the context needed to manage access and accountability.
👉 Read our full editorial: ITAM vs. ITSM for SaaS governance: where identity control diverges
This post was modified 4 days ago by NHI Mgmt Group