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.

[Amar_Be]

I'm don't want to add the OS to the VM.

We are in the scope of the service Graph integrator for Azure, which import data from Azure. Thus, it is working on VM's, where an OS is installed.

Refere to the doc of Azure and the Service Graph Connector for Azure.

[Rohit N]

@Amar_Be :

This issue still exists. Although the "Is VDI Computer" decision table confirms that the Azure VM is a VDI Computer device based on the "SN_IS_COMPUTER" tag, if the VM is in an OFF state, the Final CI Class transform logic in SGC-Azure ignores the "Is VDI Computer" value and classifies the CI under the default Server class instead.

We opened a support ticket to understand the reasoning behind this logic and this was the explanation provided.

After reviewing with our dev team, this is a limitation from Azure when power state is off, the OS info is not available and customers rely on OS info to do classification if it is VDI or not. If the check is removed, for customers using OS, would experience a flip flop issue, which was fixed in PRB1929577.
Even though the CI is initially created in the server class when it's in the OFF state, once the same CI comes in ON status, it gets reclassified as a computer.
It will remain in the computer class even if it later returns to the OFF state. SG Azure won't move it back to the server class. Therefore, VDIs must come online at least once so the OS information can be captured.

An idea has already been raised to address this issue. Please review it and vote for it if you think it makes sense.

https://support.servicenow.com/now?id=view_idea&sysparm_idea_id=f39f7c96932887147c79b36d6cba10c2&sys...