Azure SSO integration profile does not pull Software usage informationIssue Azure SSO integration profile is created to retrieve the software usage information as part of Software Asset Management application. Please refer to the docs below for details on Software Asset Management and the Azure SSO integration profile : https://docs.servicenow.com/bundle/paris-it-asset-management/page/product/software-asset-management2/concept/c_SoftwareAssetMgmt.html https://docs.servicenow.com/bundle/paris-it-asset-management/page/product/software-asset-management2/task/create-integration-azure-ad.html Sometimes, the scheduled job "SAM - SSO Azure AD download applications" does not fetch the applications data into Servicenow.ReleaseParisCauseThe application logs indicate below exception stack trace when scheduled job is executed : SAMSSOAzureAdIntegration.setAppSoftwareModel = function(profileSysId, appExternalId)Cannot find function findOrCreateSMFromExternalId in object function () {...}.at [sn_sam_saas] 'SAMSSOAzureAdIntegration' [sys_script_include:0ffb22b477b200106e617fe89810613d]:244 (anonymous)at [sn_sam_saas] 'SAMSSOAzureAdIntegration' [sys_script_include:0ffb22b477b200106e617fe89810613d]:394 (anonymous)at [global] 'SAMSSOIntegrationUtils' [sys_script_include:29580ac777720010edfc0ff9ba10610e]:151 (runAndLogResult)at [sn_sam_saas] 'SAMSSOAzureAdIntegration' [sys_script_include:0ffb22b477b200106e617fe89810613d]:370 (downloadApplicationsForProfile)at [global] 'SSOBaseJob' [sys_script_include:8128801b74b30010fa9b81f90c151467]:13 (runJobForRecord)at [global] 'AssetManagementPerGlideRecordBaseJob' [sys_script_include:054adaa873c3330012a9e5e7caf6a79a]:53 (anonymous)at [global] 'AssetManagementBaseJob' [sys_script_include:54573868538313009961ddeeff7b1296]:123 (anonymous)at [sn_azure_ad_spoke] 'SAM - SSO Azure AD download applications' [sam_sso_sysauto_script:536297c81be2e4d8a268bbbc0a4bcbc7]:1 The exception is observe if the "Software Model" is not associated with the SSO application record. ResolutionThe software model record should be added to the SSO application record in order to fix this issue.