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??

Anonymous
2024-07-12T14:19:44+00:00

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??

User received this error when opening New Teams.

Password is not new

Windows 11

New Teams Desktop App

(the banner was pink background with Black text and appeared to be generated by Teams)

If this is official; the wording is bad and I would like to change it. There is no documentation on MSFT for this error or its likeness.

Microsoft Teams | Microsoft Teams for business | Sign up and Sign in | Sign in

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

59 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-07-15T00:45:05+00:00

    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.

    Was this answer helpful?

    0 comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  3. Anonymous
    2025-07-08T21:47:33+00:00

    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.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2025-06-20T18:25:36+00:00

    I can't really specify the exact exclusion we had setup in FsLogix as I rolled back the entire redirections.xml.

    However, it was probably because we excluded one or more of these directories from roaming 

    AppData\Local\FSLogix

AppData\Local\Temp

AppData\Local\VirtualStore

AppData\Local\Package Cache

AppData\Local\Microsoft\TokenBroker\Cache

AppData\Local\Microsoft\MSOIdentityCRL\Tracing

AppData\Local\Microsoft\Windows\WebCache

AppData\Local\Microsoft\Windows\WebCache.old

AppData\Local\Microsoft\Windows\AppCache

AppData\Local\Microsoft\Windows\Explorer

AppData\Local\Microsoft\Windows\Temporary Internet Files

AppData\Local\Microsoft\Edge\User Data\Default\Service Worker

AppData\Local\Microsoft\Edge\User Data\Default\Cache

AppData\Local\Microsoft\Edge\User Data\Default\Code Cache

AppData\Local\Microsoft\Edge\User Data\Default\blob\_storage

AppData\Local\Microsoft\Teams\Packages\SquirrelTemp

AppData\Local\Packages\MSTeams\_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Logs 

AppData\Local\Packages\MSTeams\_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\PerfLogs 

AppData\Local\Packages\MSTeams\_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile\_tfw\WebStorage

    Was this answer helpful?

    0 comments