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(316.8, 14.000000000000002%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECI%3C/text%3E%3C/svg%3E)
Hello,
I have a question and some problems and I hope you can help me. For some employees in Success Factors, the current employment status (company, job title, etc) is not replicated in the AzureAD profile. Since the provisioning works as it is supposed to do for other employees, I don't know what might cause this. Do you have any idea?
We have also issues with the current employment status of employees who had two active positions in SuccessFactors after one of the position/contracts was terminated in SuccessFactors, the Azure AD profile was updated by the provisioning with the employment detail from the terminated contract, instead of the active contract.
Thank you.
Have you tried to provision on demand and troubleshot?
Another option would be to stop the provisioning, then restart and see if it works after that.
The provisioning logs can be useful to see what may be the issue
Hello. If I'm using the provision on demand, for those specific users, I got the message "The state of the entry in both the source and target systems already match" and in the logs, the process for those users appears as skipped. I have not tried stopping and restarting the provisioning, because I'm worried that we'll have more users with the same problem that we actually have. The strange thing is that for me and most part of my colleagues, the process of terminating the old contract and getting hired on a new one went without issues, our current contract details were uploaded in AzureAD, but for those users, the same termination> new hire process made by HR didn't work as expected. Stopping and restarting the provisioning, should not bring the same result as the provision on demand?
Thank you.
Well, I have seen stopping and starting fix things.
I know. Well, for some users, it worked but for some not :(
I'm running out of ideas
Thank you.
would it be possible to remove the accounts that arent working and reprovision? Not sure is you want to go that route.
If its still not working, opening a ticket with Azure support may be the next step.
this is not a solution :D
Another observation is that the same provisioning configuration, with the same attributes, returns the expected result in a test AzureAD connected to some UAT instance of SuccessFactors.
I'll try to open a ticket to Azure AD support.
thank you.