High level , Software asset management needs three integrations to get all the SAM data to work correctly :
1 - Integration with discovery tools SCCM/Intune to collect software installations from End user’s PCs / HandHelds
2 – Saas integration with SAAS providers
Integration with software Saas publishers
3 – Subscriptions
Integrations with the software publishers to get the license usage in order to provide visibility and compliance in SAM reports .
Example :
Microsoft Office O365 Integration: SAM integrates with Microsoft O365 to monitor license usage for Office tools.
The identification of the user is done based on the email address defined in the console (publisher) and the email address defined in the sys_user table .
When collecting data from publishers , the most common issue is that for some users the email address in the console is different from the one recorded in the ServiceNow platform .
From an architecture perspective, it’s a data issue , the first solution that comes in mind is to align the email addresses in both systems .
But for a company with thousands of users the clean up will take time , a workaround need to be identified .
We can work on the data before the import to make the mapping possible .
The SAMSaasIntegrationUtils script include can be customized temporarily .
For a customer the domain in some email addresses was not correct :
In the SAMSaasIntegrationUtils script include :
We modified the following :
By adding a split on the “@” :
This is only a temporary solution , the bad data needs to be cleaned up at the source level.
