Azure Discovery not creating windows/linux server CIs

[peggyl]

We have activated Azure Discovery in our company.  We are trying to understand the OOTB behaviour for when an Azure virtual machine is being discovered.

When an azure virtual machine is detected, will ServiceNow 

1. Create a new CI under the Azure Virtual Machine CI class (cmdb_ci_vm_instance) AND
2. Create another virtualised CI under the relevant OS server CI class (i.e. Windows Server or Linux Server)  AND
3. Relate the Azure Virtual Machine CI to OS server CI (windows/linux server CI) via virtualisation relationship

I wanted to confirm if the above understanding is correct OOTB and does not require any additional configuration.

Thank you.  

[Niklas Peterson]

Hi,

Azure Cloud Discovery will only discover the Virtual Machine instance. The Windows Server or Linux Server will be created by Horizontal Discovery. The horizontal discovery will also create the relationship between the server record and the virtual machine record.

Horizontal Discovery can be triggered as a child schedule to the Cloud Discovery if VM Discovery is selected when creating the schedule or you can schedule it as an ordinary schedule targeting an ip range.

Regards,
Niklas

[Rahul Priyadars]

For OS based discovery you need to trigger Horizontal Discovery as suggested.

Other Details are explained in this KB too

VM Instance and Host VM Discovery - Support and Troubleshooting (servicenow.com)

Regards

RP

[RawelSingh]

Azure cloud discovery is only supposed to populate the VM instances. This can be achieved either by performing horizontal discovery (limitation is that the servers which are turned off will not get discovered) or using Service Graph connector for Azure (This will populate the servers under Server/Windows/Linux classes).

Hope this helps.

Thanks,

Rawel