We have an issue where an Extension Attribute value is becoming hex code in a Configuration Profile. To give a bit more background, we use Cisco Umbrella for web filtering. In order to identify the user to Umbrella, we use a Configuration Profile which contains an Extension Attribute which is mapped to userPrincipalName from AzureAD. For most of our end users, this populates correctly in the format "username@company.com". However, in a few cases it becomes "username@company.com". "@" is the unicode hex code for "@". Looking at the Computer itself in Jamf correctly displays "@". Does anyone have any suggestions? Is this related to an old bug of PI-006195?
