This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 57.00000000000001%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESK%3C/text%3E%3C/svg%3E)
Hi,
We have integrated Azure AD enterprise application with Servicenow Instance. As per below link there should be a mapping between Azure AD user with a User in Servicenow.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 2%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
@Subramanyam k , Just wanted to check if the above response helped in answering your query. Do let me know if there are any more queries around this so that we can help you further.
@Subramanyam k , I believe your understanding is correct. I am not good with service now, but what I can say is ServiceNow does require your AAD users to exits in your ServiceNow Instance and Service now does support auto-provisioning.
You can refer to the following docs for more info:
User provisioning in Service Now: https://docs.servicenow.com/bundle/orlando-platform-administration/page/integrate/saml/concept/c_SAMLUserProvisioning.html
Disclaimer: This response contains a reference to a third-party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.
Enabling Auto-Provisioning in Azure AD for Service Now: https://video2.skills-academy.com/en-us/azure/active-directory/saas-apps/servicenow-provisioning-tutorial
Hope this helps.
Do let us know if this helps and if there are any more queries around this, please do let us know so that we can help you further. Also, please do not forget to accept the response as Answer; if the above response helped in answering your query.
@Subramanyam k , Thank you for reaching out. The step you mentioned is a must as that step is used to make sure you have at least one AAD user present in the SAML application in your case its ServiceNow with the same NameIdentifier as configured in AAD. This step is referred to as pre-seeding of a user. This step is used to test the SSO for the newly added Gallery SAML application.
Once the SSO is tested and made sure all the required claims are being passed properly to the SAML app from AAD, then we can enable the auto-provisioning or just normal manual provision of users from AAD to your SAML app.
Hope this helps.
Do let us know if this helps and if there are any more queries around this, please do let us know so that we can help you further. Also, please do not forget to accept the response as Answer; if the above response helped in answering your query.
Thank You @soumi-MSFT .
Based on the above response. Once the Azure AD is integrated with Servicenow and Tested Successfully with test user.
The Azure AD users has to provisioned either automatically or manually using Azure AD Provision option.
Without user provisioning from Azure Ad -> Servicenow, The user cannot login to servicenow instance.
Please advise if my understanding is correct.
Thanks