Attribute Mapping in Azure AD Provisioning

Question

Hello All,

I hope you all are doing good.

We’re integrating SuccessFactors HRIS solution with Entra ID. During synchronization from SF to Entra ID, several attributes have limitations. Suppose the username attribute sends a character limit of 256, but Entra allows only 128 characters. In this case, what would be the behavior on the Entra side? Will it truncate the value or fail the process?

Regards,

Shashank Saxena

Answer 1

From experience ( not 100% sure ) Azure will take 128 char name and ignore the rest. I think this behavior will create a future problem for you. Best is to adjust SF as er Azure then deploy the app.

Answer 2

@ShashankSaxena-2458 Thank you for reaching out to us, regarding the above-mentioned issue - We’re integrating SuccessFactors HRIS solution with Entra ID. During synchronization from SF to Entra ID, several attributes have limitations. Suppose the username attribute sends a character limit of 256, but Entra allows only 128 characters. In this case, what would be the behavior on the Entra side? Will it truncate the value or fail the process?

If any attribute exceeds the limit enforced by the AD or Entra ID, then the operation (Create/Update) will fail for the entire object. 

Recommended way to handle this scenario is to use Mid function and truncate the incoming values from SuccessFactors so they fit into the constraints set by AD / Entra ID. 

e.g.  Entra ID companyName can have max of 64 characters, so if you're mapping the SF company attribute to it, then use the expression - Mid([company], 1, 64) 

Let me know if you have any further questions, feel free to post back.

Please remember to "Accept Answer" if answer helped, so that others in the community facing similar issues can easily find the solution.