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 No comments

59 answers

Sort by: Oldest
  1. Anonymous
    2025-04-03T13:15:05+00:00

    I had this problem in a corporate VDI environment and the login issue was caused by using folder redirection in FsLogix

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2025-04-03T13:29:23+00:00

    In our environment, it was only MacOS users receiving this message. Long story short, we were able to resolve this by turning off iCloud Relay for those devices as it was continously trigger the CA policies to require an authentication.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2025-04-11T13:45:11+00:00

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

    Mitigation is necessary before posting any steps to reproduce here.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2025-06-20T17:28:56+00:00

    Hey Derek,

    What was the workaround you did to fix this issue.

    Was this answer helpful?

    0 comments No comments
  5. 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 No comments