---
sourceDocument: Australia Asset Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-asset-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Asset Management

ft:clusterId :

    - itam

bundleId :

    - itam

workflow :

    - Technology


---

# Viewing SSO subscription information

# Viewing SSO subscription information {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Viewing SSO Subscription Information

This guide outlines how to view Single Sign-On (SSO) applications, users, and groups associated with your SSO integrations within ServiceNow's Software Asset Management (SAM).
You can access this information through both the classic UI and the Software Asset Workspace.
Show full answer Show less  

## Key Features

* **SSO Integration Profiles:** Navigate to *All \> SaaS License \> Administration \> SSO Integration Profiles* to find related lists that include all SSO applications, users, and groups.
* **Scheduled Jobs:** Information on scheduled jobs that automate the downloading of applications, users, and group memberships, running daily or upon profile publication.
* **Application Information:** Access detailed views of users, groups, and subscriptions for specific SSO applications via *All \> SaaS License \> SSO Applications*.
* **Reclamation Candidates:** Identify subscriptions that do not meet usage requirements for potential reclamation.

## Key Outcomes

By utilizing these features, customers can efficiently manage their SSO integrations, ensuring accurate tracking of user access and subscriptions. Scheduled jobs facilitate data synchronization with SSO providers like Azure AD and Okta, ensuring that any changes in user status are reflected in ServiceNow. Proper management of SSO subscriptions allows for effective license reclamation and optimization of software usage.  
You can view information about the Single Sign-On (SSO) applications, SSO users, and SSO groups that are associated with your SSO integrations.
Important:  
You can view information about your SSO applications, users, and groups in both the Software Asset Management Core UI and Software Asset Workspace. The following sections provide details on viewing this information in the Software Asset Management classic application. For details on viewing this information in the Software Asset Workspace, see [License operations view](https://www.servicenow.com/docs/f97mKB9sVuReYp71DCuFZA "Use the License operations view in Software Asset Workspace to manage software asset operations.").

## Viewing SSO integration information {#sso-subscriptions__section_tgh_kwj_wlb}

To view the applications, users, and groups for an SSO integration, navigate to AllSaaS LicenseAdministrationSSO Integration Profiles and then select a profile. The related lists provide information about the integration.{#sso-subscriptions__table_ut4_dyj_wlb__entry__2}

| List | Description |
|-|-|
| SSO Applications | All SSO applications. |
| Directory Users | All SSO users. |
| Directory Groups | All SSO groups. |
| Scheduled Jobs | SAM - SSO \<sso-provider\> download applications scheduled job that downloads all SSO apps. The job runs when the SSO integration profile is published, and then runs daily. The SAM - SSO \<sso-provider\> update connected applications scheduled job downloads users, groups, and subscriptions for SSO apps. The job runs daily and whenever an app is connected. |
| Scheduled Job Results | Status of the scheduled jobs. |
| Directory Jobs | The \<sso-provider\> - Download Group Membership directory job that downloads group memberships for all users. The job runs when the SSO integration profile is published, and then runs daily. The \<sso-provider\> - Download Users directory job downloads all users. The job runs when the SSO integration profile is published, and then runs daily. The \<sso-provider\> - Download Groups directory job downloads all groups for all users. The job runs when the SSO integration profile is published, and then runs daily. Note: On upgrading to Microsoft Entra ID spoke 4.3 version, the Microsoft Azure AD - Download Group Membership directory job won't be executed for existing Microsoft Entra ID SSO or Directory integrations. This directory job also won't be created for new Microsoft Entra ID SSO or Directory integrations. Instead, the Microsoft Azure AD - Download Groups directory job downloads all groups and group memberships configured on Microsoft Entra ID. |
| Directory Job Results | Status of the directory jobs. |
[Table 1. SSO Integration Profile related lists]

{#sso-subscriptions__table_ut4_dyj_wlb}

## Viewing SSO application information {#sso-subscriptions__section_oqn_kwj_wlb}

To view the users, groups, and reclamation candidates for an application, navigate to AllSaaS LicenseSSO Applications and select an application. The related lists show information for the application. For viewing the SSO application information in Software Asset Workspace, see [View SSO applications in workspace](https://www.servicenow.com/docs/n7EetTmyWQEPWEkKgzD45A "View details related to applications that you can connect through a SSO provider in the Software Asset Workspace.").
{#sso-subscriptions__id_acl_q5h_bzb__entry__2}

| List | Description |
|-|-|
| SSO Application Users | All users that have direct access to the application, but not through membership in a group. |
| SSO Application Groups | All groups that have access to the application. |
| SSO Subscriptions | Total number of subscriptions for the application. A user may have both direct access to an app and have access through a group. But the user's access counts as only one subscription so as only one record in the SSO Subscriptions list. Note: * Add the SSO application role column to see how the user is granted access to the application. If the value is a group, then the user has access through membership in that group. If the value is the user's name, then the user has direct access to the application. User subscriptions can't be reclaimed in Software Asset Management if the user has access to the application through a group membership. To reclaim the subscription, remove the user from the group in the Azure AD portal and set the reclamation candidate state to Closed Complete. * When SSO subscriptions are created through SSO application groups, the Subscription assigned value is empty. When the subscriptions are created through SSO Application Users, the Subscription assigned value shows the date of when the subscription is assigned to the user. After you upgrade to the Software Asset Management - SaaS License Management 13.1.0 version or later, the existing Subscription assigned values for the subscriptions that were created through SSO application groups turns empty. {#sso-subscriptions__ul_zds_yt1_bzb} |
| Reclamation Candidates | Subscriptions that don't meet the usage requirements that are defined by the reclamation rule for the application. |
| SSO Group Software Model Mappings | SSO groups that are mapped to specific software models for managing licenses at the group level. |
[Table 2. SSO Applications related list]

{#sso-subscriptions__id_acl_q5h_bzb}

## Data synchronization with SSO providers {#sso-subscriptions__section_kv1_y4r_wlb}

If you delete a user, group, or app in the Azure AD portal or in the Okta Developer Console, then the corresponding records in Software Asset Management are deleted when the daily scheduled jobs run. If you revoke a user's access to an application in the Azure AD portal or in the Okta Developer Console, either directly or indirectly by removing them from a group, then the corresponding user subscription record is deleted when the daily scheduled jobs run.

*[\>]: and then


