List of component from SNOW need to get confirm whether are they licensable

Question

List of component from SNOW need to get confirm whether are they licensable

KAROM PUMPUANG 0

Dear Microsoft Licensing Team,

We are currently reviewing Microsoft software records discovered through our SNOW. The discovery results include complete products, database engine records, features, components, tools, runtimes, and duplicate software signatures. A discovered component does not always confirm that a separately licensable product is installed, so we would appreciate Microsoft’s written guidance before finalizing our software classification and license reconciliation.

We will provide an attached list containing the exact discovery model, version, server/OSE, installation evidence, related Microsoft product, environment type, and our proposed classification for each record.

For each discovery model, please confirm:

Whether it is a separately licensable Microsoft product or component.
Whether it is covered by the license for a parent Microsoft product or edition.
Whether it should be treated as Main product evidence, a bundled feature, a supporting component/tool, a free component, duplicate evidence, or an item requiring further review.
Whether a separate license is required when the component is installed on the same server/OSE as the parent product.
Whether the licensing conclusion changes when the component is installed or operated on a separate server/OSE.
The applicable product edition, license model or metric, and any relevant production, development/test, virtualization, high-availability, disaster-recovery, or access-license conditions.
The specific Microsoft Product Terms, licensing guide section, or other authoritative Microsoft document supporting the conclusion.
Any additional technical evidence required to reach a definitive conclusion.

Our objective is to avoid counting bundled, supporting, duplicate, obsolete, or component-only discovery records as separate license requirements while ensuring that all genuinely licensable Microsoft products are correctly identified and reconciled against entitlement records.

Please state any assumptions or limitations in your response. We would appreciate written confirmation that may be retained as supporting evidence for our software asset management and compliance review.

0 comments

1 answer

Your answer

Answer 1

Hello Karom,

Thank you for posting your question on the Microsoft Windows Forum!

Based on your description, this request goes beyond a typical technical support inquiry and enters the area of Microsoft Software Asset Management (SAM) and licensing compliance assessment.

A key point is that SNOW discovery records alone do not determine licensing requirements. Many discovered entries represent:

Shared components
Runtime libraries
Client tools
Features installed as part of a larger product
Duplicate discovery signatures
Bundled components that do not require separate licensing

Therefore, it is not possible to determine licensing obligations from the discovery model name alone without reviewing the actual software inventory data.

Recommended Approach

1. Prepare the Discovery Inventory

For each discovered item, include:

Product name
Version/build
Server or workstation name
Operating System Environment (OSE)
Installation path
Publisher information
Related Microsoft product (if known)
Whether installed on a separate server or on the same server as the parent product
Your proposed classification

This aligns with the information typically required during a licensing review.

2. Classify the Records

The main categories usually include:

Main Product
Bundled Feature
Supporting Component
Free Component
Runtime
Client Tool
Duplicate Evidence
Requires Further Review

Examples:

SQL Server Database Engine
→ Usually licensable product evidence
SQL Server Native Client
→ Supporting component
SQL Server Management Studio
→ Free tool
Visual C++ Redistributable
→ Runtime component
Microsoft .NET Framework
→ Operating system component

The actual determination depends on the specific product, version, and deployment scenario.

3. Validate Against Microsoft Licensing Sources

The authoritative references are:

Microsoft Product Terms
Product Licensing Guides
Licensing Datasheets
Software Assurance Benefit Guides
Volume Licensing documentation

These sources determine:

Licensing model
Core vs Server/CAL requirements
Virtualization rights
Disaster Recovery rights
High Availability rights
Development/Test rights

4. Consider Separate OSE Installation

One of the most important factors is whether a component is installed:

On the same OSE as the parent product

or

On a separate OSE/server

The licensing conclusion may change significantly depending on the architecture.

Additional Recommendation

Since you're requesting:

Written confirmation that may be retained as supporting evidence for software asset management and compliance review

The Microsoft Q&A forum generally cannot provide authoritative licensing determinations for compliance or audit purposes.

For a formal licensing position, Microsoft typically recommends working with:

Your Microsoft Account Team
A Microsoft Licensing Specialist
Your Licensing Solution Partner (LSP)
Microsoft Commercial Licensing Support

Next Step

Please attach or provide the actual SNOW discovery list (without sensitive information), and the community can help identify:

Which entries are likely licensable products.
Which are bundled components.
Which requires further licensing review.

However, any final compliance determination should be validated against Microsoft's licensing documentation and, where necessary, through Microsoft's licensing support channels.

Useful references:

Microsoft Product Terms: https://www.microsoft.com/licensing/terms
Microsoft Licensing Resources: https://www.microsoft.com/licensing/docs
Microsoft Volume Licensing: https://www.microsoft.com/licensing

I hope this answer has provided you with useful information. If so, please click "Accept answer" and consider upvoting it. This helps other community members find useful solutions to similar problems.

Chance Maurice Niyonzima 415 Reputation points Independent Advisor

2026-10-09T10:48:39.1166667+00:00

Hello Karom,

I wanted to follow up and see whether you had a chance to compile the SNOW discovery list for review.

Were you able to gather the product names, versions, installation evidence, and proposed classifications for the Microsoft components in question?

As mentioned earlier, many SNOW discovery records represent bundled features, supporting components, runtimes, tools, or duplicate signatures and do not necessarily indicate a separate licensing requirement. Reviewing the specific discovery entries is usually required before determining whether a component is independently licensable or covered by a parent product license.

If the information provided was helpful, please consider clicking Accept Answer, as it may help other community members performing similar software asset management and licensing reviews.

Thank you.