Xink Field Character Limit for Azure AD Synced Attributes

We recently switched from on prem AD sync to Azure AD sync for our employee attributes to Xink. We have now run into a 256 character limit on the new fields with AAD values which didn't exist on the previous fields containing on premise attribute values.

Nothing changed with our attribute values. The only thing that changed is the AD source. Can we please have the character limit increased to at least 448 (with spaces)? Our on premise to Azure sync tool (AD Connect) has a character limit of 448 so that's the max that we can sync to Azure anyways. If Xink could match this that would be great as we had just explained to the staff that they would have to shorten any disclaimers, land acknowledgements, etc. to 448 only to start getting angry emails from them when half of their signatures are cut off now at 256.

Thank you for the consideration.

Shane


  • Hi Shane -

    Do you conclude that it's the Xink portal that limits your AAD attrib values to 256 characters?

    AzureAD Schema extensions limits (String 256 characters):
    https://learn.microsoft.com/en-us/answers/questions/799018/azuread-schema-extensions-limits-(string-256-chara

    Thanks
    Jesper

  • Hi Jesper,


    Yes I'm pretty certain it's a Xink limitation as I can see the attributes have more than 256 characters in Azure AD. Xink isn't pulling in all the data it seems.


    Thanks,

    Shane

  • Just to add, if you check the below MS article:

    Azure AD Connect sync: Make a change to the default configuration - Microsoft Entra | Microsoft Learn


    There is a comment:


    image


  • Hi Folks,


    To add to this thread, the Azure AD Connect article below mentions that the string attribute maximum character limit is 448:

    Azure AD Connect sync: Make a change to the default configuration - Microsoft Entra | Microsoft Learn


    image


  • Got it, Shane -

    We use Microsoft API to read the values in AAD.
    As you can see in the link I provided above, the limitation is 256 characters, enforced by Microsoft, and the workaround is to split the value.

    I appreciate your understanding.
    Jesper

  • Hi Shane -

    Which of the below custom fields require more than 256 characters, please?

    Then I'll ask our development to investigate - Thanks.

  • Hi Jesper,


    It's the fields "AZ Title 3" and "AZ Title 3 in French" that we were hoping could be increased to 448.


    Thanks!
    Shane

  • Hi Shane,

    This is to confirm that the limitation is currently set at 256 characters. 

    As a workaround to the limitation of custom field of Azure AD.

    You can apply below: 
    1. Enable the setting "Do not update fields that were set or changed manually" https://imgur.com/a/TH2xZMY

    2. Manually enter the value in the Xink portal for each user 


Login or Signup to post a comment