Hi @Saravana ,
Thanks for reaching out.
If you have Azure AD access token for the Micrsoft Graph audience, then it is expected as these tokens are for Microsoft Graph and these token use special signing mechanisms which can validate signature using jwt.ms and not possible to validate signature using public validators i.e jwt.io.
However, if you generate the token with scope api://ClientIDofApp/.default where token is intent to use for application, then you won't get invalid signature while decoding the token using jwt.io.
It is recommended to use jwt.ms to validate the Azure AD access token.
Hope this will help.
Thanks,
Shweta
Please remember to "Accept Answer" if answer helped you.