Oct 20 2019 02:56 PM
As ADAL hasn't been touched in over two years now, I have migrated my application to MSAL. Sadly enough the Teams docs are still ADAL based. I have an application that is working fine outside Microsoft Teams. Once I embed it as an app inside Microsoft Teams, two things happen:
MSAL's acquireTokenSilent method, which returns a promise, fails silently without any possibility to know what happened. This has been raised before, many times:
There seems to have been a lab demo with MSAL's acquireTokenSilent in it, but that probably worked because it was launched from the config screen (or elsewhere) and not from the tab.
So on what location would acquireTokenSilent work? Should we move it to such an authentication popup to get it to work (far less silent though).
Oct 24 2019 04:35 AM
MSAL doesn’t yet support the ability to authenticate in an iframed environment, which is how Teams tabs work. That’s why all of our examples use AAD v1 and ADAL. We have been working with the MSAL team to fix this though, but we do not have a firm ETA to share.
Dec 17 2019 03:22 AM
@Gousia_Begum , @salvijansen with the new MSAL 1.2.0 release it seems like Teams is now supported have any of you verified it or plan to in near future?
Mar 21 2020 09:51 AM
@Gousia_Begum Hi. just wanted to check in to see if anything recently changed. I am having some issues making ADAL work within a Teams Tab and most replies to issues I've seen are to use MSAL.
thanks
Feb 25 2021 04:06 AM
@shachar1 @Freddy Bang @salvijansen @Gousia_Begum
Guys, Is there any recent update over this?
I am facing a similar issue with the Teams app while using MSAL.
Jan 18 2022 01:00 AM
Apr 28 2022 03:18 AM