ITOM deep-dive · LessonBy Neelima, ServiceNow Architect · Published · ServiceNow · all levels
Cloud discovery
Discover cloud resources, map them to CI classes and keep costs and tags aligned.
Quick answer
Discover cloud resources, map them to CI classes and keep costs and tags aligned.
Key takeaways
- Cloud discovery uses provider APIs, not network probes
- Scope regions and services deliberately
- Tags carry ownership and cost context into the CMDB
- Untagged resources are a governance problem, not a discovery bug
How it differs
Cloud discovery calls provider APIs rather than probing IP ranges. You register a service account per account or subscription, pick the regions and services, and the platform creates logical datacenter, virtual machine and storage CIs.
Scheduling and scope
Cloud estates change constantly, so schedule discovery more frequently than on premise scans but scope it. Discovering every region when you use three is a common and expensive mistake.
Practice challenge
+0 XPStreak ×0
Question 1 of 2
What replaces IP range scanning in cloud discovery?
Frequently asked questions
Do we still need a MID server?
Yes for most patterns, and the MID needs outbound access to the provider endpoints. Some configurations support direct calls, but the MID is the common route.
How do we avoid duplicates with on premise discovery?
Identification rules distinguish cloud instances by provider identifiers. Confirm those rules before running both against hybrid workloads.