Horizontal discovery is not getting trigger for some of the Azure VMIs.

[Shreya Jain1]

We have Azure Cloud Discovery in place to discover both Cloud Resources and Horizontal IP based discovery.

IP address information is missing  for some of the Azure VMIs due to which Horizontal discovery don't get trigger for those devices. (Horizontal Discovery schedule for cloud don't require IP ranges to be defined as it automatically gets IPs from NIC "cmdb_ci_nic" table as per below KB).

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0828888

What we observed is if no public IP address is discovered for cloud account in "Azure - Public IP (LP)" pattern, NIC pattern "Azure - NIC (LP)" don't get trigger resulting no private IP address getting discover for any of the VMIs in that cloud account. 

Some of the cloud accounts won't have public Ip address but that shouldn't have dependency to discover NIC. Please let me now if anyone encounter similar issue where IP address/NIC info is missing for VMIs resulting no horizontal discovery for those accounts?

[Niklas Peterson]

Hi,

I seem to have the same problem. We have 2 out of 5 subscriptions not finding IP addresses for VMs. @Shreya Jain1 your observations seems to apply to our case as well. The "Azure - Public IP (LP)" is not picking up a public IP for the 2 subscriptions. IP address is not populated on the VMs, no NICs created and the VM schedule gets cancelled due to no discovery range.

@Ram Devanathan1, any thoughts? Doesn't seem right that discovery of VM NICs requires a public IP on the account?

Regards,
Niklas

[Shantanu1]

Hi @Shreya Jain1 , @Niklas Peterson 

Checking if you ever received a solution on this?

Thanks,

Shantanu

[Niklas Peterson]

Hi,

Yes, changing the trigger rule  for the Azure - NIC (LP) pattern solved the issue.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1288346

Regards,
Niklas

[Shantanu1]

Thanks for the response @Niklas Peterson , much appreciated!