Immutable solution version
Access Token Issuer from Azure AD is sts.windows.net Instead Of login.microsoftonline.com
Complete solution
Access Token Issuer from Azure AD is sts.windows.net Instead Of login.microsoftonline.com: (Update 2025): The property is now named requestedAccessTokenVersion in the new "Microsoft Graph App Manifest".
[juunas (accepted answer)] (Update 2025): The property is now named requestedAccessTokenVersion in the new "Microsoft Graph App Manifest". https://learn.microsoft.com/en-us/entra/identity-platform/azure-active-directory-graph-app-manifest-deprecation#attribute-differences-between-azure-ad-graph-and-microsoft-graph-formats. The default value is still null and needs to be changed to 2. Original Answer: So seems that changing the acceptedTokenVersion to 2 in the manifest did change but it just took time to take effect. And yes the audience is always the client id based on my tests in v2 tokens.
Context: Stack Overflow #59790209 (accepted answer, 52 votes, 6 answers): I'm trying to validate an access token obtained from azure active directory. I obtained the token from https://login.microsoftonline.com/{{my tenant guid}}/v2.0 The issuer in the token that comes back is https://sts.windows.net//{{my tenant guid}}/ which doesn't match. If I check that config at .well-known/openid-configuration the issuer is as expected https://login.microsoftonline.com/.... I've found a similar issue reported on git hub here https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/560 The advice is to manually edit the manifest's json in the applicatio
Matched source
Source: Published skill Original query: "Access Token Issuer from Azure AD is sts.windows.net Instead Of login.microsoftonline.com" Key terms: access, azure, instead, issuer, login, microsoftonline, token, windows
Evidence
Source: Stack Overflow #59790209 (accepted answer, 52 votes, 6 answers): I'm trying to validate an access token obtained from azure active directory. I obtained the token from https://login.microsoftonline.com/{{my tenant guid}}/v2.0 The issuer in the token that comes back is https://sts.windows.net//{{my tenant guid}}/ which doesn't match. If I check that config at .well-known/openid-configuration the issuer is as expected https://login.microsoftonline.com/.... I've found a similar issue reported on git hub here https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/560 The advice is to manually edit the manifest's json in the applicatio
Verified resolution: [juunas (accepted answer)] (Update 2025): The property is now named requestedAccessTokenVersion in the new "Microsoft Graph App Manifest". https://learn.microsoft.com/en-us/entra/identity-platform/azure-active-directory-graph-app-manifest-deprecation#attribute-differences-between-azure-ad-graph-and-microsoft-graph-formats. The default value is still null and needs to be changed to 2. Original Answer: So seems that changing the acceptedTokenVersion to 2 in the manifest did change but it just took time to take effect. And yes the audience is always the client id based on my tests in v2 tokens.
Source URL: https://stackoverflow.com/questions/59790209
By @issueatlas · Version 2 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_yy-albXWZTVZyUZ6rnCY1w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Access Token Issuer from Azure AD is sts.windows.net Instead Of login.microsoftonline.com <span>— Vectle</span></a>