Hi @kunalkotak
Service Mapping is typically recommended for on-premise infrastructure. I've seen it used for in-house developed services and supporting CIs, and where a hierarchical map is essential. Its also a good choice for complex services with many application dependencies where a prebuilt solution cannot do the job.
The other common application of Service Mapping is via Tag-Based Service Mapping for Cloud infrastructure using cloud tagging.
Service Mapping is not the best solution where something pre-built already exists, so if there is a Service Graph Connector available and the costs are OK, this is often the better solution for certain technologies.
The other limitation with Service Mapping is the amount and breadth of credentials that ServiceNow will need access to - applicative, database, storage etc. - which can be a problem for some security teams within organisations.
The Service Mapping training on ServiceNow university goes into some detail about which technologies are the best fit for which situations.
I hope this helps!
Mat
