Forum Widgets
Latest Discussions
How are you keeping Teams Machine-Wide Installer updated?
Now that Message Center # MC245996 is going into effect, users with new-to-them PCs with older install dates of Office are starting to see the update screen with the Teams Upgrade button. Since Office updates don't appear to keep the Teams Machine-Wide Installer updated, I'm wondering what solution you've come up with to keep the installer up to date. The current method of relying on the user to update isn't very enterprise friendly for an organization that typically prohibits software downloads. Is anyone aware of anything on the roadmap for the Office updater to keep the Teams Machine-Wide Installer updated with a more recent version of Teams?
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.
