This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(92.8, 37%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECT%3C/text%3E%3C/svg%3E)
We have a user in our hybrid domain that is the only user getting error AADSTS90013 when trying to log in on zoom, everyone else can log in except this user. Zoom tells us that the error comes from Azure but azure does not report any errors. We are at a loss as to what to do since there is no indication in Azure/Entra that there is anything wrong with the user account. Searching the internet I found reports that the <> symbols cause authentication to fail At this point I am out of options and it seems there is almost no information on this issue. I would appreciate any help or comments.
![](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)
@Carlos Trujillo , is the user logging into Zoom via browser/web client? If this is the case, the issue could be due to login cookies being damaged. If the user could try a different browser, that may resolve the issue.
If the user scope includes those symbols, this could also trigger the error.
We have tried in multiple devices, we even wiped out and reloaded devices and switch to edge instead of chrome to rule this out. In all cases this fails and it happens only on a single user account so we are worried because we have not even started to migrate rest of 2000+ accounts and we do not know what we are going to run into.
In this case I would recommend opening a support case to investigate further and look into this user's logs. If you reach out to me at AzCommunity@microsoft.com ("Attn: Marilee Turscak") and include your subscription ID and a link to this thread, I can open a one-time free support case on your behalf.
I sent email as requested and provided the information requested. Thank you for your help.