What is cons and pros of azure cloud discovery and Service graph connector Azure in ServiceNow?

Sandeep _
Tera Contributor
 
1 ACCEPTED SOLUTION

Ram Devanathan1
ServiceNow Employee
ServiceNow Employee

The cloud discovery with patterns (based on Azure API) is reliant on mid server, to do server /OS / process discovery in cloud (via IP discovery) more mid servers would be needed and separate schedules.

 

ServiceGraph connector does not need Mid as it directly connects from instance, using integration hub orchestration but it relies on Azure analytics service to be enabled in each region. also requires less permissions setup.

View solution in original post

4 REPLIES 4

Ram Devanathan1
ServiceNow Employee
ServiceNow Employee

The cloud discovery with patterns (based on Azure API) is reliant on mid server, to do server /OS / process discovery in cloud (via IP discovery) more mid servers would be needed and separate schedules.

 

ServiceGraph connector does not need Mid as it directly connects from instance, using integration hub orchestration but it relies on Azure analytics service to be enabled in each region. also requires less permissions setup.

Rahul Priyadars
Giga Sage
Giga Sage

Azure Cloud discovery populates data for both Cloud Resources and full horizontal discovery too.

I see SGC for azure populates data but restricted to fewer classes.

 

https://docs.servicenow.com/bundle/rome-servicenow-platform/page/product/configuration-management/co...

 

Regards

RP

Thankyou Rahul for this reply but i need to difference between SG-Azure and azure cloud discovery.

FLP1
Tera Contributor

is there some one doing cloud discovery today? i need to do scan for all clouds and i am trying to identify the best course of action if GRAPH CONNECTOR or standard MID DISCOVERY