ServiceNow offers two closely related but fundamentally different asset management capabilities: IT Asset Management (ITAM) and Software Asset Management (SAM). Both live on the Now Platform. Both integrate with the CMDB. Both appear in ServiceNow proposals and renewal conversations, sometimes interchangeably and sometimes as “must-have” add-ons that expand the deal. But they serve different purposes, are licensed differently, carry different price points, and deliver very different value depending on your organisation’s maturity, estate size, and licensing challenges. The confusion between ITAM and SAM is one of the most expensive misunderstandings in enterprise ServiceNow procurement. Organisations that buy SAM Professional when ITAM with basic SAM Foundation would suffice overspend by tens of thousands of dollars per year. Organisations that buy only ITAM without understanding they need SAM capabilities discover too late that they cannot track software entitlements, reconcile licence positions, or manage compliance — the very problems they thought ITAM would solve. This guide provides the definitive explanation: what each product does, how each is licensed, where they overlap, where they diverge, and how to make the right investment decision for your organisation.
In casual conversation — and unfortunately in many ServiceNow sales presentations — ITAM and SAM are used almost interchangeably. “You need asset management” becomes “you need SAM Professional,” and a licensing decision worth tens of thousands of dollars per year gets made on ambiguous shorthand rather than precise requirements analysis. The distinction matters for three reasons.
First, they solve different problems. ITAM manages the lifecycle of physical and virtual IT assets: procurement, receiving, deployment, maintenance, and retirement. SAM manages software licence entitlements: what software you own the right to use, where it is installed, whether your installations are compliant with licence terms, and how to optimise your licence position. An organisation that needs to track laptop procurement and disposal needs ITAM. An organisation that needs to reconcile Oracle, Microsoft, or SAP licence entitlements against actual installations needs SAM. The problems are related but distinct, and the solution for one does not automatically solve the other.
Second, they are licensed differently and at different price points. ServiceNow ITAM and SAM are separate products with separate SKUs, separate pricing, and separate entitlements. Buying the wrong product — or the wrong edition of the right product — is a common and expensive mistake that compounds through the contract term.
Third, the SAM edition decision (Foundation vs Professional) is one of the highest-impact licensing decisions in the ServiceNow portfolio. SAM Foundation is included with many ServiceNow ITSM deployments or available at a modest cost. SAM Professional is a significant additional investment. The gap between what Foundation provides and what Professional provides is substantial — and whether that gap justifies the investment depends entirely on the maturity and scale of your software asset management programme. Buying Professional when Foundation suffices wastes budget. Buying Foundation when you need Professional creates a false sense of licence compliance that can cost far more than the Professional premium when the next Oracle or Microsoft audit arrives.
ServiceNow IT Asset Management (ITAM) is a suite of applications on the Now Platform that provides lifecycle management for IT assets — primarily hardware assets, but also encompassing the broader category of anything the organisation procures, deploys, manages, and eventually retires as part of its technology infrastructure.
ITAM tracks that a software application is installed on a device. It does not track whether the organisation has the licence entitlement to run that software. ITAM can tell you that 500 laptops have Microsoft Office installed. It cannot tell you whether your Microsoft Enterprise Agreement covers 500 installations, whether those installations are using the correct edition (E3 vs E5), or whether you are compliant with the licence terms. That is the domain of SAM.
This distinction is the source of the most common ITAM/SAM confusion. Organisations deploy ITAM expecting it to provide software licence compliance visibility, discover that it does not, and are then confronted with a choice: invest in SAM (additional cost) or accept that their licence compliance position is unmanaged (significant risk).
ServiceNow Software Asset Management (SAM) is a suite of applications that manages software licence entitlements, installation discovery, licence reconciliation, and compliance position across the enterprise. Where ITAM asks “what assets do we have?”, SAM asks “are we entitled to use the software that is installed on those assets?”
The following comparison maps every critical dimension of both products to clarify exactly where ITAM ends and SAM begins.
| Dimension | ITAM | SAM |
|---|---|---|
| Primary focus | Hardware and IT asset lifecycle | Software licence entitlement and compliance |
| Core question answered | “What assets do we have and where are they?” | “Are we entitled to use the software installed?” |
| Asset types managed | Laptops, desktops, servers, network equipment, mobile devices, peripherals | Software applications, licence entitlements, subscriptions, SaaS |
| Lifecycle scope | Procure → deploy → maintain → retire | Entitle → install → reconcile → optimise → reclaim |
| Compliance dimension | Asset disposal compliance, warranty tracking | Software licence compliance (ELP), audit readiness |
| Financial dimension | Asset depreciation, TCO, CapEx/OpEx | Licence cost optimisation, shelfware identification, audit liability quantification |
| Discovery integration | Hardware discovery (what devices exist) | Software discovery (what is installed on devices) |
| CMDB relationship | Populates CMDB with hardware CIs | Enriches CMDB with software installation and licence data |
| Key stakeholders | IT operations, procurement, finance | ITAM/SAM team, procurement, legal, compliance |
| Audit relevance | Low (hardware audits are rare) | High (software publisher audits are common and expensive) |
ServiceNow SAM is available in two editions: Foundation and Professional. This is not a trivial distinction — the gap between the two editions is substantial, and the wrong choice creates either unnecessary cost or dangerous capability gaps.
SAM Foundation provides basic software asset management capabilities: software discovery and normalisation, a software catalogue, basic entitlement tracking, and simple reporting. Foundation is often included with ITSM Professional or Enterprise deployments (check your specific contract) or available as a low-cost addition.
What Foundation does well:
What Foundation does not do:
SAM Foundation gives you software visibility. It tells you what is installed. It does not give you software compliance. It cannot tell you whether those installations are within your licence entitlements because it lacks the publisher-specific licence calculation engines needed to reconcile installations against the extraordinarily complex licence rules that Oracle, Microsoft, SAP, IBM, and other major publishers use. An organisation that deploys SAM Foundation and assumes it has licence compliance visibility is operating with a false sense of security. The compliance position is not “managed” by Foundation — it is simply visible at a surface level that does not account for the licence metric complexity that drives actual compliance exposure.
SAM Professional provides the full software asset management capability set: everything in Foundation plus publisher-specific licence calculation engines, automated Effective Licence Position reconciliation, complex licence metric handling, publisher content packs, automated reclamation workflows, and SaaS management capabilities.
What Professional adds over Foundation:
| Factor | SAM Foundation Sufficient | SAM Professional Required |
|---|---|---|
| Software estate complexity | Mostly SaaS subscriptions, limited on-premise | Significant on-premise software with complex licence metrics (Oracle, SAP, IBM) |
| Audit exposure | Low audit risk, few auditable publishers | Active audit exposure (Oracle, Microsoft, SAP, IBM all audit regularly) |
| Licence metric complexity | Simple per-user or per-device models | Processor-based, core-based, PVU, NUP, or hybrid models |
| Annual software spend | Below $5M across all publishers | Above $5M with significant concentration in auditable publishers |
| SAM maturity | Building basic inventory and visibility | Established SAM function requiring automated ELP and reclamation |
| Compliance reporting needs | Internal visibility only | Audit-ready ELP for external scrutiny by publisher audit teams |
| Shelfware / optimisation goals | Basic visibility into unused software | Automated reclamation workflows with measurable ROI |
| SaaS management needs | Minimal SaaS estate | Large SaaS estate requiring subscription optimisation |
The critical test: If your organisation faces audit risk from publishers with complex licence metrics (Oracle, Microsoft EA with per-core servers, SAP, IBM), SAM Foundation is insufficient. The Foundation gap — no publisher-specific licence engines, no automated ELP, no complex metric handling — means your compliance position is not actually managed, just partially visible. SAM Professional is required for genuine compliance management. If your software estate is primarily SaaS subscriptions with simple per-user licensing and minimal on-premise complexity, Foundation provides adequate visibility at a fraction of the cost.
The licensing structures for ITAM and SAM are distinct and merit careful analysis during procurement and renewal.
ServiceNow ITAM is typically licensed on a subscription basis, with the metric varying by the specific ITAM applications included. The core ITAM functionality (hardware asset management, asset lifecycle management, contract management) may be included as part of the broader ITSM or ITOM deployment, or licensed as a standalone module. Key licensing considerations:
ServiceNow SAM is licensed separately from ITAM, with the pricing depending on the edition (Foundation vs Professional) and the licensing metric.
ServiceNow’s sales team may present ITAM and SAM as a combined “asset management” solution, bundling both into a single proposal. This bundling can create genuine value (simplified procurement, better pricing on the combined deal) or obscure the true cost of each component (making it impossible to evaluate whether Foundation or Professional SAM is needed without separating the pricing). Always request itemised pricing for ITAM and SAM separately, with SAM broken out by edition (Foundation vs Professional) and content pack inclusions. Bundled pricing that cannot be decomposed makes it impossible to right-size at renewal.
Organisations with primarily SaaS-based software estates, limited on-premise complexity, and minimal audit exposure from major publishers do not need the publisher-specific licence engines and automated ELP reconciliation that SAM Professional provides. Foundation’s software discovery, normalisation, and basic entitlement tracking are sufficient for visibility and basic compliance management. Upgrading to Professional in this scenario means paying for capabilities that deliver no incremental value. The savings from staying on Foundation can be substantial: SAM Professional’s per-fulfiller cost is significantly higher, and the content pack licensing adds further expense. Evaluate SAM edition selection based on actual compliance needs, not aspirational maturity goals.
The mirror image of Mistake #1 and potentially far more expensive. Organisations with significant Oracle, Microsoft, SAP, or IBM estates that deploy SAM Foundation and assume they have audit-ready compliance visibility are operating with a dangerous false sense of security. When the audit letter arrives, Foundation cannot produce an accurate Effective Licence Position because it lacks the publisher-specific licence engines needed to reconcile installations against complex metric rules. The result: months of manual data gathering, expensive consultant engagement, and a compliance position assembled under time pressure — exactly the scenario SAM Professional is designed to prevent. If you face meaningful audit risk, the cost of SAM Professional is a fraction of the cost of an unprepared audit response.
Organisations that invest in ITAM for “asset management” and assume software licence compliance is covered have a hardware lifecycle management solution without a software compliance solution. ITAM tracks the laptop. It does not track whether the software on the laptop is licensed. This confusion typically surfaces when: (a) a software publisher audit arrives and the ITAM team discovers they have no licence reconciliation capability, (b) a procurement team tries to determine whether additional software licences need to be purchased and discovers that ITAM provides installation data but not entitlement data, or (c) a finance team requests shelfware analysis for software and discovers that ITAM tracks hardware cost, not software licence utilisation.
SAM is a specialist function. The number of users who genuinely need SAM fulfiller access — to manage software catalogues, configure licence models, run ELP reconciliations, and execute reclamation workflows — is typically 5–20 in even the largest enterprises. Yet proposals frequently include SAM fulfiller counts of 30, 50, or more, because the sales team sizes the population based on “everyone in ITAM” rather than “everyone who actually operates SAM.” IT asset analysts who manage hardware lifecycle (ITAM fulfillers) do not need SAM fulfiller licences unless they also perform software licence reconciliation work. The distinction is operational: ITAM fulfillers manage assets; SAM fulfillers manage licences. Right-size the SAM fulfiller count before signing.
SAM’s value depends entirely on the quality of the software installation data it receives. If the organisation has not deployed ServiceNow Discovery, SCCM/Intune integration, or another discovery tool that feeds software installation data into the CMDB, SAM has nothing to reconcile. An empty or incomplete software catalogue cannot produce an Effective Licence Position regardless of whether the SAM edition is Foundation or Professional. Before investing in SAM, ensure that the discovery infrastructure is in place to populate the data that SAM needs to function. The most expensive SAM deployment is one that sits on top of an incomplete CMDB.
ITAM and SAM do not exist in isolation. They interact with other ServiceNow modules in ways that affect both operational value and licensing cost.
ITAM integrates with ITSM to enrich incident, problem, and change management with asset data. When a user reports a laptop issue, ITSM can automatically associate the incident with the specific asset record in ITAM, providing the support agent with asset details (model, warranty status, configuration, history) without manual lookup. SAM extends this integration by enriching the asset record with software installation data, enabling support workflows that consider the software environment on the affected device.
The licensing implication: ITSM fulfillers who view ITAM asset data in the context of incidents do not necessarily need ITAM fulfiller licences. They are consuming ITAM data within the ITSM interface. The fulfiller boundary depends on whether they are managing assets (ITAM fulfiller needed) or viewing asset data within ITSM workflows (ITSM fulfiller sufficient). Clarify this boundary with ServiceNow to avoid over-licensing.
ServiceNow ITOM Discovery is the primary mechanism for populating the CMDB with infrastructure and software installation data. ITOM discovers what exists; ITAM manages the lifecycle; SAM reconciles the licences. This three-layer integration means that ITOM licensing (subscription units), ITAM licensing (fulfillers), and SAM licensing (fulfillers + edition) are all interconnected investments. An ITOM deployment without ITAM means discovered assets are not lifecycle-managed. An ITAM deployment without ITOM means asset data is manually maintained (and therefore unreliable). A SAM deployment without ITOM means software installation data is incomplete. The practical reality: effective IT asset and software asset management on the ServiceNow platform requires some level of investment in all three capabilities, and the licensing cost of each must be evaluated as part of an integrated strategy.
ITAM integrates with procurement workflows to automate the acquisition process: when a new asset is needed, the request flows through ITAM for approval, procurement for sourcing, receiving for delivery confirmation, and ITAM for deployment tracking. SAM extends this by incorporating licence checks into software procurement: before purchasing additional software licences, SAM checks whether existing entitlements have unused capacity that could be reallocated, preventing unnecessary purchases.
An often-overlooked application of SAM Professional: using it to manage your ServiceNow licence position. SAM Professional can track ServiceNow fulfiller entitlements, monitor actual fulfiller assignments, reconcile contracted quantities against deployed quantities, and identify ServiceNow shelfware. This creates a self-referential governance loop where the platform manages its own licensing — a capability that is particularly valuable for enterprises with large ServiceNow estates where fulfiller populations change frequently. The irony is not lost: you are using ServiceNow to optimise your ServiceNow licensing. But it works, and the data it produces directly supports the renewal negotiation strategy.
The investment decision depends on where the organisation sits on two dimensions: hardware lifecycle management maturity and software licence compliance risk.
| Scenario | Recommended Investment | Rationale |
|---|---|---|
| Hardware tracking needed, minimal software compliance risk | ITAM + SAM Foundation | ITAM manages hardware lifecycle; Foundation provides basic software visibility without the cost of Professional |
| Significant audit exposure (Oracle, Microsoft, SAP), hardware already tracked elsewhere | SAM Professional (standalone) | Professional’s publisher-specific engines and automated ELP address the primary risk; hardware management continues in existing tool |
| Both hardware lifecycle and software compliance needs | ITAM + SAM Professional | Full lifecycle management for hardware assets plus genuine compliance management for software — the comprehensive solution |
| SaaS-first organisation with minimal on-premise software | ITAM + SAM Foundation (evaluate SaaS management add-on) | Foundation’s basic software visibility is sufficient for simple SaaS models; ITAM manages the remaining hardware estate |
| Large enterprise with complex multi-vendor on-premise and SaaS estate | ITAM + SAM Professional + SaaS management | Full capability set required for the complexity and audit exposure of a large mixed estate |
When ITAM and/or SAM are part of a broader ServiceNow renewal, the following negotiation strategies protect the enterprise from over-investment.
A question that arises frequently in Redress Compliance’s advisory engagements: “If we deploy SAM Professional, do we still need an independent licensing advisor?”
The answer is nuanced. SAM Professional provides the operational infrastructure for ongoing software licence management: discovery, normalisation, reconciliation, and reclamation. It is the day-to-day tool that maintains the licence position between audit events and renewal cycles. What SAM Professional does not provide is the strategic and commercial expertise that drives licensing optimisation: benchmarking data for pricing negotiations, architectural advisory for licence-efficient infrastructure design, audit defence strategy when a publisher challenges your position, and contract negotiation expertise for renewals across Oracle, Microsoft, SAP, and other major publishers.
SAM is a tool. Independent advisory is expertise. They are complementary, not substitutional. The most effective enterprise licensing programmes deploy SAM Professional for operational management and engage independent advisory for strategic events: renewals, audits, M&A, and major infrastructure changes. SAM provides the data; independent advisory provides the strategy. Together, they deliver the complete licence management capability that protects the enterprise from both compliance risk and commercial overspend.
“The ITAM vs SAM confusion costs enterprises money in two directions. Buy too much — SAM Professional when Foundation suffices — and you overspend on a capability you do not need. Buy too little — Foundation when Professional is required — and you face an Oracle or Microsoft audit without the compliance visibility to defend your position. In both cases, the root cause is the same: a purchasing decision made without precise requirements analysis. ITAM and SAM are both valuable products. The question is not whether to invest, but exactly how much of each your organisation needs based on what you are actually managing and what risks you actually face.” — Fredrik Filipsson, Co-Founder, Redress Compliance
ITAM (IT Asset Management) manages the lifecycle of physical and virtual IT assets: procurement, deployment, maintenance, and retirement of hardware like laptops, servers, and network equipment. SAM (Software Asset Management) manages software licence entitlements: tracking what software you own the right to use, comparing that against what is actually installed, producing an Effective Licence Position for compliance, and identifying shelfware for cost optimisation. ITAM answers “what assets do we have?” SAM answers “are we entitled to use the software installed on those assets?”
SAM Foundation provides basic software discovery, normalisation, and simple entitlement tracking. SAM Professional adds publisher-specific licence calculation engines (Oracle, Microsoft, SAP, IBM), automated Effective Licence Position reconciliation, complex licence metric handling (processor, core, PVU, NUP), downgrade/version rights management, automated reclamation workflows, SaaS management, and regularly updated publisher content packs. Foundation provides visibility; Professional provides compliance management. If you face audit risk from publishers with complex licence metrics, Foundation is insufficient.
In some contract structures, SAM Foundation is included with ITSM Professional or Enterprise editions at no additional cost. However, this varies by contract and by deal. Check your specific ServiceNow subscription agreement to confirm whether SAM Foundation is included before purchasing it separately. If it is included, you do not need to pay for it again during renewal negotiations.
SAM fulfillers should be sized based on the number of people who operationally manage the SAM application: configuring licence models, running ELP reconciliations, managing the software catalogue, and executing reclamation workflows. For most enterprises, this is 5–20 people. The SAM fulfiller population should not be confused with the broader ITAM team or procurement organisation. Users who manage hardware assets need ITAM fulfiller licences, not SAM licences. Users who view software reports may need only approver or requester-level access.
It depends on your requirements. If you need hardware lifecycle management and software licence compliance, you need both. If you need only hardware tracking (and manage software licensing through other means), ITAM alone may suffice. If you need only software compliance management (and track hardware elsewhere), SAM alone may suffice. For most enterprises with a meaningful ServiceNow deployment, the combination of ITAM plus SAM Foundation (at minimum) provides the foundation for effective asset management. SAM Professional is required when audit risk and licence complexity demand automated compliance management.
SAM and independent advisory serve different functions. SAM Professional provides operational infrastructure: day-to-day discovery, reconciliation, and licence position management. Independent advisory provides strategic expertise: pricing benchmarking for negotiations, audit defence strategy, contract negotiation, and architectural advisory for licence-efficient design. They are complementary, not substitutional. The most effective licensing programmes deploy SAM for operational management and engage independent advisory for strategic events like renewals, audits, and major infrastructure changes.
SAM Professional (not Foundation) provides audit readiness through automated Effective Licence Position (ELP) reconciliation. When a software publisher initiates an audit, SAM Professional can generate the compliance position within days: what software is installed, what entitlements exist, and where the gaps or surpluses are. Without SAM Professional, audit response requires months of manual data gathering across multiple systems, often resulting in incomplete or inaccurate positions that weaken the organisation’s negotiating position. SAM Foundation cannot produce audit-ready ELP because it lacks the publisher-specific licence engines needed for accurate reconciliation.
Redress Compliance helps enterprises right-size their ITAM and SAM investments — ensuring you have the capabilities you need without paying for capabilities you don’t. Our independent advisory covers ServiceNow licensing across all modules.