The application ID typically represents an application object, but it can also represent a service principal object in Azure AD.
Example JWT Value: The intended recipient of the token.
A value of "0" indicates the end-user authentication did not meet the requirements of ISO/IEC 29115.
Example JWT Value: Provides object IDs that represent the subject's group memberships.
When your app receives an id_token, it must validate the signature to prove the token's authenticity and validate a few claims in the token to prove its validity.
The claims validated by an app vary depending on scenario requirements, but there are some common claim validations that your app must perform in every scenario.
If necessary, even more detail can be found in the Open ID Connect specification.
Though authentication with Azure AD is required in order to receive a bearer token, steps must be taken to secure the token, to prevent interception by an unintended party.There are several tools available for doing so, such as For more information on JWTs, you can refer to the JWT specification.You can use the claims in an id_token as you see fit - commonly they are used for displaying account information or making access control decisions in an app.Id_tokens are signed, but not encrypted at this time.