Azure Cloud VM Discovery failing with 'The Discovery range is empty.'

[MMGF]

We have several cloud schedules created. All of them completed successfully and then trigger the corresponding VM Configuration Item discovery schedule.

However, for one of them the cloud resources discovery completes successfully and finds 39 VM Instances. But when the triggered CI discovery schedule is triggered it fails immediately with the message "The Discovery range is empty."

All schedules use the same specified MID server. 

WHy would we be getting this error message?

[Community Alums]

Hi @MMGF ,

The issue can be resolved once the schedule is recreated with the correct MID server cluster with the IP Ranges mentioned again.

Steps:

1. Navigate to Discovery schedules and create a new discovery schedule "Schedule the old"
2. Add the discovery IP ranges from the schedule where the discovery is canceled with no devices discovered to "Schedule the old"
3. Run the discovery on new schedule "Schedule the old" and check the discovery status.

[BartekM]

we had a similar issue on one of our customer instances. It turned out that a user used as run as in the child schedule didn't have required roles. The scripts used in the process do checks for the roles and will fail if those are not present on run as account, the symptom of it is the same - child schedule cancelled with error - No IP ranges

[BartekM]

sorry the actual error was The Discovery range is empty