How Microsoft bundle software reconcile in SAM Pro?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi All,
I am currently configuring Microsoft products and need some guidance regarding software reconciliation for bundled licences.
We have several Microsoft bundle licences in use, such as:
- Enterprise Mobility + Security E3
- Microsoft 365 E3
- Other Microsoft licence bundles
In the Software Installation records, the discovery data captures the individual software product names rather than the bundled licence names. As a result, I am unsure how these bundle products should be configured in the Product Model/Product table for reconciliation.
I have also noticed that many of these bundled products are not available in the Content Library. Is there any specific configuration required to:
- Reconcile bundled Microsoft licences with discovered software installations?
- Retrieve licence entitlement information from the Microsoft Admin Centre?
- Enable recognition of Microsoft bundle products that are not present in the Content Library?
If anyone has implemented a similar requirement, I would appreciate your guidance on the recommended approach and any configuration prerequisites.
Thanks in advance for your help.
Regards,
Balaji Prusty
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @balaji_prusty1,
Discovery will always report the individual executables, Word, Excel, Teams, Intune and so on, never the licence SKU name, so that part is expected behaviour. What you need is to model the bundle as a suite so reconciliation can roll those components up into it. Here's how that maps to your three points:
- Reconciling the bundle: create the bundle itself (Microsoft 365 E3, EMS E3, etc.) as a parent software model, then add each discovered component product to that model's Suite Components relationship. Reconciliation attributes the component installs up to the parent, and you set the inference percent on components that can also be licensed standalone.
- Pulling entitlement data from the Admin Centre: use the native Microsoft 365 integration rather than any custom API call. Install the Software Asset Management - SaaS License Management plugin (com.sn_sam_saas_int) and the Microsoft Entra ID Spoke, register an app in Entra ID, then create a Microsoft 365 integration profile. That profile auto-generates software models with suite components already mapped and pulls subscribed SKUs and consumption straight from the Admin Centre, you just add the owned entitlement quantities on top.
- Bundles missing from the Content Library: the Microsoft publisher pack covers the common SKUs but not every regional or legacy bundle. Build the suite model manually as in point one, use a Custom Publisher Part Number so it normalizes on future imports, or raise a case with ServiceNow's content team to get the missing part number added.
Thank you,
Vikram Karety
Octigo Solutions INC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Thanks, Vikram, for the response.
I have configured Microsoft 365, and it is pulling software usage and software subscriptions. But it is not updating the product and software entitlement table for the license. Is there anything extra I need to configure for this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @balaji_prusty1 ,
Your Products will be updated by content services and entitlements are something that you own as rights which includes unit cost and rights, that is somethiing you need to enter manually no OOTB integration does that
Thank you,
Vikram Karety,
Octigo Solutions INC