Integrate ITAM and FOSM data for hybrid license compliance
Integrating Flexera One IT Asset Management (ITAM) with Flexera One SaaS Management (FOSM) combines SaaS license data, user assignments, and usage data with device-based data. This integration supports hybrid license compliance reporting for products such as Microsoft 365 and Adobe Creative Cloud.
By bringing cloud and device usage together, you can reduce duplicate license records, improve visibility into actual usage, and generate more accurate compliance positions. For example, a user may access Microsoft 365 through both a browser and installed applications. This integration ensures both usage types are considered.
If FOSM is not integrated with ITAM, you may see incomplete vendor visibility, inaccurate compliance positions, duplicate licenses, and increased shadow IT risk due to fragmented SaaS and device usage data.
Understand the integration flows
The integration includes two data flows:
- FOSM to ITAM
Sends SaaS licenses, user assignments, and usage data from FOSM to ITAM. - ITAM to FOSM
Sends device usage data for Microsoft 365 and Adobe Creative Cloud from ITAM to FOSM. - Hybrid license compliance
FOSM captures both usage types and sends them to ITAM for unified compliance reporting. Together, these flows enable a unified view of hybrid usage across cloud and device environments.
Before you begin
Make sure the following prerequisites are complete:
- An active FOSM tenant
- An active Flexera One organization
- The FOSM tenant must be linked to the Flexera One organization in Salesforce (required for all integration flows)
Set up FOSM to ITAM integration
- Configure the Microsoft 365 or Adobe Creative Cloud connector in FOSM.
- In the configuration UI, go to IT Asset Management Settings > General > Integrations.
- Select Enable Flexera One SaaS Management Integration.
If you are transitioning from Flexera SaaS Manager to Flexera One SaaS Management
Do not run Flexera SaaS Manager and Flexera One SaaS Management integrations with Flexera One ITAM at the same time.
- Relink purchases from existing FSM licenses to the new FOSM licenses
- Retire FSM licenses after relinking is complete
If Flexera SaaS Manager licenses are not retired before enabling the Flexera One SaaS Management integration, duplicate licenses may be created.
What happens next
After the integration is enabled:
- License, user, and usage data is sent to ITAM daily
- Data transfer occurs approximately 4 hours before the ITAM IMImport process
- Licenses appear in ITAM with source type: Flexera One SaaS Management
- Supported license types include Named User and SaaS User
Verify FOSM to ITAM integration
The integration is working if:
- Licenses appear in ITAM with source type “Flexera One SaaS Management”
- Usage data includes both cloud and device activity
- Hybrid compliance reports reflect accurate activity
The integration is not working if:
- Licenses do not appear in ITAM
- Compliance reports show missing or duplicated data
- Device usage is not reflected in FOSM
If issues occur:
- Check logs for data transfer errors
- Ensure all purchases from Flexera SaaS Manager licenses are linked to new Flexera One SaaS Management licenses before retiring from FSM. Confirm purchases were relinked correctly
- Delete Flexera SaaS Manager connections to ensure licenses are retired
- Use Business Adapters for large-scale license mapping updates if needed
ITAM to FOSM integration
No additional configuration is required for this integration. Device usage data is automatically exported from Flexera One ITAM to FOSM.
After the organizations are linked during order execution:
- ITAM sends device usage data for Microsoft 365 and Adobe Creative Cloud
- FOSM imports this data daily
Verify ITAM to FOSM integration
To confirm that device usage data is available in FOSM:
- Go to the Microsoft 365 product family page
- Select an application
- Open the Users tab
- Filter by Discovery type: Device
The integration is working if:
- Device activity appears in the Users tab
The integration is not working if:
- No device usage data appears in FOSM