Is Discovery Map required for SW Reconciliation?

[RahulY00040]

Hello friends,

I would like to understand if Discovery Map is required for effective and complete SW reconciliation?

I saw few SW models and they were reconciling successfully even if Discovery Map is missing.

In face, even if discovery map is missing UI action on SW Model record shows Matching Discovery Models. So would like to understand if its required for Reconciliation? Also, what's the significance of fields such as Version condition, edition condition, etc. Is it to locate the SW Discovery Models?

Thanks in advance,
Rahul Yamgar

[Vikram Reddy]

Hi @RahulY00040 ,

Discovery Map is not always mandatory for software reconciliation, but correct discovery-model matching is mandatory.

A Software Model can reconcile without the Discovery Map field populated if it has enough matching criteria directly on the Software Model, such as Publisher, Product, Version condition, Version, Edition condition, Edition, Platform, Language, and Software install condition.

ServiceNow documentation says a Discovery Map is a set of conditions that determines which Software Discovery Models are mapped to Software Models. It also says you can use the provided discovery maps, or specify the condition information directly. That is why you may see Software Models reconciling successfully even when the Discovery Map field is blank.

The “Show Matching Discovery Models” UI action can also return matching discovery models even when Discovery Map is missing, because it evaluates the Software Model’s publisher/product and mapping conditions. It does not necessarily require the Discovery Map field to be populated.

Example 1: Simple product with broad matching

Publisher: Adobe
Product: Acrobat Reader
Version condition: is anything
Edition condition: is anything
Discovery Map: empty

This can still reconcile because the model can match discovery models using publisher/product and broad version or edition criteria.

Example 2: Version-specific licensing

Software Model: Microsoft Project 2021 Standard
Version condition: starts with
Version: 2021
Edition condition: is
Edition: Standard

This can match discovery models such as Microsoft Project 2021 Standard or Microsoft Project 2021 Standard 16.0. It should not match Microsoft Project 2019 Standard or Microsoft Project 2021 Professional.

Example 3: Edition-specific licensing

SQL Server 2019 Standard and SQL Server 2019 Enterprise may have similar publisher/product/version values, but the licensing is different. If the Edition condition is too broad, reconciliation may incorrectly apply Standard rights to Enterprise installs. In this case, either the Discovery Map or the direct Edition condition must be accurate.

Example 4: Suite products

For products like Microsoft Office Professional Plus, the Discovery Map is much more important because suite components such as Word, Excel, PowerPoint, and Outlook may be involved. Discovery Maps and suite definitions help determine which component discovery models are covered by the suite entitlement. Without correct mapping, reconciliation may count components incorrectly or show them as unlicensed.

Example 5: Downgrade rights

Purchased: SQL Server 2022 Enterprise
Installed: SQL Server 2019 Enterprise

If downgrade rights apply, the 2022 entitlement may cover the 2019 installation. Discovery Maps and related SAM content help determine which older versions are covered. Without proper mapping, older installations may show as unlicensed even though the entitlement should cover them.

Example 6: Platform or language-specific software

If Windows and macOS editions are licensed differently, or English and multilingual packages are licensed differently, the Discovery Map or direct Platform/Language conditions help prevent overmatching across platforms or languages.

Example 7: Software install condition

If Visual Studio is licensed only for non-production machines, you can use a Software install condition to include only those installations during reconciliation. Installs outside that condition may still appear in reconciliation, but they may be flagged as unlicensed unless another Software Model covers them.

Discovery Map is not strictly required in every case. Reconciliation can work without it if the Software Model’s direct conditions correctly match the relevant Software Discovery Models. However, for accurate reconciliation, especially for suites, downgrade rights, upgrade rights, edition-specific licensing, platform/language-specific licensing, and complex publishers like Microsoft, Oracle, IBM, Adobe, or VMware, using the ServiceNow Content Service Discovery Map is recommended.

If a Discovery Map is missing but reconciliation appears successful, validate the Matching Discovery Models list carefully. Make sure the matching is not too broad or generic, the Discovery Models are normalized, the product type is licensable, and the correct Software Model is being referenced.

Final rule: Discovery Map is not mandatory in all cases, but correct discovery-model matching is mandatory.

Thank you,

Vikram Karety

ServiceNow Architect

Octigo Solutions INC