If you've ever been in a room with an Enterprise Architect and had to explain ServiceNow SAM Pro from scratch this one's for you.
One question comes up more than almost any other, usually right before a design workshop
"Can you send me something that shows what SAM actually covers? Like a capability map?"
What Is a SAM Capability Map?
It's not a data model. It's not a process flow. It's a structured view of what SAM Pro can do, across domains, grouped by capability - with an honest indication of what works out of the box vs. what needs configuration vs. what needs an integration or Publisher Pack.
Think of it as the one-pager you hand an EA before the architecture review so you're not starting from zero.
The 3 Domains
The map covers three distinct domains:
1. SAM Pro - On-Prem / Perpetual Licensing The core engine. Discovery, normalization, entitlement, reconciliation, optimisation, and governance. This is where 80% of your implementation effort lives.
2. SaaS License Management Connector-driven. OOB connectors for Adobe CC, M365, Salesforce, Okta, Box, Zoom, DocuSign, Tableau, Workday and more. The reconciliation rules are OOB - but they only fire once usage data is actually flowing. Worth calling that out clearly with your stakeholders upfront.
3. Engineering / Complex Licensing Oracle and IBM Publisher Packs. This is where things get interesting - PVU/RVU, ILMT integration, GLAS alignment, Java SE, ULA compliance. Not plug-and-play but genuinely powerful once configured.
Platform Foundation
Everything SAM does sits on top of the Now Platform. The map includes the full foundation layer:
CMDB / CSDM · ITSM (Change / Incident) · ITOM Discovery · Service Catalog / CSD · Procurement & Contracts · GRC / Policy & Compliance.
This matters for EA conversations because SAM doesn't operate in isolation - the quality of your CMDB directly determines the quality of your compliance position. Garbage in, garbage out. Always has been.
A Note on SaaS + Discovery Timing:
One thing I always flag in workshops - SaaS reconciliation rules are OOB but they don't actually do anything until you have usage data flowing. If your SCCM or Intune integration isn't live yet, you'll be sourcing user data from the SaaS portal directly and creating entitlements manually. Plan for that in your WBS. It's not a blocker - just a sequencing conversation.
If you're an implementer preparing for a design workshop, or an architect reviewing your SAM programme scope I hope this saves you some time.
How I Use This
I typically walk through the visual diagram first to set context, use the filter view to focus on the domain we're designing for, then land on the maturity table to have the honest conversation about where we are vs. where we need to get to.
The EA gets a reference they can take back to their architecture review. The customer gets a clear picture of what's in scope.
Feel free to adapt, and use this in your own workshops. If you want the editable format (high-quality PDF), connect with me on LinkedIn happy to share.
As always drop questions or comments below. This community has given me a lot over the years, happy to give a bit back.
Regards,
Abhishek Singh
