We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

Provisioning of Entra ID User data to ServiceNow Custom Table

Harshit Singh1
Tera Contributor

Hello All,

 

We have been assigned to a task of provision user accounts added in Microsoft Entra ID Users module to be synced into ServiceNow custom table.
We already been syncing user data in sys_user table as part of SCIMv2 plugin we have setup a basic authentication connection between Entra ID and ServiceNow.
Now to sync the User details from Entra ID to ServiceNow custom table do I need to create schema and send all the field or attribute to Entra first and then Entra ID will be able to provision user details in custom table.

4 REPLIES 4

Ankur Bawiskar
Tera Patron

@Harshit Singh1 

you need to check with Entra team about this

I remember when users are provisioned the sys_user gets created automatically from Entra side

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  10x ServiceNow MVP  ||  ServiceNow Community Leader

Hello @Ankur Bawiskar ,

Yeah it is getting automatically synced into sys_user table. But what if we want to sync the same details into a custom table.

@Harshit Singh1 

for that you need to check with Entra team, seems out of the box microsoft supports sync to user table only

Configure ServiceNow for automatic user provisioning with Microsoft Entra ID 

if Entra team is not willing to do then ServiceNow will have to copy the data from User to Custom table

but what's the requirement to store same user data into another custom table?

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  10x ServiceNow MVP  ||  ServiceNow Community Leader

Tanushree Maiti
Tera Patron

Hi @Harshit Singh1 

 

Why is another custom table needed to store foundation data like user record or record details? Introducing a separate table (for Foundation data!!) for this purpose will create unnecessary technical debt.

 

If the business agrees, the records should be created directly in sys_user if it does not exists. If the data originates from another approved source, you should integrate or modify the existing process rather than introducing a new custom table.

 

Since this is foundation data, business approval is essential. The source of the data must be clearly identified and approved before implementing any solution.

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti