MS Teams android app keeps refreshing

Trying to see if there are any consistencies between users on here having this issue.

• I have a Samsung Galaxy S10+ like someone else in this thread. I am not experiencing this issue, but one of our customers is
  • Turning off WiFi seems to be the only resolution for them at this point which obviously isn't a great workaround
  • The biggest difference between my organization's setup vs our customers is we must enroll our devices in MDM whereas they are now only required to protect things at the app level via app protection policies (MAM).
• A customer we are working with is having this issue and one of the folks I was testing with had a Galaxy S20, another had a Pixel 5
  • We had them update to the latest versions of Authenticator app (beta version) and Teams app and still no luck.
  • Turning on/off WiFi was a temporary fix but within an hour the phone would go back to looping
  • They used to have their devices enrolled in Intune/MDM however now they are switching over to MAM so not sure if this has something to do with it
  • The Samsung devices are on Android 11 (will need to check to see what the Pixel was on though)

Is everyone else enforcing MFA and/or MAM in these scenarios? I believe the underlying issues are either the authentication via the Authenticator app or the App Protection Policy enforcing app-level protections (biometrics, PIN) but I don't have enough to go off of at this point.

Trying to see if there are any consistencies between users on here having this issue.

• I have a Samsung Galaxy S10+ like someone else in this thread. I am not experiencing this issue, but one of our customers is
  • Turning off WiFi seems to be the only resolution for them at this point which obviously isn't a great workaround
  • The biggest difference between my organization's setup vs our customers is we must enroll our devices in MDM whereas they are now only required to protect things at the app level via app protection policies (MAM).
• A customer we are working with is having this issue and one of the folks I was testing with had a Galaxy S20, another had a Pixel 5
  • We had them update to the latest versions of Authenticator app (beta version) and Teams app and still no luck.
  • Turning on/off WiFi was a temporary fix but within an hour the phone would go back to looping
  • They used to have their devices enrolled in Intune/MDM however now they are switching over to MAM so not sure if this has something to do with it
  • The Samsung devices are on Android 11 (will need to check to see what the Pixel was on though)

Is everyone else enforcing MFA and/or MAM in these scenarios? I believe the underlying issues are either the authentication via the Authenticator app or the App Protection Policy enforcing app-level protections (biometrics, PIN) but I don't have enough to go off of at this point.

I have a Pixel 4a using both MFA and MAM. Unfortunately this still comes up for me after updating to the beta of Teams, Outlook and Authenticator. Toggling WiFi occasionally works but a lot of the time I'm out in the field and have no WiFi connected to toggle in the first place. I've had to just use the web version on mobile for the last month or so.

To be honest, I've just given up on using Teams mobile. Microsoft support has been completely useless for me on this issue. They've asked for a video of the issue multiple times and every few weeks I get a call where I need to explain the issue again to a new agent.

Instead of workarounds can someone fix this issue, I have re-installed so many times, and its fine at first then it happens again sometimes an hour later.

I'm having the same issue and re-installing the app hasn't worked. The instructions given are only for mobile — how do we fix this on desktop? It's actually getting worse with time and becoming incredibly difficult to do my job when this is our main form of communication.

It's clearly a bug and extremely disappointing to see that it's been a problem for many months and still not resolved by Microsoft.

It appears to be fixed now.