Cloud Resource Discovery Schedule with VM Discovery

[Tuna]

My question is about configuring Cloud Resource Discovery. In step 3 (Discover Virtual Machines (optional)) there is an option to create an additional VM Discovery that has the Cloud Resource Discovery as a parent.
We are facing the problem that in some cases the VM Discovery does not work as expected and throws the error that no IP Ranges have been configured.
According to the documentation, IP ranges are not required and according to KB0870860, the IPs are determined by a series of queries starting with the logical datacentre.
Does anyone know how the virtual machine discovery determines the IP addresses to scan? Where does it get the IP Ranges from?

In one case I had to recreate the cloud resource discovery to get the VM discovery working again, but I don't want to reconfigure all the discovery schedules we have.

[Pratiksha]

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

Try this 

[SK Chand Basha]

Hi @Tuna 

Navigate to cmdb_ci_cloud_subnet.LIST 

Where you can see Subnets along with the Object ID

If you enable Discover VMs by IP address in 3rd step

In cloud resources discovery schedule you can VM instance(cmdb_ci_vm_instance) are discovered with Azure - virtual machine LP pattern. 

Mark it Helpful and Accept Solution!! If this helps you to understand. 

[Abdul Parveez]

did you have to manually re-create the schedules or did you get any help from servicenow? I dont think there is any answer to this problem in community.

I have noticed, this mostly happens to some cloud schedules after an upgrade.

[Tuna]

In fact, we had to recreate the affected Discovery Schedules after the upgrade. This solved the problem. With the amount of schedules we have, that was a lot of work. But it's working again now.