I am working on updating the description attribute in Active Directory on users using EmployeeID and Jobtitle as the description. Any new account gets that, but I want to update all users description to match that form but I also want if the jobtitle changes to change the title in the description. I was going to setup an Identity attribute and do a transform and do attribute sync in the AD source for description. Wanted to see what others were doing or what best practice would be.
I’ve had a similar use case before, but for setting an extensionAttribute on the account.
I agree with your idea that using an identity attribute + attribute sync is the simplest native approach.
If you only needed this populated once, I would go with a static option during account creation and reference the attributes there. This approach would save you an identity attribute, but it sounds like you require it to be updated on an ongoing basis.
I can think of numerous ways to do this, but I don’t think there are any that are as native and simple as an identity attribute + attribute sync.
Are you syncing job title to an AD attribute already? If so you can forego creating an identity attribute and instead calculate that description value in an update provisioning policy
Hi @dpowers1 ,
I think you are already on right track.
Just one thing I will highlight is: if the displaynames for existing users are not already correct in AD. You might want to do a clean up activity first on AD side directly and then make the changes to avoid mass update from ISC which could lead to some short of performance issues. its better to do that one time activity on AD side directly and then enable the feature in ISC.
You are in your approach to create an attribute use transforms to evaluate the value for description and then enable one to one attribute sync on the source level
We had similar requirement and we did using Identity Attribute + Transform + Attribute Sync. I am not sure if we really have any other option here ?
Yes the job title is being synced to an attribute.
Just throwing it in the mix. Probably a bit heavyweight, but you could run a powershell to do the job with an After Modify Connector Rule.