Why isn't Azure Cloud Discovery not finding VMs that IP-based is finding

[Robert Polickos]

We are in the middle of a project to implement ITOM Visibility with both IP-based and Cloud Discovery.  When we run Azure Cloud VM Discovery, it finds 2 devices of which only one it classifies as a Windows VM.  When we run IP-based Discovery on the same subnet in which Azure Cloud VM Discovery found and classified 1 Windows VM, there are 5 Windows devices successfully found and classified.  We are confused.  Any insights on why there is a difference in what is discovered would be greatly appreciated.

[Ram Devanathan1]

can you share some more details about the 5 devices discovered? are these VMs - regular compute or more like devices with IP that the azure API does not return?

if you can use azure cli - what do you get when you run azure cli against the same service principal?

[admin60]

Hi Ram,

I am trying to find the network peering in SNOW discovery, I can see all cloud networks but I am not able see network peerings.

We are using Azure cloud

[Robert Polickos]

All,

It turns out that the Service Principal we were provided by the Cloud Services team did not have the proper permissions to discover anything other than the one VM despite asking multiple times if it had global permissions..