- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-26-2023 02:29 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-26-2023 06:07 AM
So Service Now need User data in user table and Single sign on ...from where we will get this .
We get from Active Directory (AD) . Before Cloud came into picture AD setup used to be hosted in On Premise Data Center then we used to Call simple AD- Active Directory.
Now when AD is now hosted on Azure Cloud Its Called Azure AD. Nothing changed except where AD is hosted now.
So AD or Azure AD data prime use case is - User Provisioning and Deprovisioning in service Now . So all application user data is synched with AD data as AD is the golden truth for User data.
ADFS ( AD federation Services )is used for SSO.
Regards
RP

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-26-2023 05:23 AM
No need to provision/decomission users manually, possibly use SSO.
Help others to find a correct solution by marking the appropriate response as accepted solution and helpful.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-26-2023 06:07 AM
So Service Now need User data in user table and Single sign on ...from where we will get this .
We get from Active Directory (AD) . Before Cloud came into picture AD setup used to be hosted in On Premise Data Center then we used to Call simple AD- Active Directory.
Now when AD is now hosted on Azure Cloud Its Called Azure AD. Nothing changed except where AD is hosted now.
So AD or Azure AD data prime use case is - User Provisioning and Deprovisioning in service Now . So all application user data is synched with AD data as AD is the golden truth for User data.
ADFS ( AD federation Services )is used for SSO.
Regards
RP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-26-2023 08:45 AM
Hi @Sandeep _ ,
Hope you are doing great.
By linking these Azure with servicenow, following are benefits:
Centralized User Management:It ensures that user information, such as user names, roles, and attributes, remains up to date across both systems. This centralization streamlines user management tasks, reducing administrative overhead and improving data accuracy.
Single Sign-On (SSO) Capabilities: This eliminates the need for separate login credentials and simplifies the user experience, enhancing productivity and reducing the risk of password-related issues.
Enhanced Security and Compliance: Organizations can enforce multi-factor authentication (MFA) and other security policies defined in Azure AD, providing an additional layer of protection for ServiceNow access.
Automated User Provisioning and Deprovisioning: The integration facilitates the automation of user provisioning and deprovisioning processes. When a user is added or removed from Azure AD, the integration triggers corresponding actions in ServiceNow, such as creating or disabling user accounts, granting or revoking access rights, and assigning or removing roles. This automation reduces manual effort, minimizes errors, and enhances overall efficiency.
Unified Reporting and Analytics: Integrating Azure AD with ServiceNow enables consolidated reporting and analytics capabilities. IT administrators can gather comprehensive insights on user activities, access patterns, and service usage, leveraging this information to make informed decisions, optimize resource allocation, and identify areas for improvement.
Regards,
Riya Verma