Cloud discovery for Azure vs Service Graph connector Azure

[sukran]

For Azure discovery , we can use cloud discovery in Servicenow 

But there is another option for Service Graph connector for azure 

Is there any difference scenario to be use for cloud vs service graph connector for azure ? or its our wish to be choose ?

Any Insight ?

[Sunny14]

Hello @Rahul Priyadars 

Could you please provide similar table for the AWS as well? 

Thanks,

Sunny.

[Rahul Priyadars]

@Sunny14 

Try below URL

Amazon AWS Cloud Discovery (servicenow.com)

Regards

RP

[Sunny14]

Thanks @Rahul Priyadars 

[FLP1]

Hello @Rahul Priyadars and @sukran according to what you are pointing out here, from the KB article for Service Graph connector it states the below azure components can be used, from what i am reading this part is almost bringing partially what horizontal discovery does... do you know what is this about please correct me otherwise.

thank you!

Azure components and API used

Change Tracking and Inventory

Change Tracking Inventory feature tracks changes in virtual machines hosted in Azure, on-premises, and other cloud environments to help you pinpoint operational and environmental issues with software managed by the Distribution Package Manager

Change Tracking and Inventory natively tracks:

• Software changes
• Windows services
• Linux daemons

Enabling all features included in Change Tracking and Inventory might cause additional charges. Before proceeding, review Automation Pricing and Azure Monitor Pricing

Azure Graph API

Importing Hardware Cis from Azure