Azure VDIs not getting excluded from ITOM Server License count - Known Error

Azure VDIs not getting excluded from ITOM Server License count Description Issue: Azure Virtual Desktop Infrastructure (VDI) virtual machines are incorrectly counted as Servers in ITOM licensing calculations.

Description:

Currently, there is no direct or reliable attribute available in all scenarios to identify Azure Virtual Desktop (VDI) VMs during discovery.

As a result:

All Azure VMs are classified under Server CI category for ITOM licensing. This leads to incorrect server license consumption , as VDIs should be excluded from server licensing calculations. To address this, the ITOM Licensing team introduced a fix in PRB1929395 .

Root Cause:

Azure Virtual Desktop VMs created using custom images (not marketplace images) do not contain consistent identifiers that allow discovery or licensing logic to automatically classify them as VDIs.

Because of this limitation:

These VMs are discovered into cmdb_ci_vm_instance ITOM licensing logic treats them as Server licenses (1:1) instead of exempting them as VDIs. ITOM Licensing Implemented Fix: Release: SR – ITOM – ITOM Licensing – 202512

Fix Logic: VDI exclusion is now handled via the itom_license_exclusion_metadata table.

A VM will be excluded from server licensing if:

The CI has a tag: Key : licenseType Value : Windows_Client Configuration Item : reference to cmdb_ci_vm_instance class When this condition is met, the VM is automatically exempted from ITOM Server license count.

Steps to Reproduce

Create an Azure Virtual Desktop pool with a custom image and not from the default market place image gallery Run Azure Cloud Discovery Observe: VMs are created under cmdb_ci_vm_instance ITOM licensing counts them as Servers They are not excluded as VDIs. Workaround To prevent Azure VDIs from being counted as Server licenses, use one of the following options:

Option1: Azure Console side Tagging

Add the following tag directly to Azure VDI VMs in Azure Console:

Name : licenseType Value : Windows_Client After cloud discovery runs:

the tag will populated in Key Value ( cmdb_key_value ) table Configuration Item reference to cmdb_ci_vm_instance record. This ensures the VM is automatically excluded from ITOM Server licensing calculations.

Option2: ServiceNow Business Rule Approach:

Create a new Business Rule on the cmdb_ci_vm_instance table:

1. Identify Azure VDIs using specific conditions (Example: resource group, naming pattern, Image type).

2. Create a cmdb_key_vlaue record:

Key : licenseType Value : Windows_Client Configuration Item : Reference to the VM CI record. This Key Value records allows the licensing logic to properly exclude the VM from server license counts.

Note:

The conditions used to identify Azure VDIs in the Business Rule are customer-specific and vary by environment. Therefore, an OOTB rule cannot be provided.

Impact If this issue is not addressed:

Azure VDIs will continue to be incorrectly counted as Server license. This may lead to inflated ITOM licensing consumption and inaccurate license reporting . Related Problem: PRB1958219