Azure AD Integration issue - UPN length

[Lex]

Would like to request for recommendation on how to address ServiceNow user_name length limitation (40).

We are integrated to Azure AD using UPN with max length of 256.  ServiceNow OOTB is causing issue as it truncates the data beyond 40 (length). 

There's a KB article stating that it is not recommended to increase length of user_name, since it will have downfall impact to other tables utilizing the user_name value (for created by/updated by field).

How should we handle this? 

Note that - Only ServiceNow has this user_name limitation issue integrating w/ our Azure AD. 
We have hundreds of users w/ 40+ length in UPN and updating their UPN just for servicenow may not be the best option (considering other apps).

[Hemant Kumar Ch · Accepted solution]

Hello Lex 

It sounds like the primary issue you are facing is that the user_name field in ServiceNow has a length limitation of 40 characters, and you are unable to change this field due to the potential impacts on other tables that use this field.

One solution you could consider is to use a different field in ServiceNow to store the Azure AD UPN. This field could have a longer length, allowing you to store the full UPN without truncation. You could then use a custom script or integration to populate this field with the UPN from Azure AD when a user is created or updated in ServiceNow.

Another option would be to use a different method of integration between ServiceNow and Azure AD that does not rely on the user_name field. For example, you could use a different field in ServiceNow as the unique identifier for each user, and use this field to map to the appropriate user in Azure AD.

It's also worth considering whether it is necessary to store the full UPN in ServiceNow. Depending on your use case, you may be able to store a shorter version of the UPN (such as the username portion before the "@" symbol) in the user_name field, or you may be able to use a different field altogether to store the UPN.