Cloud Discovery for Azure is not discovering Virtual Machines

[SSK2]

Hi All,

We turned on Cloud discovery for Azure with the option on the schedule to discover the virtual machine, which created two scheduled for Service & IP based as expected.

When discovery ran it discovered all cloud resources, but none of the virtual machines was discovered. 

Que:

Does the cloud Service Account added is enough to discover the virtual machines in the cloud? or do we need to add separate WMI credentials for the virtual machines?

Error:

When the Virtual Machine schedule run it fails during "HTTP - Classify" with the error "Active, couldn't classify"

Can anyone able to help with what's required to discover virtual machines in cloud discovery?

Really appreciate any help, many thanks

[shloke04]

Hi @SSK 

See if below two link help you here:

https://docs.servicenow.com/bundle/sandiego-it-operations-management/page/product/discovery/concept/azure-cloud-discovery.html

https://www.youtube.com/watch?v=MjG__siORn4

Hope this helps. Please mark the answer as correct/helpful based on impact.

Regards,
Shloke

[SSK2]

Many thanks, Shloke for the link.

Both links don't really explain whether just Azur Service Account will be sufficient with cloud virtual machine discovery or not.

[BozhidarNizamov]

The sequential discovery of virtual machines in Azure works just like regular IP based discovery - you will need the appropriate credentials (WMI for windows) and open network traffic on the correct port (443). you might want to have the MID server installed within the Azure cloud or you will need to configure and allow the traffic from the MID to the cloud.