Service Graph Connector for Microsoft Azure and OS information

[Amar_Be]

Hi,

In the release note of version 1.13.0 of the service graph connector for Azure , an issue is supposed to be fixed :

"

• Fixed
  • Resolved the issue where OS information was not received for deallocated or terminated VMs, so that classification occurs only when the VM is in the 'on' state.

"

Has anyone been able to retrieve the correct Operating System info from a VM that is stopped?

I would like to have some feedbacks before opening, at the support, a new case about the OS info.

The previous case remained open for 6 month and I want to be sure if it is working or not as described.

We have correctly configured the decision table as stated in the knowledge base (https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2184443) and the info are correctly retrieved when the VM is running.

[Will O]

Hi Amar_Be.  I followed KB2184443 to ensure SG-Azure classifies VDIs as Computer (instead of Server) based on Tags.  However, if the VDIs are powered off when SG-Azure runs, they are still reclassified back to Servers (even though the KB states anything "off" should be left alone and ignored). 

Not a great answer, but I would suggest reaching back out to support regarding a potential upcoming fix to address updating CIs when SG-Azure runs and the VM is off.

[Pratiksha]

@Amar_Be 

https://www.servicenow.com/community/itom-articles/get-os-details-on-virtual-machine-instance/ta-p/3...

check this out. It will give you idea

[Amar_Be]

Hi Thank you for your answer.

But the Service Graph connector is not using patterns.

The idea here is not to customize the application but to test if what is supposed to be fixed is really fixed.

But it seems that it is not the case. 

[Pratiksha]

Yes, if you are using it via api then this will not work. But you should be getting the info in the respective server table with SGC. Their should be relation between VM and server. Why you want to mention it on VM table?