Troubleshooting ServiceNow Software Asset Management Microsoft 365 integration: Complete troubleshooting GUIDE for subscriptions or usage missingSummary :root { color-scheme: light; --blue:#005baa; --ink:#172033; --muted:#5b6678; --line:#d6dee8; --surface:#fff; --page:#f3f6fa; --red:#b42318; --amber:#9a6700; --green:#087443; } * { box-sizing:border-box; } html { scroll-behavior:smooth; } body { margin:0; padding:24px; background:var(--page); color:var(--ink); font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",sans-serif; line-height:1.55; } .kb-page { max-width:920px; margin:0 auto; } .kb-hero { background:var(--blue); color:#fff; padding:28px 32px; border-radius:10px; margin-bottom:24px; } .kb-eyebrow { margin:0 0 6px; font-size:11px; letter-spacing:1px; opacity:.78; text-transform:uppercase; } .kb-hero h1 { margin:0 0 7px; font-size:clamp(22px,4vw,30px); line-height:1.15; } .kb-lede { margin:0; font-size:14px; opacity:.9; } .kb-badges { display:flex; flex-wrap:wrap; gap:8px; margin-top:16px; } .kb-badge { padding:3px 11px; border-radius:12px; background:rgba(255,255,255,.18); font-size:12px; } .kb-toc,.kb-panel { background:var(--surface); border:1px solid var(--line); border-radius:8px; } .kb-toc { padding:18px 24px; margin-bottom:24px; } .kb-toc-title { margin:0 0 8px; color:#374151; font-size:13px; font-weight:700; letter-spacing:.5px; text-transform:uppercase; } .kb-toc ol { margin:0; padding-left:22px; line-height:2; } .kb-toc a { color:var(--blue); text-decoration:none; } .kb-section { margin-bottom:28px; scroll-margin-top:16px; } .kb-section-title { margin:0; padding:12px 20px; border-radius:8px 8px 0 0; background:var(--blue); color:#fff; font-size:16px; } .kb-panel { padding:20px 22px; border-top:0; border-radius:0 0 8px 8px; } .kb-panel p:first-child { margin-top:0; } .kb-panel p:last-child { margin-bottom:0; } .kb-callout { margin:0 0 18px; padding:13px 16px; border-left:5px solid var(--blue); border-radius:0 7px 7px 0; background:#eef5fc; } .kb-callout.critical { border-color:var(--red); background:#fff1f0; color:#7a271a; } .kb-callout.warning { border-color:var(--amber); background:#fff8e7; color:#6b4d00; } .kb-callout.success { border-color:var(--green); background:#ecfdf3; color:#05603a; } .kb-table-wrap { overflow-x:auto; margin:16px 0; } table { width:100%; border-collapse:collapse; font-size:13px; } th { padding:9px 12px; background:#31506d; color:#fff; text-align:left; } td { padding:9px 12px; border-bottom:1px solid #e5e7eb; vertical-align:top; } tr:nth-child(even) td { background:#f8fafc; } code { padding:1px 4px; border-radius:3px; background:#f1f3f5; font-family:ui-monospace,SFMono-Regular,Menlo,monospace; font-size:.92em; overflow-wrap:anywhere; } pre { overflow:auto; padding:14px; border-radius:6px; background:#111827; color:#f9fafb; } details { margin:0 0 12px; border:1px solid #bfdbfe; border-radius:6px; overflow:hidden; } summary { cursor:pointer; padding:12px 16px; background:#eff6ff; color:#1e3a5f; font-weight:700; } details > div { padding:16px; background:#fff; } .kb-footer { padding:16px 20px; color:var(--muted); font-size:12px; background:#f8fafc; border:1px solid var(--line); border-radius:8px; } @media (max-width:640px) { body { padding:12px; } .kb-hero { padding:22px 20px; } .kb-panel { padding:16px; } .kb-section-title { padding:11px 16px; } th,td { min-width:140px; } } .kb-hero { padding:24px 28px; } .kb-toc ol { display:grid;grid-template-columns:repeat(2,minmax(0,1fr));gap:2px 26px;line-height:1.7; } .kb-toc li { padding:3px 0; } h3 { color:#183653;line-height:1.3; } a { color:#005baa;overflow-wrap:anywhere; } th,td { overflow-wrap:anywhere; } pre code { padding:0;background:transparent;color:inherit;overflow-wrap:normal; } code.kb-err { color:#c62828;font-weight:700;background:#fdecea; } .kb-err-list { display:flex;flex-wrap:wrap;gap:6px;margin-top:8px;font-weight:400; } .kb-err-chip { display:inline-block;max-width:100%;padding:2px 8px;border-radius:4px;background:#fdecea;border:1px solid #f5c2c0;color:#c62828; font-family:ui-monospace,SFMono-Regular,Menlo,monospace;font-size:12px;font-weight:700;line-height:1.45;overflow-wrap:anywhere; } .kb-sum-title { font-weight:700; } .branch-index { margin:18px 0 20px;padding:14px 18px;background:#f8fafc;border:1px solid var(--line);border-radius:8px; } .branch-index ol { list-style:none;margin:0;padding:0;display:grid;grid-template-columns:repeat(2,minmax(0,1fr));gap:6px 28px; } .branch-index li { font-size:14px;line-height:1.45;padding:4px 0; } .kb-section-title + .kb-panel { margin-top:0; } details > div p { margin:0 0 14px; } details > div p:last-child { margin-bottom:0; } @media(max-width:640px) { .kb-toc ol,.branch-index ol { grid-template-columns:1fr; } .kb-hero {padding:20px;} } @media print { body {padding:0;background:#fff;} .kb-toc,.branch-index {display:none;} } .flow { margin:4px 0 26px;padding:18px;border-radius:12px;background:linear-gradient(135deg,#f8fafc,#eef2ff);border:1px solid var(--line); } .flow-intro { display:flex;flex-wrap:wrap;justify-content:space-between;gap:10px;font-size:13px;color:#475569;margin-bottom:14px; } .flow-legend { display:flex;flex-wrap:wrap;gap:6px; } .flow-key { padding:2px 9px;border-radius:10px;background:var(--b);color:var(--c);font-weight:700;font-size:11px;border:1px solid var(--c); } .flow-lane { margin-top:14px; } .flow-lane-head { display:flex;align-items:center;gap:10px;margin-bottom:8px;color:#0f172a; } .flow-lane-head span { font-size:11px;padding:2px 8px;border-radius:10px;background:#0f172a;color:#fff;text-transform:uppercase;letter-spacing:.05em; } .flow-track { display:grid;grid-template-columns:repeat(4,minmax(0,1fr));gap:16px 30px; } .flow-node { position:relative;display:flex;flex-direction:column;gap:3px;padding:12px 10px 10px 12px;border-radius:10px; background:var(--b);border:2px solid var(--c);color:#1e293b;text-decoration:none;box-shadow:0 1px 2px rgba(15,23,42,.06); transition:transform .2s ease,box-shadow .2s ease;animation:flowPulse 4.4s ease-in-out infinite;animation-delay:var(--d); } .flow-node::after { content:"";position:absolute;top:50%;right:-27px;width:22px;height:4px;margin-top:-2px;border-radius:2px; background:repeating-linear-gradient(90deg,var(--c) 0 6px,transparent 6px 10px);background-size:20px 4px;animation:flowDash .8s linear infinite;opacity:.7; } .flow-node:nth-child(4n)::after,.flow-node:last-child::after { display:none; } .flow-node:hover,.flow-node:focus { transform:translateY(-3px);box-shadow:0 8px 20px rgba(15,23,42,.18);outline:none;z-index:5; } .flow-node:focus-visible { outline:3px solid var(--c);outline-offset:2px; } .flow-num { position:absolute;top:-9px;left:-9px;width:22px;height:22px;border-radius:50%;background:var(--c);color:#fff;font-size:12px;font-weight:700; display:flex;align-items:center;justify-content:center;box-shadow:0 0 0 2px #fff; } .flow-title { font-weight:700;color:var(--c);font-size:13.5px;line-height:1.25; } .flow-what { font-size:12px;line-height:1.35;color:#334155;overflow-wrap:anywhere; } .flow-tip { position:absolute;left:50%;top:calc(100% + 8px);transform:translateX(-50%) translateY(-4px);width:210px;padding:10px 12px;border-radius:8px; background:#0f172a;color:#f8fafc;font-size:12px;line-height:1.4;opacity:0;pointer-events:none;transition:opacity .18s ease,transform .18s ease;z-index:10; } .flow-tip::before { content:"";position:absolute;top:-6px;left:50%;margin-left:-6px;border:6px solid transparent;border-top:0;border-bottom-color:#0f172a; } .flow-tip em { display:block;margin-top:6px;font-style:normal;color:#93c5fd;font-weight:700; } .flow-node:hover .flow-tip,.flow-node:focus .flow-tip { opacity:1;transform:translateX(-50%) translateY(0); } .tri { margin:14px 0 20px;padding:16px;border-radius:12px;background:#0f172a;color:#e2e8f0; } .tri-head { font-size:12px;text-transform:uppercase;letter-spacing:.08em;color:#93c5fd;font-weight:700;margin-bottom:12px; } .tri-row { display:grid;grid-template-columns:repeat(4,minmax(0,1fr));gap:12px 26px; } .tri-step { position:relative;display:flex;flex-direction:column;gap:4px;padding:12px;border-radius:10px;background:#1e293b;border:1px solid #334155; animation:triGlow 4.2s ease-in-out infinite;animation-delay:var(--d); } .tri-step::after { content:"";position:absolute;top:50%;right:-22px;width:16px;height:3px;background:repeating-linear-gradient(90deg,#60a5fa 0 5px,transparent 5px 8px); background-size:16px 3px;animation:flowDash .7s linear infinite; } .tri-step:last-child::after { display:none; } .tri-step strong { color:#f8fafc;font-size:14px; } .tri-where { font-size:12px;color:#93c5fd; } .tri-tells { font-size:12px;color:#cbd5e1;line-height:1.35; } .tri-num { position:absolute;top:-9px;left:-9px;width:22px;height:22px;border-radius:50%;background:#2563eb;color:#fff;font-size:12px;font-weight:700;display:flex;align-items:center;justify-content:center; } @keyframes triGlow { 0%,100% { border-color:#334155;box-shadow:none; } 10% { border-color:#60a5fa;box-shadow:0 0 0 3px rgba(96,165,250,.35); } 22% { border-color:#334155;box-shadow:none; } } .tri-row.tri-5 { grid-template-columns:repeat(5,minmax(0,1fr)); } @media (max-width:820px) { .tri-row,.tri-row.tri-5 { grid-template-columns:repeat(2,minmax(0,1fr)); } .tri-step:nth-child(2n)::after { display:none; } } @media (max-width:520px) { .tri-row { grid-template-columns:1fr; } .tri-step::after { display:none; } } @media (prefers-reduced-motion: reduce) { .tri-step,.tri-step::after { animation:none; } } @keyframes flowPulse { 0%,100% { box-shadow:0 1px 2px rgba(15,23,42,.06); } 8% { box-shadow:0 0 0 4px var(--b),0 0 0 6px var(--c),0 6px 18px rgba(15,23,42,.2); } 18% { box-shadow:0 1px 2px rgba(15,23,42,.06); } } @keyframes flowDash { to { background-position:20px 20px; } } @media (prefers-reduced-motion: reduce) { .flow-node,.flow-node::after { animation:none; } } @media (max-width:820px) { .flow-track { grid-template-columns:repeat(2,minmax(0,1fr)); } .flow-node:nth-child(4n)::after { display:block; } .flow-node:nth-child(2n)::after { display:none; } } @media (max-width:520px) { .flow-track { grid-template-columns:1fr;gap:24px; } .flow-node::after,.flow-node:nth-child(4n)::after,.flow-node:nth-child(2n)::after { display:block;top:auto;bottom:-22px;right:auto;left:50%;width:4px;height:18px;margin:0 0 0 -2px; background:repeating-linear-gradient(180deg,var(--c) 0 6px,transparent 6px 10px);background-size:4px 20px; } .flow-node:last-child::after { display:none; } .flow-tip { position:static;transform:none;width:auto;margin-top:6px;display:none;opacity:1; } .flow-node:focus .flow-tip,.flow-node:hover .flow-tip { display:block;transform:none; } } @media print { .flow-node,.flow-node::after { animation:none; } .flow-tip { display:none; } } Software Asset Management - Knowledge Article Troubleshooting ServiceNow SAM Microsoft 365 integration: subscriptions or usage missing Find the failing stage, correct its cause, and verify complete recovery. Contents Scope and applicabilityImplementation checklistSymptoms and expected behaviorExecution path and evidence correlationDetailed troubleshooting branchesCause-specific correction and controlled recoveryVerification criteria and recovery evidenceEscalation evidence to collectReferences, processing rules and known limitationsServiceNow Otto / Now Assist troubleshooting 1. Scope and applicability This article covers the direct Microsoft 365 profile type microsoft_office_365, its subscription import and its separate usage collection. It does not cover Microsoft Dynamics 365 and Power Apps: their observed type is microsoft_365_subscription. Microsoft Entra ID SSO, endpoint Discovery, ACC and Service Graph ingestion are separate paths. Applies to: SAM Professional with the Software Asset Management - SaaS License Management (sn_sam_saas_int) and SaaS License Management Foundation Store applications. Behavior described here can differ between application versions; compare your installed versions with the release documentation before applying a version-specific conclusion. 2. Implementation checklist Complete this checklist before changing authentication or retrying imports. Keep sensitive configuration inside the authorized administrative interface; record only nonsecret metadata in the investigation. CheckWhere and what to inspectReady condition / diagnostic decisionProduct and compatibilityInstalled SAM, SaaS License Management and SaaS Foundation application records; release-specific requirementsApplications required for the selected Microsoft 365 variant are active and mutually supported. A registered scope alone does not prove licensing rights or compatible dependencies. Validate compatibility before proposing activation or upgradeCorrect profile typeIntegration Profile, samp_sw_subscription_profile.profile_typemicrosoft_office_365, not microsoft_365_subscription. If wrong, use the supported configuration experience for the intended product; do not repurpose another product's profileServiceNow setup accessRelevant role definition and the administrator's permitted setup interfacesam_integrator is verified as granting SaaS-profile setup access. This does not automatically grant every diagnostic table, secret or job-execution permission. Use least-privilege access approved for each checkIntended source identityProfile and referenced authentication configuration; compare intended tenant, cloud and application metadataThe identity and organization match the source population being troubleshot. Never put tenant/customer identifiers, passwords, secrets, certificates or token contents into the KB or shared log bundleAuthentication modeAuthentication binding actually used by the referenced REST message and HTTP methodsSupported mode, valid nonsecret credential metadata, correct grant/audience and current consent for that mode. The selected profile/REST configuration must be traced; do not assume an alias or grant type is identical across integration generationsRead-operation permissionsVendor administrator reviews the operations in the checklists belowUsers, license details, tenant purchased quantities and required reports are accessible to the integration identity. Compare with Minimum Microsoft permissions by process belowOptional Power BISeparate Power BI request/authentication binding and source administrative accessDecide whether Power BI activity is required for the customer's coverage. Power BI validation failure can be an optional warning; it is not proof that all Graph activity is blockedREST-message referenceProfile rest_message → sys_rest_message → its sys_rest_message_fn methodsReference resolves to the intended generated configuration. Required method labels and usable methods/endpoints are present; see section 4. A profile existing in a list does not prove that reference resolvesConnection selectionFollow the REST method's actual authentication configuration; if it uses an alias, inspect that alias and its selected active connectionThe runtime connection, not merely a similarly named connection, belongs to the intended tenant and environment. Multiple connections, credential rotation or clones require a reference-by-reference comparisonNetwork and execution routeActual REST endpoint and configured route; MID selection only if this method uses itRequest reaches the intended approved host with trusted TLS and the correct proxy/MID route where applicable. A MID Server is involved only if the REST method is configured to use oneValidation stateProfile validation result and controlled configuration, compared with SampO365Admin.getProfileGrSubscription reader selects successful validation state. Usage also requires download_activity=1. Never edit internal validation JSON to make a profile appear eligibleSchedulesScheduled Script Execution, sysauto_script; exact jobs listed in section 4Correct jobs are active, at the intended approved cadence, and actually produce execution evidence. Do not create a second import job to compensate for unexplained missing resultsSource coverageVendor's intended user/SKU population, exclusions and separate Dynamics ownershipAccount for source assignments, user visibility, SKUs routed elsewhere and intentional exclusions. Source seats, users and imported subscription rows are not interchangeable countsPagination and batchesUsers requests and license-detail batch items from the same runAll user pages are visited and each relevant batch item is accounted for. Include a licensed user outside page one when the tenant exceeds the initial page sizeUser/model prerequisitesSubscription references, User Resolution Rules, content mapping and model recordsIntended identities resolve without collisions; SKU mapping is valid for the profile type. An imported row with blank user/model is a matching issue, not automatically a transport issueUsage reports and privacyRequired reports under the integration identity; attachment/parser inputs and reporting settingsNon-anonymized identities are available where approved and needed for matching; dates and columns match the installed parser. Do not change reporting privacy globally without governance approvalManual-report coverageSupported report export, filename and sync-date handling on the profileIf Visio, Project or Copilot manual reports are used, preserve the supported export format and verify the reader recognizes the intended file. Uploading any CSV does not make it eligibleCleanup and change controlExisting subscriptions, report attachments and overlapping executionsUnderstand that imports deactivate and can delete leftovers; usage can delete profile attachments. Preserve approved sanitized diagnostic evidence before reruns. Recovery is a controlled write operation, not a harmless connection testRecovery ownershipIntegration owner, vendor administrator and authorized ServiceNow administratorOwners approve the cause-specific configuration change and one controlled recovery run. No source permission expansion or production job execution is implied by this read-only investigation Permission and source-capability coverage checklist This is an operation checklist, not an OAuth scope matrix. Confirm current Microsoft roles, scopes, consent requirements and service-principal policies against the ServiceNow documentation for your release before remediation. CapabilityOperation used by the integrationEvidence to establish before enabling collectionUser populationUser enumeration with identity and assignment-plan fieldsIntegration identity can see every intended user, including later pagesAssigned licensesPer-user /licenseDetails inside batch requestsIntended user/SKU items return usable results; outer batch success is insufficientPurchased quantitiesConfigured default endpoint requesting consumedUnits, skuPartNumber, prepaidUnitsTenant and SKU match; enabled purchased units and consumed units are returnedGraph usage/activationReports requests and CSV processingRequired report operations succeed, identities are usable and reporting dates cover the investigationPower BI activitySeparate configured Power BI activity requestSource policy permits the selected identity to read the intended activity; optional-warning behavior is distinguished from Graph Reports failureManual product reportsSupported Visio, Project and Copilot exports recognized by the readerFilename, timestamp, headers and product mapping are recognized for the installed version Minimum Microsoft permissions by process Grant only what the processes you use require, with administrator consent on the app registration used by the profile. ProcessMicrosoft Graph application permissionsAdditional source-side requirementDownload subscriptions and purchased quantitiesUser.Read.All plus Organization.Read.All or LicenseAssignment.Read.All (follow your release's documentation)App registration exists in the same tenant entered on the profilePull user activity (Download activity)Reports.Read.AllReport user names are not concealed (see below)Power BI activity (optional)Power BI admin API access for the service principalPower BI tenant setting Allow service principals to use Power BI APIs is enabled for the app (directly or through an allowed security group)Reclaim subscriptions (automated license removal)User.Read.All, GroupMember.ReadWrite.All, LicenseAssignment.ReadWrite.AllMicrosoft Entra ID spoke is installed and configured What happens when a setting is missing or wrong Use this list to predict the symptom from a configuration gap, or to work backwards from a symptom to the setting most likely responsible. Setting, field or propertyIf it is missing or wrongTypical symptomProfile REST message (rest_message)Import cannot build its REST client; validation can still appear successfulBoth jobs complete in a few seconds with no subscriptions and no usage; or No REST message record found for the Microsoft 365 integration profile:Profile validation state (custom_properties contains "validate_connection":"success")Every Microsoft 365 job skips the profileJobs complete, no outbound calls, no data changeDownload activity (download_activity) uncheckedUsage job skips the profileNo usage rows; subscription last_activity is never refreshed; no low-usage candidatesReclaim subscriptions uncheckedRemoval candidates are still created but the license-removal subflow never runsCandidates stay open; licenses are not removed in Microsoft 365Tenant value contains anything other than the bare directory IDToken request goes to the wrong or a nonexistent directoryAADSTS700016 (application not found in directory) or authentication failure on validationClient secret expired or mistypedNo access token can be obtainedAADSTS7000222 (client secret keys expired), Authorization_RequestDenied, or User Not Authenticated. Could not retrieve a new access tokenConnection base URL not graph.microsoft.comValidation rejects the connection, or runtime calls return 404Connection URL is incorrect… or HTTP 404 on every Graph callNeither Organization.Read.All nor LicenseAssignment.Read.All grantedPurchased-quantity call failsPurchased/available subscription details empty or stale while user subscriptions importReports.Read.All not grantedReport downloads failUsage job fails; samp_sw_usage and samp_m365_apps_usage_report stay emptyMicrosoft 365 report setting Display concealed user, group, and site names in all reports enabledReports contain hashed identities that cannot match usersUsage rows exist but never match a subscription; last_activity stays blankPower BI service-principal tenant setting disabledPower BI activity call returns HTTP 401 with ServicePrincipalIsNotAllowedByTenantAdminSwitchOptional Power BI warning on validation; no Power BI usage; Power BI low-usage and downgrade candidates are skippedMicrosoft 365 reclamation rule last_activity_threshold not 30, 90 or 180The threshold is passed as the Microsoft report period, which only accepts those valuesUsage job fails during the Apps usage report with Response body was requested to be saved as attachment. It's not available through getBody() anymore.Subscription-identifier content not downloaded, or SKU unrecognizedSKU cannot map to a software modelSubscriptions with empty software_model; entries under the profile's Unrecognized Subscription Identifiers; installs unlicensed; no reclamation or downgrade candidatesNo matching sys_user for the user principal nameSubscription user stays emptyReconciliation consumes no right for the subscription; candidates skipped for that usersn_itam_samp.user_resolution_exclude_table empty while duplicate users exist in extended user tablesMatching can select the wrong sys_user recordSubscription attached to a non-person or duplicate accountSuite relationship (cmdb_m2m_suite_model) missingSuite children are not evaluated togetherNo overlapping candidates; last activity not aggregated from suite componentsEntitlement missing for an assigned SKUNothing to reconcile againstSKU shows as unlicensed; potential savings show 0csv not allowed in glide.attachment.extensionsMicrosoft reports cannot be saved as attachmentsUnable to save response body as attachment: csv is not an authorized file extension; usage emptyPermission type on the profile differs from the type granted in Entra ID (Application vs Delegated)Token lacks the expected permissionsInsufficient scopes provided or HTTP 403 although permissions appear grantedGovernment cloud tenant with commercial endpointsCalls go to the commercial cloudAuthentication or 404 failures; government endpoints (graph.microsoft.us, login.microsoftonline.us, api.powerbigov.us) are requiredSame client ID and secret reused on a second profileSecond profile cannot be savedOne app registration per profile is required by designUser-resolution rules that dot-walk reference fields, plus a long exclusion-table listEach subscription's user lookup becomes expensiveImport runs for many hours on large tenantsJob inactive after installationNothing runsNo Scheduled Job Results rows for the job 3. Symptoms and expected behavior SymptomFirst diagnostic branchHealthy evidence to seekNo job result, or job does not runAActual scheduled execution and its bounded job resultJob completed, but no data or no source requestsB, CEligible profile, resolved REST configuration and source requests for that profileAuthentication/authorization failureD, E, FCorrect source identity and successful operation-specific requestsSome licensed users or SKUs missingG, H, IComplete user pages, individual license results and accounted-for filtersUser or model blank/wrongJ, KExisting target row with correct identity/model resolutionPurchased quantities missing or inconsistentLCorrect tenant/SKU response and updated purchased-details rowUsage absent, stale or parsing failsM, NRequired report/event inputs, parser outputs and correct last-activity calculationDuplicates, unexpected deletion or stale recordsOExact-key behavior, complete source coverage and intended cleanup outcomeFailure after a clone or upgradePCurrent references, compatible applications and recovered execution chainNo reclamation candidates of any typeQCorrect rule scope, product mapping, thresholds and usage inputsDowngrade candidates not generatedRActive downgrade configuration with all conditions satisfied by real usage/storage dataOverlapping or consolidate candidates missing, or savings are zeroSSuite relationships, entitlements and a recent reconciliationAutomated license removal fails or stops part-wayTRemoval prerequisites, permissions and a throttling-aware retryVisio, Project or Copilot usage not updatingUA correctly named, unmodified report newer than the last sync A healthy import is not “every tenant user becomes one subscription.” The reader creates assignments for eligible user/SKU combinations after its filters. An unlicensed source user may have no subscription; one licensed user may have multiple SKUs. Healthy usage also does not mean every imported subscription has a recent activity date: the source must have a supported, identifiable activity signal for the mapped product. Treat a blank activity date as unknown until acquisition, report identity, parsing, mapping and calculation are verified. Do not classify users as inactive or approve reclamation solely from missing data. 4. Execution path and evidence correlation Hover or tap a step to see what breaks there; click it to open the matching branch.SetupConnectionCollectionMatchingWriteDownstream Subscription importweekly 1Scheduled importSAM - Import M365 User Subscriptions startsBreaks here: Job missing, inactive or plugin activation errorOpen branch A →2Eligible profileType microsoft_office_365, validated, REST message setBreaks here: Completes in seconds with no dataOpen branch B →3AuthenticateToken from Microsoft Entra ID with the right permissionsBreaks here: AADSTS errors, 401/403, insufficient scopesOpen branch D →4Users pagesGET /users, 500 per page, follows @odata.nextLinkBreaks here: Partial tenant, long runs, paging stopsOpen branch G →5License batches$batch of 20 users to /licenseDetailsBreaks here: Item 404/429 skips users; throttlingOpen branch H →6User and modelUPN to sys_user; SKU to software modelBreaks here: Empty user or model; unrecognized SKUOpen branch J →7Upsert and cleanupDeactivate, reactivate returned, delete leftoversBreaks here: Unexpected deletions or duplicatesOpen branch O →8Purchased detailsSubscribed SKUs: prepaid and consumed unitsBreaks here: Purchased or available counts wrongOpen branch L → Usage collectiondaily 1Usage jobSAM - Collect Microsoft 365 Usage startsBreaks here: Job missing or failing on a stepOpen branch A →2Download activityValidated profile with Download activity checkedBreaks here: Profile skipped, no usage at allOpen branch B →3Graph reportsActive user, Apps, storage and activation reportsBreaks here: Concealed names, period error, csv blockedOpen branch M →4Power BIPrevious UTC day of activity eventsBreaks here: Optional warning; service principal blockedOpen branch N →5Manual reportsVisio, Project, Copilot files on the profileBreaks here: Filename or date not recognizedOpen branch U →6Parse and matchRows with a valid UPN matched to usersBreaks here: Usage rows never match a subscriptionOpen branch J →7Last activityNewest activity across suite componentsBreaks here: Blank or stale last activityOpen branch M →8OptimizationReclamation, downgrade, overlap, removalBreaks here: No candidates, zero savings, removal failsOpen branch Q → Subscription path Scheduled import → eligible Microsoft 365 profiles → profile REST message → user pages → license batches → routing/exclusions → user and model matching → subscription upsert → leftover cleanup → purchased details → install-count calculation Usage path Separate usage job → eligible profile with Download activity → Graph/manual reports and Power BI activity → parsing and usage targets → product/user matching → last activity and activation fields → attachment cleanup The jobs are SAM - Import M365 User Subscriptions and SAM - Collect Microsoft 365 Usage. Out of the box they run weekly and daily respectively. Global wrappers write Software Asset Job Result, samp_job_log. Use sam_saas_job_log only when the actual execution is a SaaS framework job and its schedule_job reference identifies that job. Do not assume one framework concurrency rule applies to every legacy wrapper. StageRecord or source to inspectBehaviorEligibilitysamp_sw_subscription_profile; SampO365Admin.getProfileGr/getUsageProfileGrSelects microsoft_office_365 and successful validation text; usage additionally selects Download activityBindingProfile rest_message; sys_rest_message_fnClient looks up Default GET, GET Users, GET Reports, GET PowerBI Usage, POST Users By Batch by message name and exact method labelEnumerationSampO365RestClient.getUsersPrincipalNameByPagesInitial user page size 500; follows @odata.nextLinkLicense detailsBatch response responses[].id/status/body; client/admin batch methodsBuilds batches of twenty; each item status must be 200 to produce SKU data. Some outer errors return null and the admin skips that batchTarget identitysamp_sw_subscriptionLookup key is profile + Graph user ID in external_user_id + skuPartNumber in subscription_identifier; takes the first matching rowFilters and mappingIdentifier/user exclusion rules; SampSaasSubscriptionIdentifierUtils; User Resolution RulesDynamics-owned identifiers can be skipped; active scoped exclusions can suppress rows; matching and model resolution are separate stagesCleanupImport orchestration and profile subscriptionsExisting rows are deactivated, successful rows reactivated, inactive leftovers deleted. Catch reactivates surviving inactive rows; deleted rows are not restored by that operationPurchased detailssamp_purchased_subscription_detailsUpserts by profile/SKU using consumed units and enabled prepaid units; available quantity is floored at zero. Runs after subscription cleanupUsage targetssamp_sw_usage, samp_m365_apps_usage_report, subscription fieldsParses reports and combines supported product/user evidence; an Apps report can affect suite last activityEndpoint countsSampSubscriptionUtil; cmdb_sam_sw_installCounts existing endpoint-install evidence for resolved users/models. The SaaS import does not discover endpoint installations The generic endpoint normalization pipeline is not a prerequisite for every direct SaaS row. Subscription content mapping and downstream entitlement/reconciliation interpretation must be diagnosed separately. Purchased tenant quantities are not automatically proof of rights in ServiceNow entitlements or compliance. Correlate one execution before deciding a cause Record the exact job, one profile reference, start/end in UTC and the application versions. Use a narrow interval around that execution; expand it only if the execution actually exceeded it.Start with samp_job_log and inspect name, status, sys_created_on, sys_updated_on. Preserve the result reference privately. Its timestamp is a correlation anchor, not a guaranteed vendor request ID or per-profile success certificate.Match application/system messages from SampO365Admin, SampO365RestClient and the actual caller by profile, timestamp and available transaction context. If normal logging is insufficient, enable com.snc.samp.debug for one rerun only (see section 9) and turn it off afterwards.If available and authorized, inspect sys_outbound_http_log metadata: sys_created_on, hostname, method, response_status, transaction_id, source_table, app_scope. Link only records that genuinely share execution context. Host/time alone can collide during concurrent runs.Preserve sanitized request-path shape, outer status, vendor correlation reference and batch item IDs/statuses where available. Batch item IDs are local to that batch; correlate them to its request mapping, not another batch. Do not export raw authorization headers, request bodies or response payloads containing user data.Compare the intended source identity/SKU and the exact target key. Target sys_updated_on within the window supports a write, but alone does not prove every source item or the whole run succeeded. If outbound logging is absent, say “request evidence unavailable under the current logging, retention or access.” Do not conclude that no call occurred. Collecting new traces or executing a validation action requires approval and privacy controls. 5. Detailed troubleshooting branches Each branch lists the symptoms with the exact text the integration writes, where to look, each cause with its fix, and how to confirm recovery. Identifiers shown as <profile>, <app> or <tenant> are placeholders; keep the real values private. Start every investigation here 1Job resultScheduled Job Results (samp_job_log)Did the job run, and did it fail or complete? 2System logSystem Logs > All, filter SampO365Admin / SampO365RestClientThe real exception behind a failed or empty run 3Outbound HTTPSystem Logs > Outbound HTTP RequestsWhich Microsoft call failed, with status and headers 4Pick a branchMatch the status or error text below401 → D, 403 → E, 404 → C, 429 → I, no calls → B Start every investigation the same way. (1) Open Scheduled Job Results (samp_job_log) for the job and run. The message SamImportUserSubscriptionsO365: Failed to run job. Please look into logs for more details (or the SamCollectUsageO365 equivalent) is only a wrapper; the real exception is in the system log. (2) Open System Logs > All (syslog) for the same time window and filter Message contains SampO365Admin, SampO365RestClient or SAMP. (3) Open System Logs > Outbound HTTP Requests (sys_outbound_http_log) for the same window and read URL, response status and response headers. Any response other than HTTP 200 — including 202 and 204 — is treated as a failure, and the Microsoft error body becomes the error message. A. Import or usage job is missing, inactive or fails before processing any profileB. Job completes, but no subscriptions or usage are downloadedC. REST message, method or endpoint cannot be resolvedD. Authentication or token failureE. Authenticated, but access is denied or incompleteF. Data from the wrong tenant, or tenants mixed togetherG. Large tenants: users missing, very long runs or overlapping executionsH. Outer batch succeeds, but some users or licenses are missing — or disappearI. Throttling, Microsoft service errors or network failuresJ. Subscription user is empty or resolves to the wrong personK. Software model is empty or wrongL. Purchased or available quantities are missing, stale or look wrongM. Usage is stale, blank or the usage job failsN. Power BI activity missing, or the optional Power BI warning appearsO. Duplicates, unexpected deletions or stale subscriptionsP. Failures after a clone or upgradeQ. No reclamation candidates are generated for Microsoft 365R. Downgrade candidates are not generated (or unexpected ones are)S. Overlapping or consolidate candidates missing, or potential savings are zeroT. Automated license removal fails or stops part-wayU. Visio, Project or Copilot usage is not updating A. Import or usage job is missing, inactive or fails before processing any profilePlease activate the Software Asset Management - SaaS License Management from the store for Microsoft 365 integration to work...for Office 365 and Adobe integration to work Symptoms. No recent row in Scheduled Job Results for SAM - Import M365 User Subscriptions or SAM - Collect Microsoft 365 Usage.Job result Failed with Please activate the Software Asset Management - SaaS License Management from the store for Microsoft 365 integration to work (import) or ...for Office 365 and Adobe integration to work (usage and reclamation).New on Direct Integration Profiles does not offer the Microsoft 365 (Office 365) Integration Profile option. Where to check. System Definition > Scheduled Jobs (sysauto_script), name starts with SAM - ; System Applications > All Available Applications > Installed for Software Asset Management - SaaS License Management (sn_sam_saas_int) and the SAM Professional Microsoft plugin (com.snc.samp.microsoft). Causes and fixes. Job inactive. The job can be created inactive when the SAM Professional plugin is installed after the SaaS License Management app. Open the job, check Active, confirm the schedule (import weekly, usage daily by default) and save.SaaS License Management app not installed or not active. Install or activate it from the Store, then confirm both jobs exist.Activation error although the app is installed (typically right after an upgrade). Update SaaS License Management and SaaS License Management Foundation to the latest version available for your release. If the error persists, repair the application from the application manager and run each SaaS job once manually.Old combined job still active. SAM - Import User Subscriptions is the legacy combined job; current versions use separate Microsoft 365 and Adobe jobs. Keep only the per-vendor jobs active.Profile option missing from New. The wizard answer record Office 365 Integration Profile (sys_wizard_answer) is inactive. Open it, check Active, save and retry New. Verify. Execute the job once (Execute Now) and confirm a new Scheduled Job Results row with status Completed, followed by system log lines Start subscription pull for profile : <profile> and Finish subscription pull for profile : <profile>. B. Job completes, but no subscriptions or usage are downloaded Symptoms. Job result Completed within a few seconds; no Start subscription pull for profile line in the system log.No new outbound requests to graph.microsoft.com for the run window.Software Subscriptions related list on the profile is empty or unchanged. Where to check. The profile form and Show XML on it: profile_type, rest_message, download_activity and custom_properties. Causes and fixes. Profile not validated. The jobs select only profiles of type microsoft_office_365 whose custom_properties contains "validate_connection":"success". Changing the client secret or other connection details resets the profile to Draft and validation to false. Open the profile, run Validate Connection, fix any reported error (branches D and E) and repeat until it succeeds.REST message field empty (common after a clone or upgrade). The REST message record still exists in sys_rest_message, but the profile's REST message reference is empty or points to a deleted record. Validation can still report success because it skips the API calls when no REST message is found. Set the field back to the out-of-box Microsoft 365 REST message on the profile (or recreate the profile through setup), validate, then run both jobs. Do not edit the out-of-box REST message itself.Usage job only: Download activity unchecked. The usage job also requires download_activity = true. Check Download activity, validate again (this adds the Reports API check) and run the usage job.SKUs belong to another integration. Microsoft Dynamics 365 and Power Apps SKUs (for example FORMS_PRO, POWERAPPS_*) are intentionally skipped by this profile. Configure the Microsoft Dynamics 365 and Power Apps integration for them. Verify. One run shows Start subscription pull for profile, outbound calls to /users and /$batch, Users and subscriptions inserted, and new or updated rows on the profile's Software Subscriptions list. C. REST message, method or endpoint cannot be resolvedSampO365Admin No REST message record found for the Microsoft 365 integration profile: <profile>TypeError: Method and Endpoint must be definedConnection URL is incorrect. Delete the connection and recreate it to proceed further. Symptoms. SampO365Admin No REST message record found for the Microsoft 365 integration profile: <profile>.TypeError: Method and Endpoint must be defined — a required HTTP method is missing or renamed.HTTP 404 on every call, or validation message Connection URL is incorrect. Delete the connection and recreate it to proceed further. Where to check. Profile REST message > System Web Services > Outbound > REST Message > HTTP Methods; the Connection & Credential alias used by that REST message. Causes and fixes. Missing or renamed HTTP methods. The integration looks methods up by exact name: Default GET, GET Users, GET Reports, GET PowerBI Usage, POST Users By Batch. Restore the original names; do not rename or delete methods.Wrong endpoint. Expected endpoints are https://graph.microsoft.com/v1.0/users, https://graph.microsoft.com/v1.0/$batch (license details), the subscribed-SKUs endpoint for purchased quantities, and https://api.powerbi.com/v1.0/myorg/admin/activityevents. Common mistakes: /user/ instead of /users/, a missing /v1.0/, /me/, or graph.microsoftonline.com.Connection URL wrong. The connection base URL must contain graph.microsoft. Recreate the connection through the profile rather than editing the URL by hand.Tenant changed on an existing profile (older versions). The REST message endpoints may keep the previous tenant. Update the application, or create a new profile for the new tenant. Verify. System log shows UsersPrincipalName endpoint : <endpoint> with the expected URL, and the outbound log shows HTTP 200 for it. D. Authentication or token failureConnection validation failed. Verify the configurations you have provided and then retry.SampO365AdminUnhandled exception for profile : <profile> : com.glide.communications.ProcessingException: User Not Authenticated. Could not retrieve a new access token with the refresh token.AADSTS7000222: The provided client secret keys for app '<app>' are expiredAADSTS7000215: Invalid client secret providedAADSTS700016: Application with identifier '<app>' was not found in the directory '<tenant>' Symptoms. Validate Connection returns Connection validation failed. Verify the configurations you have provided and then retry., or the import logs SampO365AdminUnhandled exception for profile : <profile> : com.glide.communications.ProcessingException: User Not Authenticated. Could not retrieve a new access token with the refresh token. followed by a Microsoft error code. The outbound log shows HTTP 401 to login.microsoftonline.com. Where to check. The Microsoft error code in the system log; the app registration in Microsoft Entra ID (Certificates & secrets, API permissions, Overview for client and tenant IDs); System OAuth > Application Registry and Manage Tokens for the profile's OAuth entity. Causes and fixes. AADSTS7000222: The provided client secret keys for app '<app>' are expired. Create a new client secret in Microsoft Entra ID, paste the new secret Value into the profile, save, validate and run the import.AADSTS7000215: Invalid client secret provided. The secret ID was copied instead of the secret Value. Microsoft shows the Value only once; create a new secret and copy the Value column.AADSTS700016: Application with identifier '<app>' was not found in the directory '<tenant>'. The client ID belongs to another tenant, the Tenant field is wrong, or the app was never consented in this tenant. Enter the bare directory (tenant) ID with no extra text, confirm the client ID and grant admin consent.Token still failing after permissions or secret changed. A cached token was issued before the change. Delete the profile's tokens under System OAuth > Manage Tokens, then validate again so a fresh token is requested.Delegated vs application permission mismatch. The permission type granted in Entra ID (Application or Delegated) must match the permission type selected on the profile. Grant the same type and admin-consent it.US Government tenant. Endpoints must use the government cloud: graph.microsoft.us in the REST message methods, login.microsoftonline.us as the token URL in the Application Registry, .us OAuth scopes and api.powerbigov.us for Power BI. Microsoft 365 usage reports other than Power BI are not available in government clouds. Verify. Validate Connection succeeds; on the REST message, the Get OAuth Token related link reports OAuth token flow completed successfully; the next import shows HTTP 200 on /users. E. Authenticated, but access is denied or incompleteConnection validation failed. Insufficient scopes provided. Verify the configurations you have provided and then retry.Unhandled exception for profile : <profile> : Error: { "error": { "code": "Authorization_RequestDenied", "message": "Insufficient privileges to complete the operation." } } Symptoms. Connection validation failed. Insufficient scopes provided. Verify the configurations you have provided and then retry.Unhandled exception for profile : <profile> : Error: { "error": { "code": "Authorization_RequestDenied", "message": "Insufficient privileges to complete the operation." } }HTTP 403 in the outbound log; subscriptions import but purchased quantities or usage are missing. Where to check. Entra ID > App registrations > the app > API permissions (type and Status: Granted for <tenant>); the outbound request that returned 403 tells you which capability is denied. Causes and fixes. Permission missing for the failing call. /users and license details need User.Read.All; purchased quantities (subscribed SKUs) need Organization.Read.All or LicenseAssignment.Read.All; reports need Reports.Read.All. Add the missing permission as the correct type, then Grant admin consent.Permission added but consent not granted. The permission shows "Not granted". Grant admin consent, delete cached tokens (D4) and validate.Permission added as Delegated on an application (client credentials) setup. Application permissions are not selected by default in the Azure portal. Remove the delegated entry and add the Application permission.Power BI 403 while Graph works. Grant the Power BI service permission and complete branch N; update the application if Power BI validation fails with 403 despite correct permissions. Verify. Validation succeeds without the scopes message; the previously failing request (users, subscribed SKUs or reports) returns HTTP 200 in the next run. F. Data from the wrong tenant, or tenants mixed together Symptoms. Validation succeeds, but subscriptions belong to another organization; user principal names from one domain appear under another tenant's profile; models are shared across tenants. Where to check. The profile's Tenant and client ID; the token URL and REST message endpoints; the list of Microsoft 365 profiles. Causes and fixes. Profile points at the wrong tenant or app. Correct the Tenant and client ID; delete cached tokens; validate; run the import. Review rows already imported for the wrong tenant before deleting anything.Several tenants. Create one integration profile per tenant, each with its own app registration. Reusing the same client ID and secret on a second profile is blocked by design.Several tenants sharing the same software models. If compliance must be separated per tenant, create a software model per tenant (copy the out-of-box model with the same discovery map), add a subscription condition that matches that tenant's profile, create entitlements per tenant with the User Subscription metric, then run the import and reconciliation.Profile deleted and recreated. Existing subscriptions keep a reference to the deleted profile. Edit profiles in place; when a profile must be replaced, clean up subscriptions of the old profile through supported data maintenance. Verify. A known user from the intended tenant appears under the intended profile only; no new rows from another domain arrive in the next import. G. Large tenants: users missing, very long runs or overlapping executions Symptoms. Only part of the tenant is imported; the job runs for many hours; a second run starts while the first is still running; usage or reclamation runs overlap the import. Where to check. Outbound log: count of /users requests per run (500 users per page) and whether @odata.nextLink was followed; Scheduled Job Results start and end times; System Scheduler > Scheduled Jobs > Today's Scheduled Jobs (sys_trigger) for running instances. Causes and fixes. Run interrupted. A paging failure ends the import with SampO365AdminUnhandled exception for profile. Previously deactivated rows are reactivated, so nothing is lost, but the run did not finish. Fix the underlying error (D, E or I) and run again.Slow user resolution. Very long imports are most often caused by user-resolution rules that dot-walk reference fields, combined with a long sn_itam_samp.user_resolution_exclude_table list. Simplify the rules to direct field matches and keep the exclusion list to the tables you actually need.Overlapping runs. Current versions refuse to start an import or usage run while one is already running, and SaaS framework jobs log An instance of '<job>' is already running. Please wait till it completes. Do not start manual runs while the scheduled run is active; stagger import, usage and reclamation schedules.Very large tenants. Schedule the import outside business hours, keep the weekly cadence and allow the run to finish before reclamation starts. Verify. The outbound log shows every user page until no next link remains; the run ends with Finish subscription pull for profile; a known user from a late page has its subscriptions. H. Outer batch succeeds, but some users or licenses are missing — or disappearUnhandled exception while fetching license details: <error> Symptoms. Most users import, but specific licensed users have no subscriptions; subscriptions that existed last week are gone after an import that completed successfully; system log shows Unhandled exception while fetching license details: <error>. Where to check. Outbound log for POST /$batch: overall status and, in the response body, each item's status; the user in the Microsoft 365 admin center (licenses and sign-in state). Causes and fixes. Individual batch items failed. License details are requested in batches of 20 users. A batch item with any status other than 200 (for example 404 or 429) is skipped for that user. Fix the underlying cause (I for throttling, E for permissions) and rerun.Whole batch failed. If the entire batch call fails, those 20 users are skipped and the run continues.Why subscriptions disappear. Each import first marks all existing subscriptions inactive, reactivates those returned by Microsoft, then deletes the rest. A user skipped by a failed batch item therefore loses existing subscriptions even though the job completes. Treat unexpected deletions as an incomplete run, not as license removal, and rerun once the cause is fixed.User genuinely unlicensed or license removed in Microsoft 365. Confirm in the Microsoft 365 admin center before investigating further; removal on the next import is expected synchronization. Verify. All $batch items in the run return 200; the previously missing user has a subscription per assigned SKU; subscription counts are stable across two consecutive runs. I. Throttling, Microsoft service errors or network failuresConnection reset Symptoms. HTTP 429 in the outbound log; runs take much longer than usual; HTTP 5xx; Connection reset, socket timeout or TLS/proxy errors; Conditional Access blocks the sign-in. Where to check. Outbound log status and timing for the run; the Microsoft 365 service health dashboard; Entra ID sign-in logs for the app (Conditional Access result). Causes and fixes. Throttling (429). The client retries a 429 up to three times, waiting 60, 120 and 240 seconds, then fails. 429s inside individual batch items are not retried (see H). Stop manual reruns, schedule imports off-peak, and avoid other integrations using the same app registration at the same time.Microsoft service error (5xx). Not retried. Check Microsoft service health and rerun after the incident clears.Network or proxy failure. Connection resets and I/O errors are not retried. Confirm the instance can reach login.microsoftonline.com, graph.microsoft.com and api.powerbi.com; if the REST message uses a MID Server, check that MID Server's proxy and certificates.Conditional Access or IP restrictions. If the tenant restricts service principals by location, allow the ServiceNow instance's outbound IP ranges for this app registration. Verify. One complete run with no 429/5xx left unhandled, every user page and batch item successful, and a normal run duration. J. Subscription user is empty or resolves to the wrong person Symptoms. Subscriptions show a user principal name but an empty User; the wrong sys_user is linked; manually corrected users are overwritten by the next import; reclamation skips the subscription. Where to check. The subscription's User principal name; sys_user records whose Email or User ID match it; Software Asset Workspace > License operations > SaaS license management > User resolution rules; the property sn_itam_samp.user_resolution_exclude_table. Causes and fixes. No match. By default the UPN is matched to sys_user Email, or the part before @ to User ID. Align the user records, or create a user resolution rule (category SaaS, source field user_principal_name, the transform that fits your naming — for example prefix plus a fixed domain) and run the import.Wrong match from duplicate identities. When the same email exists in sys_user and an extended user table (for example csm_consumer_user or customer_contact), list those tables in sn_itam_samp.user_resolution_exclude_table (comma-separated). Active users are preferred over inactive ones.Manual edits overwritten. The User field is owned by the integration and is recalculated on each import. Correct the source data or a resolution rule instead of editing the field.Usage not matching although subscriptions resolve. Usage records use only rules that are not limited to a specific integration. Make the rule apply to all SaaS integrations if usage must use it.Rule error. Source field is missing in rule <rule> means the rule has no source field. Complete the rule.Non-person accounts (shared mailboxes, service accounts). Mark the discovered user's Non-person account instead of forcing a match. Effect of an empty user. The subscription consumes no right during reconciliation, the user's installs stay unlicensed, and low-usage, downgrade, overlapping and consolidate candidates are skipped. Verify. After the next import, the subscription's User is the intended person, and a known negative example (a similar but different user) is not matched. K. Software model is empty or wrongNo matching product definition is foundNo matching entitlement definition found Symptoms. Subscriptions show the raw SKU (for example SPE_E3) as display name with an empty Software model; entries in the profile's Unrecognized Subscription Identifier related list; system log No matching product definition is found or No matching entitlement definition found; install counts and activations not updated. Where to check. samp_sw_unrecognized_subscription_identifier; samp_sw_subscription_product_definition (external ID = SKU); the content download status of the subscription-identifier content. Causes and fixes. Subscription-identifier content not downloaded or out of date. Run the content download and confirm the SKU exists as a product definition, then rerun the import.SKU genuinely unknown to content (new Microsoft SKU). Open the SKU in Unrecognized Subscription Identifiers and set the correct software model; subscriptions with that SKU are updated. Request a content update for the SKU as well.Wrong model reused. A new subscription reuses the model already set on the most recent subscription with the same SKU and profile type, so one wrong mapping spreads. Correct the mapping at the unrecognized identifier, then rerun the import. If changing the mapping a second time does not update subscriptions, update the application.Duplicate models. Do not create models without a discovery map or entitlements without a publisher part number; the integration reuses existing models by part number, and extra models split compliance. Effect of an empty model. Activation counts are not updated, reclamation and downgrade candidates are not generated, and installs are not licensed. Verify. The subscription shows the intended model, publisher and product; the SKU no longer appears in Unrecognized Subscription Identifiers. L. Purchased or available quantities are missing, stale or look wrongSampO365RestClient Failed for <endpoint> with error: <error> Symptoms. The Microsoft 365 portal available subscription details view is empty; purchased counts do not change after a purchase; available shows 0 although assigned exceeds purchased; system log SampO365RestClient Failed for <endpoint> with error: <error>. Where to check. samp_purchased_subscription_details for the profile; the outbound subscribed-SKUs request; SAM - Collect Microsoft Purchased Subscription Details, if present in your version. Causes and fixes. Permission missing. Grant Organization.Read.All or LicenseAssignment.Read.All (as documented for your release), consent, validate.Import did not finish. Purchased details are collected after subscriptions; fix the import first.Quantity semantics. Purchased = enabled prepaid units; Assigned = consumed units; Available = purchased − assigned, never below 0. A SKU that is in suspended or warning state is not counted as enabled.Retired SKUs. Rows are updated but never deleted, so a SKU you no longer own keeps its last values. Leave them, or remove them through supported data maintenance after confirming the SKU is retired. Verify. The row for the SKU matches the Microsoft 365 admin center Licenses page for the same time. M. Usage is stale, blank or the usage job failsCaptureM365AppsUsageReport: Error: ...CaptureM365AppsUsageReport: ... Response body was requested to be saved as attachment. It's not available through getBody() anymore.Unable to save response body as attachment: csv is not an authorized file extension Symptoms. Last activity blank or old; samp_sw_usage or the Microsoft 365 Apps usage report table is empty; usage job failed with <StepName>: <error>, for example CaptureM365AppsUsageReport: Error: .... Where to check. The usage job's system log lines (User activity captured, M365 apps usage captured, OneDrive and MailBox Storage usage captured, User activity updated); outbound report requests; the profile's sync dates in Show XML (<report>SyncDate). Causes and fixes. Concealed names. If Display concealed user, group, and site names in all reports is enabled in the Microsoft 365 admin center, report rows contain hashed names; rows without @ are skipped. With privacy approval, clear it under Settings > Org settings > Services > Reports, then rerun the usage job after the next report refresh.CaptureM365AppsUsageReport: ... Response body was requested to be saved as attachment. It's not available through getBody() anymore. The Microsoft 365 reclamation rule's Last activity threshold is used as the report period, and Microsoft accepts only 7, 30, 90 or 180 days. Set it to 30, 90 or 180 through the rule form (not list edit) and rerun.Unable to save response body as attachment: csv is not an authorized file extension. Reports are saved as CSV attachments. Add csv to glide.attachment.extensions (keep the existing values) and, if MIME restrictions are used, allow text/csv; rerun.Reports.Read.All missing. Add it, consent, validate with Download activity checked.GlideDateTime constructor error, or invalid UPN in the response. Update the application; these inputs are handled in current versions.Several Microsoft 365 profiles (older versions). The Apps usage report table may keep data only for the last profile processed. Update the application.Expected latency. Microsoft reports lag by at least a day, so last activity normally trails by one or two days. Verify. All usage steps log success; samp_sw_usage has a recent last_used_time for a known active user, and that user's subscription last activity updates. N. Power BI activity missing, or the optional Power BI warning appearsAll required APIs have been validated successfully. However, the optional Power BI API validation failed.PowerBI api access is not authorized: <error>Error occured while collecting PowerBI usage. Check if api access is authorized correctly Symptoms. Validation shows All required APIs have been validated successfully. However, the optional Power BI API validation failed.; no Power BI usage; E5 → E3 and Power BI low-usage candidates are not created; system log PowerBI api access is not authorized: <error> or Error occured while collecting PowerBI usage. Check if api access is authorized correctly. Where to check. Profile Show XML: powerBIAPIStatus (success or failed); outbound request to /admin/activityevents and its X-PowerBI-Error-Info header; Power BI admin portal > Tenant settings > Developer settings. Causes and fixes. HTTP 401 with ServicePrincipalIsNotAllowedByTenantAdminSwitch. Enable Allow service principals to use Power BI APIs (and, where present, Allow service principals to use read-only admin APIs). If limited to a security group, add the app's service principal to that group. Allow up to 15 minutes, then validate.HTTP 404 with ResourceNotFound. Power BI or its admin API is not enabled for the tenant.403 with delegated permissions. Grant the Power BI permission; update the application if the delegated scope is still rejected.Classic workspaces. Only upgraded workspaces return activity to a service principal.Warning still visible after a successful Power BI validation. Cosmetic in some versions; trust powerBIAPIStatus. Behavior to expect. Power BI never fails the usage job; it only sets powerBIAPIStatus. Activity is read for the previous UTC day, so missed days are not backfilled. Sign-in activity is not part of this API. Verify. powerBIAPIStatus = success, and a known Power BI user has a recent Power BI usage row after the next daily run. O. Duplicates, unexpected deletions or stale subscriptions Symptoms. A user appears to have duplicate subscriptions; subscriptions disappear after an import; removed users still show; open reclamation candidates point to deleted subscriptions. Where to check. Compare rows by profile + Microsoft user ID (external_user_id) + SKU (subscription_identifier), not by name. Causes and fixes. Not a duplicate. One user with several SKUs has one row per SKU, and several profiles can legitimately hold the same person.Deleted after an incomplete run. See H3 and fix the cause before rerunning.Recreated Microsoft account. A deleted and recreated Microsoft user gets a new ID, so a new row is created and the old one is removed on the next import.Candidates left behind for removed subscriptions. Close or cancel candidates whose subscription no longer exists; update the application so this is handled automatically.Blocked users show 0 on the overview. Blocked status is refreshed only by the weekly import; run the import on demand. Verify. Two consecutive complete runs produce identical counts for the same source state. P. Failures after a clone or upgradeRESTMessageClient : Problem retrieving authentication profileGet for non-existent record: oauth_entity_profile:<id>TypeError: Cannot find function getUsageProfileGr Symptoms. Jobs complete with no data (B2); RESTMessageClient : Problem retrieving authentication profile with transaction-log warning Get for non-existent record: oauth_entity_profile:<id>; TypeError: Cannot find function getUsageProfileGr (or another missing function); the profile form behaves incorrectly after an update. Where to check. Profile REST message and OAuth references; installed versions of SAM Professional, SaaS License Management and SaaS License Management Foundation. Causes and fixes. Clone copied references to the source instance's OAuth profile. Individual REST methods may still test successfully because they do not use the profile link. Recreate the integration profile in the target instance (or re-point its authentication), re-enter the client secret, validate and run both jobs. Prefer a separate app registration per instance.Application versions out of step. Missing-function errors mean the SAM and SaaS applications do not match. Update all SAM Store applications to compatible versions.After any upgrade. Run each Microsoft 365 job once manually and check the results before the next scheduled cycle. Verify. Validation succeeds and both jobs complete with data in the target instance. Q. No reclamation candidates are generated for Microsoft 365 Symptoms. No low-usage candidates although users are inactive; the job SAM - Create New Reclamation Candidates for Office 365 Integration runs for very long or fails. Where to check. Software Asset Workspace > reclamation rules (samp_sw_reclamation_rule) for Microsoft 365 products; subscriptions' User, Software model and Last activity. Causes and fixes. Prerequisites missing on the subscription. User and software model must be set (J, K) and reconciliation must have run.Rule configuration. Each rule must have Applies to = Subscription Software, Create reclamation candidate checked, a Last activity threshold, a product row with an empty parent, and a subscription condition that matches. Out-of-box rules: Exchange Online, Microsoft 365, Microsoft 365 Copilot, OneDrive for Business, Power BI, Project Online, SharePoint Online, Teams, Visio Online and Office 365. Edit rules on the form, not in list edit.Blank activity. With Include no activity unchecked (default), subscriptions with no activity are not candidates. Fix usage (M, N) rather than enabling the option blindly.Too new. Subscriptions assigned more recently than the threshold are excluded.Already a candidate. Subscriptions in an open candidate are skipped.Duplicate rule for the same product. Delete the duplicate, close or cancel its candidates, and rerun.Products without usage data (for example Bookings, Forms, Planner, Power Apps, Power Automate, Stream, Sway, To Do). Suite candidates containing them are created with Notify user and are never removed automatically.Job runs for days or fails on suites. Update the application, and remove any circular parent/child relationship in cmdb_m2m_suite_model. Verify. A known inactive, fully resolved subscription produces exactly one candidate; a recently assigned one does not. R. Downgrade candidates are not generated (or unexpected ones are) Symptoms. No E5 → E3, E3 → F3, E3 → E1 or shared-mailbox candidates; or many false E3 → E1 candidates. Where to check. saas_downgrade_configuration and saas_downgrade_config_condition (both must be active); storage usage (saas_sw_storage_usage, License operations > User subscription > Software storage usage); powerBIAPIStatus. Causes and fixes. A condition is not met or its data is missing. E3 → F3 requires no desktop usage, OneDrive and mailbox under the configured size and a subscription older than 30 days. Missing usage or storage data counts as a failed condition unless Include no activity is set.E5 → E3 (no Power BI) missing. Requires powerBIAPIStatus = success and a Power BI rule older than its threshold (N).Shared-mailbox downgrade missing. The discovered user's Non-person account must be Shared Email Box.Additional discovery sources. With Include usage from additional discovery sources on the Microsoft 365 / Office 365 rule, desktop usage from other sources is considered and "no desktop usage" downgrades are generated only in the first week of the month.False E3 → E1 candidates. Desktop usage was not collected (Apps usage report empty, see M). Fix usage collection and update the application.Different path than expected. Downgrades are evaluated at the licensable model: with a Microsoft 365 E3 model and no Office 365 E3 entitlement, you get Microsoft 365 E3 → F3, not Office 365 E3 → E1. Verify. A known eligible user gets one candidate with the expected path; an ineligible user does not. S. Overlapping or consolidate candidates missing, or potential savings are zero Symptoms. A user with both Microsoft 365 E5 and Office 365 E5 has no overlapping candidate; consolidate candidates appear and vanish; potential savings show 0. Where to check. cmdb_m2m_suite_model for the suite relationships; entitlements and license metric results for the models; last reconciliation date. Causes and fixes. Suite relationship missing. Overlap uses the parent/child suite definition. Add the missing relationship.No entitlement or no reconciliation. Savings need entitlements for the models and a reconciliation run after they were created. Consolidate candidates with no positive saving are removed automatically. Recommended setup: Microsoft metric group with the User Subscription metric.Only the Microsoft 365 rule drives overlap and consolidate. Make sure it is active with Create reclamation candidate checked.Savings scope. Savings at the license metric result level are calculated only for low-usage and overlapping candidates. Verify. After reconciliation and the candidate job, the known overlapping user has one candidate with a positive saving. T. Automated license removal fails or stops part-way<product> - Error due to concurrent requests being made to the tenant. Please wait briefly and retry.. Symptoms. Candidate shows Closed but the license is still assigned; <product> - Error due to concurrent requests being made to the tenant. Please wait briefly and retry.. after Reclaim All; errors for licenses assigned through groups. Where to check. Profile Reclaim subscriptions; Microsoft Entra ID spoke and its connection; Flow Designer executions of the reclaim subflow; app permissions. Causes and fixes. Prerequisites. Reclaim subscriptions checked on the profile; Microsoft Entra ID spoke installed (Integration Hub) and connected; User.Read.All, GroupMember.ReadWrite.All and LicenseAssignment.ReadWrite.All granted with admin consent.Throttling. Wait, then use Resume Reclaim instead of restarting.Group-assigned licenses. Microsoft does not allow removing a group-assigned license from one user. Remove the user from the licensing group in Entra ID, or handle those users outside automated removal.Closed but not removed. Subflow errors are not always written back to the candidate. Check the subflow execution in Flow Designer, and confirm the reclaim subflow is mapped to the profile. Update the Entra ID spoke if its group action fails.Eligible types. Only low-usage and overlapping candidates are removed automatically; suite candidates with Notify user need approval. Verify. The license is gone in the Microsoft 365 admin center, and the next import no longer returns that user/SKU. U. Visio, Project or Copilot usage is not updating Symptoms. Last activity for Visio, Project Online or Microsoft 365 Copilot never updates; no candidates for these products. Where to check. Attachments on the profile before the usage run; profile Show XML VisioSyncDate, ProjectSyncDate, CopilotSyncDate. Causes and fixes. No file uploaded. Microsoft provides no API for these products. Download the activity user detail report from the Microsoft 365 admin center (Reports > Usage) and attach it to the integration profile.File name not recognized. The name must start with Visio, Project or Copilot and keep Microsoft's original date-time stamp (for example ProjectActivityUserDetail<month>_<day>_<year><time>.csv). Do not rename or re-save the file; if Microsoft's export name starts with another prefix (for example FastCopilot...), rename it to start with CopilotActivityUserDetail and keep the rest.File older than the last sync. Only the newest file per product is processed, and a file older than that product's sync date is skipped. Upload a newer export.Dates in day/month format. Export with ISO (yyyy-MM-dd) dates where possible; ambiguous day/month dates can be read incorrectly.CSV attachments blocked. See M3.Stale data blocks candidates. Candidates for these products need a sync date within the last 7 days, so upload weekly. Behavior to expect. The usage job deletes all attachments on the profile at the end of every run. Keep your own copy. Verify. The product's sync date moves forward and a known user's last activity matches the report. 6. Cause-specific correction and controlled recovery Do not use credential rotation, global properties or repeated imports as universal fixes. The checks above are read-only; configuration correction, validation, import, usage, restoration and reconciliation are write operations that require approval. Established causeCorrection owner and prerequisiteControlled recovery and stop conditionWrong profile/reference or missing generated REST configurationSAM integration owner; supported variant and configuration-generation procedure establishedRestore intended bindings, approve validation and one import. Stop if the same missing reference remains; collect configuration evidenceAuthentication or operation-specific access failureVendor administrator and integration owner; current exact mode/permission requirements validatedCorrect only the failing grant/credential/policy. Verify the failing operation before assessing complete importIncomplete paging, skipped batch or throttlingSource/integration owner; page/item evidence and supported recovery identifiedResolve source pressure/failure; allow one complete approved run. Stop repeated reruns if omissions remain or cleanup affects rows unexpectedlyIntended/unintended exclusionSAM data owner; exact active scoped rule and expected coverage reviewedCorrect the specific rule through supported management; verify both a previously missing assignment and an assignment that should remain excludedIdentity or model-resolution issueIdentity/content/model owners; exact target row exists and supported mapping procedure establishedCorrect narrowly, then run supported resolution/remapping with approval; verify user/model and negative controlsReport identity/schema/coverage issueReporting/privacy owner and SAM integration owner; approved supported report confirmedPreserve evidence, correct the proven input/policy, approve one usage run; verify every stage rather than the final job statusCleanup-related loss or duplicatesSAM data owner and support; before/after evidence and complete source population establishedUse supported repair/restoration. Do not claim import rollback; separately verify current assignments and historical/manual metadataPost-clone/upgrade mismatchPlatform/application owners; environment and compatibility requirements confirmedRestore environment-specific bindings and supported application state; prove complete import and independent usageReclamation, downgrade or overlap configuration gapSAM process owner; rule, condition, suite and entitlement setup reviewedCorrect the specific rule or relationship, run reconciliation where savings are involved, and verify one positive and one negative exampleLicense removal failure or throttlingMicrosoft administrator and SAM process owner; write permissions and spoke confirmedWait out throttling, use Resume Reclaim, verify removal in Microsoft 365 and in the next import Before recovery, record expected source assignments and targeted outcome, preserve permitted evidence, confirm no overlapping execution, and document the authorized change/run. If the correction requires custom code, undocumented source operations or unavailable rollback, escalate rather than improvise. 7. Verification criteria and recovery evidence Close the ingestion incident only when the relevant criteria below are met. Where a feature is intentionally unused, mark it out of scope with the customer's approval; do not quietly treat it as tested. Verification layerEvidence requiredWhat does not satisfy itConfigurationCorrect profile type, application context, resolved REST/authentication binding and eligible supported stateA profile row or green test aloneExecutionActual intended job/profile execution in a recorded UTC windowOnly an active schedule or global completed resultSource coverageIntended tenant/identity, all user continuations and accounted-for batch items; filters explainedFirst-page success or outer HTTP 200AssignmentsPreviously missing known key exists with intended current fields; later-page sample where relevant; no unexplained omissionsEqual user/subscription totals without accounting for multi-SKU assignmentsMatchingIntended user and model references, valid same-type content mapping and explained model-derived edition/versionPopulated but wrong referencesPurchased quantitiesCorrect profile/SKU source quantities and updated details; discrepancies explainedAssuming details equal entitlement rights or complianceUsageRequired reports/events acquired and parsed, supported identities/dates mapped, last activity correctly derivedRecent job timestamp, attachment download or blank date interpreted as inactivityCleanup and stabilityExpected leftovers removed only after complete coverage; no unexplained duplicate/deleted rows; next approved scheduled execution remains healthyCatch reactivation interpreted as rollbackReporting handoffUnderlying target rows and approved reporting scope agreeA workspace tile alone or forced dashboard refresh The same test execution should demonstrate the corrected failure, downstream target effect and absence of adjacent-stage failure. If live vendor evidence is unavailable, record “static/configuration validation only” and keep runtime recovery open. 8. Escalation evidence to collect Collect the smallest approved bundle that allows support to follow one failure. Use a secure support channel; anonymize user/tenant data consistently and never paste secrets or private keys into article feedback. Platform build and exact SAM/SaaS/Foundation versions; selected variant and recent clone/upgrade/change timeline. Include relevant compatibility/access gaps.Intended job name, private result reference, profile reference and UTC start/end; wrapper status and actual per-profile evidence. Preserve same-run correlation rather than unrelated log excerpts.Nonsecret reference chain: profile → REST message → exact method → runtime authentication/connection metadata. State whether an alias is actually used and whether multiple definitions/connections exist.Sanitized request-path shape, source operation, outer status, provider error code and authorized correlation reference. Remove tokens, authorization headers, cookies, secrets, signed URLs and raw user payloads.Page sequence/counts and continuation presence without secret/query values; batch request/item mapping, each relevant item outcome and a sanitized missing-assignment example.Target key comparison, active/user/model presence, update timing and relevant exclusion/mapping/resolution-rule metadata. Keep source identity values inside the secure case where genuinely necessary.For usage: sanitized header structure, report refresh/usage dates, supported export/filename pattern, failed stage name, parser outcome and target dates. Do not send full reports with unrelated users.Before/after coverage and cleanup evidence, overlap/concurrency timeline, proposed correction, approved recovery actions and their observed result.Explicit gaps: unavailable logs, ACL denial, protected code, unvalidated vendor permissions, missing configured profile or untested multi-page execution. Label inference separately from observation. Do not include internal notes, unpublished defect claims, unrelated customer records or copied support-case narratives. If detailed HTTP evidence was never retained, explain the limitation; obtain approval for any new collection rather than retrospectively asserting a request outcome. 9. References, processing rules and known limitations Key records Jobs: SAM - Import M365 User Subscriptions, SAM - Collect Microsoft 365 Usage, and where present SAM - Collect Microsoft Purchased Subscription Details and SAM - Microsoft 365 Daily Job (feeds the Optimization and Savings widgets).Job results: samp_job_log; SaaS framework jobs also write sam_saas_job_log. Errors: system log, filtered on SampO365Admin, SampO365RestClient or SamCollectUsageO365 for the run window. Calls: sys_outbound_http_log.Configuration: samp_sw_subscription_profile, sys_rest_message / sys_rest_message_fn, the referenced connection and credential.Data: samp_sw_subscription, samp_purchased_subscription_details, samp_sw_usage, samp_m365_apps_usage_report, saas_sw_storage_usage, samp_discovered_user.Mapping: samp_sw_subscription_product_definition, samp_sw_entitlement_definition, samp_sw_unrecognized_subscription_identifier, samp_user_resolution_rule, cmdb_m2m_suite_model.Optimization: samp_sw_reclamation_rule, samp_m2m_rule_product, saas_downgrade_configuration, saas_downgrade_config_condition.Script includes: SamImportUserSubscriptionsO365, SamCollectUsageO365, SampO365Admin, SampO365RestClient, SampSubscriptionUtil, SAMSaasIntegrationUtils, SAMSaasCommonUtils. System properties com.snc.samp.debug — set to true temporarily to write detailed SAM logging (system log sources sn_sam_saas_int and script) for one rerun. It has a performance cost; set it back to false immediately after the run.sn_itam_samp.user_resolution_exclude_table — comma-separated list of sys_user extended tables to exclude from user matching. Empty means no exclusion. Change it only when duplicate users across extended tables are proven to cause wrong matches. Processing rules to remember Only profiles of type microsoft_office_365 with successful validation are processed; the usage job also needs Download activity.Each user/SKU pair is one subscription keyed by profile, Graph user ID and SKU part number. A user with several SKUs has several rows; that is not duplication.Each import deactivates existing rows, reactivates returned ones and deletes leftovers, so a partial run can remove rows. It is not a transactional rollback.The usage job deletes all attachments on the profile at the end of every run.Only an outer HTTP 429 is retried (up to three attempts with 60/120/240-second waits). Other non-200 responses fail the operation.Power BI activity is read for the previous UTC day only; missed days are not backfilled automatically. Known limitations Reports with concealed user names cannot be matched to users.Some Microsoft 365 products (for example Bookings, Forms, Planner, Power Apps, Power Automate, Stream, Sway, To Do) have no usage source, so they cannot drive automatic reclamation.The Power BI activity API does not provide sign-in activity, and classic Power BI workspaces do not return data to a service principal.Purchased tenant quantities are not entitlements. Compliance still needs entitlements for each assigned SKU and a reconciliation run.Blank activity is unknown, not inactive. Do not approve reclamation from missing data. Documentation ServiceNow: Microsoft 365 integration — prerequisites, supported authentication and permissions for your release.Microsoft: Power BI Activity Events API — authorization and response contract for Power BI activity.ServiceNow: Configure Now Assist for SAMServiceNow: SaaS troubleshooting with Now Assist for SAM 10. ServiceNow Otto / Now Assist troubleshooting ServiceNow Otto for Software Asset Management (formerly Now Assist for SAM, application sn_now_assist_sam) adds generative AI help for SaaS integrations. Use it to explain a failed Microsoft 365 job or a failed connection validation, and to propose user resolution rules when imported subscriptions do not match users. Treat its output as a starting point: confirm every recommendation against the branch in section 5 before changing configuration. How Troubleshoot works 1Failure bannerProfile in Software Asset WorkspaceFailed job or failed Validate Connection 2TroubleshootButton on the error bannerDebug-level validation, ~15–20 s 3Read guidanceError Summary + Suggested ResolutionsMap each item to a section 5 branch 4Fix and validateApply the fix yourselfValidate Connection again; rerun Troubleshoot if needed 5Publish or runPublish new / run existing jobConfirm with section 7 What the AI skills do SkillWhat it doesWhen it runsDefault model providerError log summarizationReads the logs of the failed job or validation and produces an Error SummaryWhen you click TroubleshootAWS Claude (from Australia Patch 4)Error resolution recommendationTurns the summarized errors into Suggested Resolutions, one per errorChained after the summaryAWS Claude (from Australia Patch 4)SaaS user resolutionProposes user resolution rules that map the Microsoft user principal name to sys_userAutomatically after a subscription download, when prerequisites are metAzure OpenAI The model provider can be changed per skill in the Now Assist Admin console; Now LLM Service can still be selected manually. Before you start Installed and licensed. Otto for SAM (sn_now_assist_sam) is installed and your subscription includes generative AI for SAM. Confirm entitlement with your account team. The capability is not available, or is limited, in in-country, FedRAMP, NSC DOD IL5, IRAP-Protected, self-hosted, regulated-market and other restricted environments.Skills active and displayed. Go to All > Now Assist Admin > Skills, choose the SAM workflow group, open each skill and confirm it is active with Display turned on. To activate: Activate skill > Save and continue > Select display (turn on Display, add roles if needed) > Review and activate > Activate. Skills are active by default from Zurich Patch 4, but a skill you deactivate stays off until reactivated.Roles. sam_integrator to use Troubleshoot and SaaS user resolution; skills are available to sam_user and sam_admin by default. If an administrator changed the skill roles, the custom roles apply instead. Activating or configuring skills needs the Now Assist administrator role.Software Asset Workspace. Troubleshoot appears in the workspace profile form, not in the classic form.Privacy. Inputs and outputs are processed in ServiceNow's generative AI environment and may be processed by the selected third-party model provider. Review your organization's AI data-handling settings and the Now Assist opt-out options before use. Use Troubleshoot on a failed job or validation Go to Workspaces > Software Asset Workspace > License operations > User subscription > Direct integration profiles and open the Microsoft 365 profile.Existing profile, failed scheduled job: the profile shows an error banner for the failed job. New profile or changed connection: click Validate Connection; a failure shows an error banner.Click Troubleshoot on the banner. Otto runs the validation with debug-level logging, summarizes the errors and proposes resolutions. Expect a response in around 15–20 seconds.Read the Error Summary and Suggested Resolutions on the profile. Map each resolution to the matching branch in section 5 and follow that branch's fix and verify steps.Apply the fix yourself (Troubleshoot never changes connection or integration configuration), then click Validate Connection again. Click Troubleshoot again to regenerate guidance if validation still fails.When validation succeeds, Publish a new profile, or run the job once for an existing profile and confirm the result with section 7. What Troubleshoot writes. The error summary and suggested resolutions are stored on the integration profile, and each run is kept in a troubleshooting log shown as a related tab on the profile. It does not modify subscriptions, credentials or jobs. The AI indicator may not appear on these fields when the system rather than the AI last updated them. What it covers. Runtime failures of the integration's scheduled jobs and connection-validation failures for SaaS and SSO integration profiles. It does not diagnose data-quality questions such as missing users in a product scope, model mapping or reconciliation results; use section 5 for those. AI-generated user resolution rules After each subscription download, SAM checks whether a rule should be generated. The SAM - Generate user resolution rule job calls the SaaS user resolution skill only when at least 10% of subscriptions have no user, and either it is the first run, or the previous run created no rule and the data has changed (a new field or about 10% more user data). Review results: Software Asset Workspace > License operations > SaaS license management > User resolution rules. Rules created by the skill show Source = AI. Steps are listed in the AI activity log in the Activity center on the Software asset overview.Activate deliberately: a generated rule that is inactive shows Review needed. Check it against a few known users, then set it Active and save. Rerun the Microsoft 365 import to apply it.Each run is logged in samp_user_resolution_rule_log with the outcome. When the assistant does not help What you seeLikely causeWhat to doNo Troubleshoot buttonApplication not installed, skill inactive or Display off, missing role, classic form instead of the workspace, or no current failureCheck the prerequisites above; the button appears only on the error banner of a failed job or validationTroubleshoot runs but returns nothing or an errorSkill call or output formatting failedOpen the generative AI log (sys_generative_ai_log.list) for the skill request: error code, message and whether the response was formatted correctly. Check System Logs > Errors for formatting failuresSummary is short, generic or cut offOlder application version with a smaller output limit, or too little log detailUpdate Otto for SAM to the latest version; rerun Troubleshoot after reproducing the failure so fresh logs existRecommendation contradicts the logsAI output is a suggestion, not a verified diagnosisFollow the outbound HTTP status and the matching section 5 branch; report the mismatch with the generative AI log entryProfile reference fields show invalid field name: troubleshooting_logTroubleshooting component not active on an older SaaS License Management versionUpdate SaaS License ManagementUser resolution job ends with "did not meet the pre-requisites" or "no change in your user data"Expected: fewer than 10% unresolved, or nothing changed since the last runNo action; create a rule manually if needed (branch J)User resolution job ends with "failed due to some error in the Gen AI skill"Skill call or output failedCheck sys_generative_ai_log for the skill runNo rule created: "no user table field could uniquely be identified"the Microsoft user principal name has no unique exact match in any sys_user fieldCorrect user data or create the rule manually (branch J) Limitations Output is AI-generated and can be inaccurate or incomplete; a person must review it before acting.Only job and validation failures are analyzed; ingestion completeness, mapping, usage and optimization still need section 5.Responses take several seconds because each Troubleshoot click chains more than one model call.Availability depends on your AI entitlement and hosting environment.