When "Auto Provisioning User" is turned on in the IDP Record, users are still not being created in ServiceNowDescriptionYou have enabled "Auto Provisioning User" option in ServiceNow. You can understand more about user auto-provisioning HERE You can see that each time the user attempts to login, a record is NOT created in ServiceNow for this user. When checking the Import Set for the staging table corresponding to the record, you can notice it got populated. However, a record has not been created in ServiceNow. Release or EnvironmentAll versions CauseThis is mostly due to a mismatch in the transform table, comparative to the Response coming from the IDP.ResolutionLet us take the "Email field " as an example for this scenario. The target field "email" should be populated from the source field "email" from the staging table as shown in the screenshot below: You have enabled the property glide.authenticate.multisso.debug in your sys_properties table and analyzed the SAML Response. You notice that the field corresponding to Email is coming empty in the <saml:AttributeStatement> section. <saml:Attribute Name="mail" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri"> However, you are noticing the desired email is coming in another field of the staging table: example http://schemas.xmlsoap.org/ws/2005/05/identity/claims/mail Please note that is your Identity Provider that is sending the user information in the "AttributeStatement" element in the SAMLResponse. You will need to work with your Identity Provider admin to confirm that configuration After agreeing with the correct attributes to be send over, you would need to update the import set table and transform map associated to your Identity Provider that maps those "AttributeStatement" elements to the columns of sys_user table. In this specific example, you need to replace in the transform map, the field : Email - maps to email from the above screenshot, with http://schemas.xmlsoap.org/ws/2005/05/identity/claims/mail maps to email.