Banner in New Teams Desktop “! Please sign in again. This could be a request from your IT department or Teams, or the result of a password update.” - Is this real??

This should have been fixed in January. I'm a pentester.

Mitigation is necessary before posting any steps to reproduce here.

Hello Microsoft,

Do you not pay attention to your own forums? Ok, Let's do this publicly:

Steps to reproduce:

1. Launch and login to Teams personal and enterprise. Dual screens preferred.
2. Turn off Wi-Fi
3. Pull the Ethernet cable.
4. Grab some coffee.
5. Observe the difference in error messages.

You can probably search the code for the error message verbatim.

This could be a request from your IT department or Teams, or the result of a password update.

Why this has been so elusive to Microsoft is a much more interesting story, but makes sense. Really smart people never use Wi-Fi if we can avoid it, but that's also the root of the problem. Geeks are wired, so we never see this error message. It doesn't help the error message is completely wrong. It should be "We freaked out at losing the internet for a millisecond or two, so enjoy this lovely popup!"

When connected to the internet, clicking "Sign In" makes the banner disappear. This is why this bug was so elusive. Unless you're a pentester, the problem resolves itself.

The problem is resolved in the consumer or Personal version of Teams. It's likely a minor oversight or a configuration issue this wasn't pushed to all versions of Teams. Fix Enterprise first ;)

The changes on the Personal Teams made this simple to diagnose, but that requires those same geeks to have both versions installed. Microsoft clearly missed an internal pentest here, or this never would have made it into production.

Everyone has seen this error, and just ignores it. Switching Access Points (APs) causes the same issue for the banner to immediately pop back up. This is why traveling professionals have been frustrated for so long. It's painfully obvious to everyone that's _not_ hardwired.

If you want to get into Cybersecurity, start here.

Synopsys https://www.linkedin.com/company/synopsys/

Black Duck https://www.linkedin.com/company/black-duck-software/

Cheers,

Ritchey

Have the same issue with Server 2022 - Non-persistent using latest FS Logix update 4. Classic Teams is fine. New Teams has the issue. Anyone able to resolve yet?

Did you ever get this resolved? We are running a similar setup and have the issue.

I have been able to consistently reproduce this issue. If a user logs into ServA, they get the sign-in error. If you click on sign-in message is cleared. If you logout, then log back in to ServA, no message. If you login to ServB (first time) you get the error again. Sign-out and go back to ServA (no error). Go back to ServB (error), click sign-in - no more error. Essentially the first time a FSlogix profile is used on a new machine the error occurs. Once users have logged into each host at least once (and clicked "sign in") the error goes away.

When we publish a new image, or expand the host pool - the problems start all over again.