Azure VDI consuming ServiceNow license

[Shraddha Dube]

In our ServiceNow environment, we have identified that more than 2,000 Azure VDIs are currently being discovered as EC2 instance VMs through Azure API Discovery. Since each VDI consumes one ServiceNow license, this is causing a significant licensing impact and resulting in inaccuracies on our license utilization.

To address this, we will be implementing a business rule to completely stop Azure VDIs from being created or updated during Discovery runs. 

We consulted with the VDI team regarding the removal of existing VDI records from the CMDB. They confirmed that deleting these records could result in audit issues in the future, as the information may be required for historical or compliance‑related purposes.

Given this constraint, we are evaluating two possible approaches and need clarification:

1. Moving VDI records from cmdb_ci_vm_instance to cmdb_ci_computer

Is it technically feasible and considered a best practice to change the class of all VDI records? We are concerned that reclassifying these CIs might break existing relationships (such as application services, server mappings, and CR references) and potentially corrupt the CMDB data model.

2. Bringing future VDI records into the computer table (instead of VM Instance)

For new VDIs going forward, is it possible to populate the cmdb_ci_computer table through:

• a custom integration or script, or
• SCCM ingestion, if SCCM is able to supply VDI inventory?

We need guidance on whether this is supported, and which method would be the most reliable and CMDB‑compliant for long‑term use.

Please help us understand the feasibility and recommended approach for both of these options.

Thanks in advance!!

[Rohit Ladda]

For future records SCCM Ingestion looks like a good option. Also if not OOTB SCCM Integration, you can also explore JDBC based SCCM custom integration / data source.

For License calculation, do you have any documentation around how ServiceNow is calculating the records, what filters being used? Some tweaks to certain attributes of existing records so they are excluded from calculation could also be a more viable option. For e.g. if ServiceNow considers records in specific lifecycle state for calculation or Most Recent discovered records from last 1 year, you can simply tweak those fields of existing records to get them excluded from counting towards licenses.