Overview

The SAM–M42 Pro integration uses M42 Pro's built-in Generic REST API connector — no separate installation is required. It keeps your M42 Professional (M42 Pro) environment continuously enriched with up-to-date device, software, and SaaS application data. All data is retrieved from a single source: M42 SAM (Software Asset Management). 

Instead of maintaining device inventories, software records, and SaaS application lists manually, the connector does this automatically on a daily schedule. The result is a live, accurate Configuration Management Database (CMDB) that provides your IT service management processes — incidents, changes, and problem management — with the asset context they need to be effective.

How the Connector Works

The Generic REST API connector, configured within M42 Pro, pulls all data from M42 SAM automatically on a recurring schedule and writes it into M42 Pro. No manual exports or imports are needed — the synchronization happens in the background without any user action required.

Architecture

The diagram below shows how data flows from the source systems into M42 Pro and how the enriched records connect to ITSM processes.

Synchronization Process

Each synchronization run follows a consistent sequence:

1. The connector reads its configuration settings from M42 Pro, including which data types to fetch and how fields should be mapped.
2. It queries the M42 SAM API to retrieve the latest device, software, and SaaS application data. M42 SaaS Management data is included in M42 SAM's API responses and does not require a separate connection.
3. Retrieved data is mapped field-by-field from the source format to the M42 Pro data model.
4. Mapped records are created or updated in M42 Pro — existing records are updated in place, and new records are created automatically.

What Data Is Synchronized

The connector brings in three categories of data, each corresponding to a specific record type in M42 Pro. The mapping tables below show exactly which fields are read from the source system and where they land in M42 Pro.

Devices

Hardware devices discovered by M42 SAM are synchronized into Device records in M42 Pro. This keeps your CMDB populated with accurate, real-world device information — including who the primary user is, what operating system is running, when the device was last seen, and whether it is approaching end of life.

Device records in M42 Pro can be linked directly to incidents, changes, and problem records, giving your service desk team immediate hardware context when resolving issues or planning changes.

Installed Software on Devices

The software installed on each discovered device is synchronized into Software Version records in M42 Pro. For every application found running in your environment, the connector records its name, version, license type, and current status.

Having installed software linked to specific devices makes it straightforward to answer questions like "which devices are running an outdated or end-of-life version of this software?" — information that is essential for compliance reviews, vulnerability assessments, and change impact analysis.

SaaS Applications

SaaS application data discovered by M42 SaaS Management is surfaced through the M42 SAM API and synchronized into Application records in M42 Pro. This includes not just the application name and publisher, but also usage data — how many accounts have been detected, how many are actively used, and when the application was last accessed.

SaaS records in M42 Pro give your organization a consolidated view of the cloud application portfolio alongside on-premise assets, supporting informed decisions about software renewals, license optimization, and governance compliance.

Key Benefits

Richer ITSM Context

When an incident, change, or problem record is created in M42 Pro, the connector's data is already there. Service desk agents can see which device is involved, what software is installed on it, and whether any related SaaS applications are in use — without switching to another tool or waiting for someone to look it up.

• Incidents – Quickly identify the affected device and its software context to speed up root cause analysis and resolution.
• Changes – Understand the full scope of a planned change by seeing which devices and software versions are affected, and assess compliance or end-of-life risks before approving.
• Problems – Spot patterns across devices, such as a recurring issue tied to a specific software version or operating system, and address the root cause rather than individual symptoms.

Software Compliance and Lifecycle Visibility

The connector brings end-of-life dates and software version information directly into M42 Pro. This means your team can proactively identify devices running software that is approaching or past end of support, enabling timely upgrades and reducing security exposure without relying on manual audits.

SaaS Governance and Spend Awareness

By surfacing SaaS application usage data — including the number of accounts detected versus accounts actively used — the connector helps identify underutilized subscriptions. This information supports decisions about license rightsizing, contract renewals, and overall SaaS portfolio governance, all from within M42 Pro.