{"id":9186,"date":"2022-11-16T20:18:10","date_gmt":"2022-11-16T20:18:10","guid":{"rendered":"https:\/\/blogs.aaddevsup.xyz\/?p=9186"},"modified":"2022-11-16T20:18:16","modified_gmt":"2022-11-16T20:18:16","slug":"the-identity-of-the-calling-application-could-not-be-established","status":"publish","type":"post","link":"https:\/\/blogs.aaddevsup.xyz\/2022\/11\/the-identity-of-the-calling-application-could-not-be-established\/","title":{"rendered":"The identity of the calling application could not be established"},"content":{"rendered":"\n
You are getting the following error from Microsoft Graph or downstream services that uses Microsoft Graph…<\/p>\n\n\n\n
\nThe identity of the calling application could not be established<\/p>\n<\/blockquote>\n\n\n\n
This error is thrown because the “oid” and “sub” claim is missing from the access token. This is because the servicePrincipal does not exist in the tenant or the tenant is not aware of the application.<\/p>\n\n\n\n
Partner Scenario<\/h2>\n\n\n\n
If this is a Partner application, make sure you follow the Partner pre-consent process. <\/p>\n\n\n\n
And do not forget to add your application\/servicePrincipal to the AdminAgents group.<\/strong><\/p>\n\n\n\n