![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 86%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELL%3C/text%3E%3C/svg%3E)
25,155 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 81%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMT%3C/text%3E%3C/svg%3E)
Hi @Leandro Lima ,
There is a known limitation. Google Workspace does not support non-ASCII characters, and Azure does not support replacing/transforming the data inside claims from non-ASCII to ASCII as it is a standard requirement to include non-ASCII characters.
I've reported this issue to both the Google and Azure teams, and they are aware of it. There is no ETA for a fix yet, though. The issue is because Google does not accept non-ascii characters in fields such as display name last name.
The best recommendation is to omit these types of attributes and rely on UPN/e-mail address. Our issued tokens will contain the users' names as stored in AAD - so if they have non-ASCII characters, we will include those.
See related issues:
https://github.com/MicrosoftDocs/azure-docs/issues/84432
https://learn.microsoft.com/en-us/answers/questions/50242/g-suite-sso.html
I also recommend creating a request with Google to drive this improvement. https://support.google.com/a/answer/6284762?hl=en
-
If the information helped you, please Accept the answer. This will help us and other community members as well.