Microsoft SCCM software usage

  • Release version: Zurich
  • Updated July 31, 2025
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Microsoft SCCM software usage

    The Microsoft SCCM software usage integration enables ServiceNow customers to import software usage data from Microsoft SCCM into ServiceNow's Software Asset Management (SAM) module. This integration supports enhanced visibility into software utilization by syncing usage data with the ServiceNow AI Platform.

    Show full answer Show less

    Two plugins are available for this integration:

    • Integration — Microsoft SCCM 2012 v2 Software Usage (com.snc.sampusagesccm)
    • Integration — Microsoft SCCM 2016 Software Usage (com.snc.samp.usagesccm2016)

    The SCCM 2016 plugin supports SCCM versions 1606, 1906, 1910, and 2002.

    Important: Both SCCM plugins will be deprecated starting with the Tokyo release. New integrations should use the Service Graph connector for Microsoft SCCM, available from the ServiceNow Store. Existing users should use the Migration Readiness Tool to transition to the Service Graph connector.

    Key Features

    • Scheduled monthly imports of SCCM software usage data into ServiceNow.
    • Data is mapped into the Software Usage table and refreshed via a SQL query executed during the import job.
    • Import can be run on demand by adjusting the scheduled import settings, though data always reflects the previous month.
    • Two types of usage data are imported:
      • Last used: shows the last time software was used during the previous month.
      • Total usage: records detailed usage duration down to the second for the previous month, which can result in large data volumes.
    • Usage records aggregate monthly usage to enable assessment of software utilization.
    • Only usage data for products linked to active reclamation rules is imported; the reclamation type must match the scheduled import.
    • User data can be imported and matched against the ServiceNow sysuser table by username; unmatched users are excluded.
    • Configuration item (CI), user, product, and publisher values are used to avoid duplicate usage records for the same month and year.
    • Usage data can also be imported using ServiceNow import sets as an alternative method.

    Practical Considerations for ServiceNow Customers

    • Activate the appropriate SCCM plugin based on your SCCM version, or plan migration to the Service Graph connector for future compatibility.
    • Configure reclamation rules correctly to ensure software usage data is imported as expected.
    • Schedule and monitor monthly imports to maintain up-to-date usage insights for software asset management.
    • Understand the difference between last used and total usage data to optimize reporting and storage.
    • Ensure user and CI data consistency to prevent data duplication and improve accuracy.

    Activate the Microsoft SCCM software usage plugin to integrate your software usage data with the ServiceNow AI Platform.

    One of the following Microsoft SCCM Software Usage plugins must be installed to import software usage data from Microsoft SCCM to Software Asset Management.
    • Integration — Microsoft SCCM 2012 v2 Software Usage (com.snc.samp_usage_sccm) plugin
    • Integration — Microsoft SCCM 2016 Software Usage (com.snc.samp.usage_sccm_2016) plugin

    The Integration — Microsoft SCCM 2016 plugin is compatible with SCCM version 1606, 1906, 1910, and 2002.

    Important:
    Both Microsoft SCCM plugins will be deprecated in the Tokyo release. If you are integrating with SCCM for the first time, request and install the Service Graph connector for Microsoft SCCM application from theServiceNow Store instead. If you have already activated one of the Microsoft SCCM plugins on your ServiceNow instance, use the Migration Readiness Tool for Service Graph Connector for SCCM store application to prepare your instance for migration from the Microsoft SCCM plugin to the Service Graph connector. See Service Graph connector for Microsoft SCCM for more information on the Service Graph connector.

    The SCCM integration plugin installs several components.

    After the SCCM usage plugin is activated and configured, a scheduled import runs monthly to bring SCCM software usage data into your instance. The usage data is then mapped to Software Usage table. During the scheduled job, a SQL query is executed.

    The scheduled import runs once a month, but you can run the import on demand by clearing the Conditional option on the Scheduled Data Import form. However, the data is always pulled from the previous month, so there won't be a change in the data until the following scheduled import.

    Note:
    The SCCM software usage data source can't be executed directly because the SQL statement doesn't actually pull in the data, so the records aren't retrieved. A valid SQL statement on the data source is updated dynamically though a scheduled import. So, if you need to pull the data into your ServiceNow instance, use the scheduled import.

    There are two types of data (total usage and last used) that you can extract from SCCM and import into your instance. Last used data will only show the last time the software was used during the previous month.

    Total usage data will show down to the second when the software was used in the previous month, which can be a large amount of data imported into your instance. A usage record tracks the sum of usage on a monthly basis so that you can assess the software usage in your environment.

    Depending on what you've specified in the reclamation rule for the product, one of the following scheduled imports will run to pull in the data.
    • SAMP Usage Import
    • SAMP Usage 2016 Import
    • SCCM 2012 v2 Software Last Used
    • SCCM 2016 Software Last Used
    Note:
    Only usage data for products associated with a reclamation rule is imported. The Reclamation type field on the Reclamation Rule form must match the scheduled import that you are running, otherwise the data is not pulled into your instance. For more information, see Create a reclamation rule to import Microsoft SCCM usage data.

    You can also pull in user data from SCCM. User data is compared to the user_name field of the sys_user record. If the names don't match, the user data isn't imported.

    Note:
    Configuration item (CI), user, product, and publisher values are used to identify a matching software installation.

    Duplicate usage information cannot be created for the same CI, user, product, or publisher values in the same month and year.

    You can also import usage information using ServiceNow import sets feature.