How to handle a User and HR Profile created during on boarding when the user later is created in the AD?

[palmen]

When requesting a new hire in the portal you have to fill in name and email for the user.
Since the user hasn't started yet, and this is what triggers the on boarding, the user doesn't exist in AD yet.

When submitting the request a new user and hr profile is created for the person with roles so they can access the onboarding tasks they receive.

The question is, how do we handle this user once the new hire has been created in the AD?
When the user is created in AD it will be imported as a new user to the user table.
Is there some way to set this up so it actually update the already created user? Or is the best practice to create a new user with the same but with the company email instead?

If we in some way update the existing user, the email will also be updated, which might be an issue since the new hire hasn't got access to the company email yet. 

How do you handle this part in the onboarding process?

[Susan Britt]

When triggering onboarding from ServiceNow and creating the user and HR profile at that time, you have a couple of "normal" options that have been touched on above.  1)  Update your existing AD to ServiceNow integration to verify if the sys_user account already exists based on a unique identifier or combination of fields (i.e. employee #, start date & name) and update the record accordingly.  2)  Part of your onboarding flow could include deactivating the temporary sys_user record that was automatically created, once the AD account is created.  The former is preferred, if possible.  It could help with any identity management audits and traceability, lowers the record counts, but also prevents the risk of duplicated HR Profiles, better user experience for the new hire, and keeps all existing task records assigned to the same sys_user record for that history and visibility.

[Rohit Kolate]

As I generated a HR case for new user for new hire onboarding lifecycle event so after creating user manually in user table then is the user record get updated in AD or AD for that user is updated from somewhere else.