Forum Discussion

salvijansen's avatar
salvijansen
Copper Contributor
Sep 07, 2019

AADSTS500011 The resource principal named was not found in the tenant

Although it is less obvious in the desktop version than it is in the online version of Microsoft Teams, both are throwing authentication related errors when you have sideloaded a development version of your app, like prefetchAuthTokenForApp failure and AADSTS500011 (the latter one also mentioned by faquino here). Not sure whether it is only for multi-tenant apps, but mine is at least.

 

It doesn't seem to actually block me from following the authentication flow to get an idToken but it sure doesn't look nice. Is it an expected behavior that will automatically go away once your app is in the store?

 

Attempting to handle adal response: error:AADSTS500011: The resource principal named [appURL] was not found in the tenant named [currentTenantID]. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You might have sent your authentication request to the wrong tenant., resource: [appURL], error mapped to action:resourceDisabled

 

The tenant I'm testing it on has all possible switches set to Allow in terms of app side-loading.

    • salvijansen's avatar
      salvijansen
      Copper Contributor

      Gousia_Begum Hi Gousia Begum, thanks for replying!

       

       

      I've configured the Teams manifest as follows using the App Studio. I'm not sure what is meant by "resource url for acquiring token". If this should be something other than the root url of the site, that might be the issue. The "learn more" link still points to the old app registration site so not able to get any input there.

       

       

      Thanks again for considering my question.

      Salvi

      • salvijansen's avatar
        salvijansen
        Copper Contributor

        I've now entered https://graph.microsoft.com into the Resource URL field and that seems to have cleared the errors. I am however still wondering whether some more information would be available regarding SSO (apart from that one page).

Resources