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(275.2, 18%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAA%3C/text%3E%3C/svg%3E)
When obtaining access and id tokens from azure active directory (via nextauth), the access token comes in two different format: the standard jwt format and some other format. I have noticed that for users within my tenant, the access token is in the standard jwt format but for users that are outside my tenant, the token format is different. Both tokens work however.
The id token however seems to be the standard jwt token in every case.
Why do the tokens differ?
![](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(246.4, 20%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
Hi @Aashutosh Aryal ,
Thanks for reaching out.
Have you attempted to decode the token using the https://jwt.ms tool?
Can you please verify the structure of another token you've received?
I tried to obtain two different access tokens by authentication guest user and member and both time able to get the jwt tokens. Nevertheless, the token lengths differ because of modifications in certain claims.
Thanks,
Shweta