OBLYTECH Logo
OBLYTECH Logo

Software Usage Metering in SAM: Data Sources and Reclamation

Software usage metering in SAM records how often and how long each product runs, then sets that activity against the licenses you hold. Usage arrives from Microsoft SCCM, Microsoft 365 APIs, Jamf, ACC-V and manual entry. Reclamation rules decide which usage counts as idle and which installations become removal candidates.

What usage metering records in SAM

Usage metering tells SAM whether an installed product is in use. The Software Usage table tracks usage at product level, so version and edition are not split out there. Each record links a configuration item, a user, a publisher and a product. Total usage records also carry a month, a year, a usage count and total seconds used; last used records carry a last used time.

Two reclamation types exist, and they measure different things.

Reclamation type What the record holds What the rule compares against
Total Usage Time A monthly usage count and total seconds used Total hours used over an aggregation window
Last Used Date The date and time the product was last used The period a user can leave software unused

Total usage is a monthly sum, so each usage record covers one month of use. Last used reflects the most recent use in the previous month.

Where the usage data comes from

Source Platform Products covered Where it lands
Microsoft Graph APIs Desktop, web and mobile Outlook, Word, PowerPoint, Excel, OneNote, Teams, Exchange Online, SharePoint Online, Power BI Software Usages and Microsoft 365 Apps Usage Reports
Microsoft SCCM or ACC-V Desktop Office 365 apps for Enterprise Software Usages
Jamf Desktop (macOS) Office 365 apps for Enterprise Software Usages
SCCM usage plugin Desktop Products that have a reclamation rule Software Usage

Setting up the SCCM usage import

Three decisions shape an SCCM usage import: the plugin, the reclamation rule, and the timing of the data.

Choose the right SCCM plugin

Two plugins import software usage from SCCM: the 2012 v2 plugin and the 2016 plugin. The 2016 plugin is compatible with SCCM versions 1606, 1906, 1910 and 2002. Both are slated for deprecation in the Tokyo release.

For a first-time integration, the current route is the Service Graph connector for Microsoft SCCM, installed from the ServiceNow Store. If a plugin is already active, the Migration Readiness Tool for that connector prepares the move. The integration setup is covered in the SCCM integration guide, so this section stays on usage.

Build the reclamation rule first

Usage reaches the instance for products that have a reclamation rule. Create one from All > Software Asset > Administration > Reclamation Rules, with the sam_admin role.

The form asks for a name, the software type it applies to (installed software or an engineering app license), the reclamation type, and an optional notify-user checkbox that emails the assigned user for permission to remove the software. Then complete the section for your reclamation type:

  • Total Usage Time: pick an aggregation window (last month, last two, three or six months) and a total hours threshold, meaning the time the software must be used to avoid reclamation.
  • Last Used Date: set the last used before value, meaning how long a user can keep the software unused before it is reclaimed.

Each product also needs a product process, which holds the filename the SCCM pull depends on. If none exists, add a custom product process with the product name, file name and platform. The content library also adds new product processes twice a week, so check again later if the product still has none.

As a worked example, a rule for Microsoft Excel can use Total Usage Time, aggregated over the last month, with a threshold of 20 total hours. Excel has two product processes in this setup. The data arrives at the next monthly import.

Know when the data arrives

The SCCM import runs monthly by default. You can run it on demand by clearing the Conditional option on the Scheduled Data Import form, but the import pulls the previous month either way. A rerun changes nothing until the next scheduled import brings in a new month.

Reclamation type Scheduled import (2012 v2 / 2016) What it brings in
Total Usage Time SAMP Usage Import / SAMP Usage 2016 Import Monthly usage down to the second
Last Used Date SCCM 2012 v2 Software Last Used / SCCM 2016 Software Last Used Last use during the previous month

The reclamation type on the rule must match the import you run. A mismatch means the data is not pulled, even though the rule exists.

Two matching rules also shape what lands. SCCM user data is compared with the user_name field on the user record, and names that do not match are not imported. Installations are matched on configuration item, user, product and publisher, and a duplicate usage record is not created for the same combination in the same month and year.

Reading usage in the workspace

The License usage view (Software Asset Workspace > License usage) shows a card per publisher with a colour-coded compliance status, the over-licensed amount and true-up cost, and sorting by true-up cost, over-licensed amount or potential savings. Its Reconciliation tab lists each run as Completed, Failed or Partially Completed. Its Reclamation tab consolidates reclamation across publishers, SaaS integrations, installed software and reconciliation flows.

The License usage analysis view answers a narrower question: why a product’s installations are or are not licensed. Its four-level node map runs from the product, to its versions and editions, to the consumption status of each installation (licensed, unlicensed, ignored or requiring action), to the licensing result. A useful check is that total installations equal used plus not-used installations.

The workspace also reports true-up cost (the estimated cost of covering unlicensed installations at the lowest number of rights needed), over-licensed amount (the estimated cost of rights not in use) and potential savings (the cost saved if removal candidates are reclaimed).

Reconciliation runs weekly by default and can also be started on demand.

Manual usage records

An admin with the sam_admin or sam_user role can also create a software usage record by hand, from the Core UI or the Software Asset Workspace path below. In Core UI the path is All > Software Asset > Discovery > Software Usage. In the Software Asset Workspace it is Workspaces > Software Asset Workspace > License operations > Discovery > Software usage. In the workspace, the Core UI option to view or create usage is inactive.

A record holds a publisher, a product, a reclamation type, a configuration item and a user. Total usage records add a month, a year, a usage count and total seconds used. Last used records add a last used time.

One behaviour is easy to miss. If a configuration item’s CI Status or Hardware Status changes to Retired or Stolen, the installations related to that CI are deleted.

Microsoft 365 usage and subscription signals

Usage activity also drives optimisation of Microsoft 365 subscriptions. Recommendations fall into four groups: overlapping, low usage, downgrade and consolidated.

Overlap happens when active subscriptions provide the same services at the same time. The worked example is an Office 365 E3 subscription running alongside a Microsoft 365 E3, which duplicates Office applications. The recommendation is to reclaim the Office 365 E3.

Downgrade recommendations depend on the condition that was found:

Condition found Example downgrade
No Power BI usage Microsoft 365 Enterprise E5 to E3
Shared mailbox Microsoft 365 E3 or E5 to Exchange Online Plan 2
No desktop usage Microsoft 365 E3 to F3
Mailbox and OneDrive under 2 GB Microsoft 365 E3 to F3

For E3 to F3, the mailbox and OneDrive size check (under 2 GB each, from the Software storage usage table) runs after the desktop-usage check. Mailbox and OneDrive sizes come from the Software storage usage table, which records the user principal name, subscription profile, storage allocated and used in bytes, product, and whether the account is deleted. The conditions and their target editions sit in their own configuration tables, which is where to check a recommendation before acting on it.

Consolidation merges several subscriptions into one. The example is an Office 365 Enterprise E5, Windows and EMS set replaced by a single Microsoft 365 Enterprise E5 license. The subscription assignment date from the Microsoft 365 portal is used for this rather than the date the record was created in the instance, so candidates reflect actual use.

Frequently asked questions

Can I enter usage data myself?

Yes. A user with the sam_admin or sam_user role can create a software usage record for a product and user.

What is the difference between total usage and last used?

Total usage is a monthly sum shown to the second. Last used is the most recent use in the previous month, so it suits inactivity rules.

Why is a product missing from the SCCM usage data?

Check three things: the product has a reclamation rule, the reclamation type on that rule matches the import being run, and the product has a product process with a filename. User names that do not match the instance’s user records are also skipped.

Which SCCM plugin should a new team install?

A first-time integration should use the Service Graph connector for Microsoft SCCM from the Store, because both SCCM plugins are slated for deprecation in the Tokyo release. Teams already on a plugin can prepare the move with the Migration Readiness Tool.

For the reclamation side, the reclamation rules guide covers the rule logic in more depth, and the Software Asset Management hub lists the wider set of SAM Professional topics.